Re: inheritance. more. - Mailing list pgsql-general

From Gurjeet Singh
Subject Re: inheritance. more.
Date
Msg-id 65937bea0804300430u4bb10349nc1aeeef7f8c516c1@mail.gmail.com
Whole thread Raw
In response to Re: inheritance. more.  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: inheritance. more.  ("Karsten Hilbert" <Karsten.Hilbert@gmx.net>)
Re: inheritance. more.  (Jeremy Harris <jgh@wizmail.org>)
List pgsql-general
On Tue, Apr 29, 2008 at 11:47 AM, Martijn van Oosterhout <kleptog@svana.org> wrote:
On Tue, Apr 29, 2008 at 06:31:30AM +0530, Gurjeet Singh wrote:
> On Mon, Apr 28, 2008 at 8:01 PM, Erik Jones <erik@myemma.com> wrote:
> > Postgres doesn't yet handle inheritance of constraints from parent to
> > child tables via inheritance.

> Was it done by design or was it a limitation we couldn't get over?

Inheritence of most constraints works, just not unique constraints. The
problem of managing a unique index over multiple tables has not yet
been solved (it's a reasonably hard problem).


I completely agree with the difficulty of the problem. One of the advantages of breaking up your data into partitions, as professed by Simon (I think) (and I agree), is that you have smaller indexes, which improve performance. And maybe having one huge index managing the uniqueness across partitioned data just defeats the idea of data partitioning!

Best regards,
--
gurjeet[.singh]@EnterpriseDB.com
singh.gurjeet@{ gmail | hotmail | indiatimes | yahoo }.com

EnterpriseDB      http://www.enterprisedb.com

Mail sent from my BlackLaptop device

pgsql-general by date:

Previous
From: Andy Anderson
Date:
Subject: Quoting "
Next
From: "Peter Geoghegan"
Date:
Subject: Performing a sub-query in a SELECT SUM aggregate.