On Tue, Jul 26, 2011 at 10:51:58AM -0400, Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > On Tue, Jul 26, 2011 at 4:12 AM, Nikhil Sontakke
> > <nikhil(dot)sontakke(at)enterprisedb(dot)com> wrote:
> >> Hmmm, but then it does open up the possibility of naive users shooting
> >> themselves in the foot. It can be easy to conjure up a
> >> parent-only-constraint that does not gel too well with its children. And
> >> that's precisely why this feature was added in the first place..
> > Yeah, but I think we need to take that chance. At the very least, we
> > need to support the equivalent of a non-inherited CHECK (false) on
> > parent tables.
> No, the right solution is to invent an actual concept of partitioned
> tables, not to keep adding ever-weirder frammishes to inheritance so
> that it can continue to provide an awkward, poorly-performing emulation
> of them.
Other SQL engines have partitions of types list, range and hash, and
some can sub-partition. I'm thinking it might be easiest to do the
first before adding layers of partition structure, although we should
probably bear in mind that such layers will eventually exist.
Does the wiki on this need updating?
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
In response to
pgsql-hackers by date
|Next:||From: Noah Misch||Date: 2011-07-26 16:04:40|
|Subject: Re: Another issue with invalid XML values|
|Previous:||From: Pavan Deolasee||Date: 2011-07-26 15:40:36|
|Subject: Re: write scalability|