Re: [GENERAL] Table inheritance implementation.

2007-01-05 Thread Grzegorz Nowakowski
On piÄ…, 2007-01-05 at 10:55 +0100, Martijn van Oosterhout wrote: > On Fri, Jan 05, 2007 at 09:27:31AM +0100, Grzegorz Nowakowski wrote: > > Well, I never used partitioning and I don't know what it's worth but > > just after sending my original mail I got another variant of the idea: > > to duplicat

Re: [GENERAL] Table inheritance implementation.

2007-01-05 Thread Martijn van Oosterhout
On Fri, Jan 05, 2007 at 09:27:31AM +0100, Grzegorz Nowakowski wrote: > Well, I never used partitioning and I don't know what it's worth but > just after sending my original mail I got another variant of the idea: > to duplicate columns (parent(p), child(p,c)), so inserts into child > update both pa

Re: [GENERAL] Table inheritance implementation.

2007-01-05 Thread Grzegorz Nowakowski
On czw, 2007-01-04 at 10:44 -0500, Tom Lane wrote: > Grzegorz Nowakowski <[EMAIL PROTECTED]> writes: > > But I have another question: why can't be > > inheritance implemented as implicit JOIN? > > Interesting thought, but joins are expensive --- this would be quite a > lot slower than the current

Re: [GENERAL] Table inheritance implementation.

2007-01-04 Thread Vlad
ops. alter table seems to be propagating OK in 8.2... On 1/4/07, Vlad <[EMAIL PROTECTED]> wrote: Speaking of partitioning, I see there some improvements planed for this feature in 8.3 - any info on what exactly users can expect? Any possibility to improve it so we don't have to add insert trigge

Re: [GENERAL] Table inheritance implementation.

2007-01-04 Thread Vlad
Speaking of partitioning, I see there some improvements planed for this feature in 8.3 - any info on what exactly users can expect? Any possibility to improve it so we don't have to add insert trigger that selects the right table for operation? Also, propagation of Alter table on inherited tables

Re: [GENERAL] Table inheritance implementation.

2007-01-04 Thread Tom Lane
Grzegorz Nowakowski <[EMAIL PROTECTED]> writes: > But I have another question: why can't be > inheritance implemented as implicit JOIN? Interesting thought, but joins are expensive --- this would be quite a lot slower than the current way, I fear, especially when you consider more than one level o