Re: [BUG?] table inhiritance violates primary key - Mailing list pgsql-general

From Sven Köhler
Subject Re: [BUG?] table inhiritance violates primary key
Date
Msg-id 3EF9B3E9.7020009@upb.de
Whole thread Raw
In response to Re: [BUG?] table inhiritance violates primary key  (Stephan Szabo <sszabo@megazone23.bigpanda.com>)
List pgsql-general
> Table inheritance is fairly broken right now. Foreign keys and unique
> constraints (including primary key) don't inherit to children, you can't
> even get the effect that is generally desired by putting a separate
> constraint on the child table since then the parent and the child could
> each insert a 1 value.  Workarounds have been discussed in the past, so
> you can probably find details in the archives. There was also talk
> recently about multi-table indexes on either general or hackers, so you
> can find that discussion as well for more info.

I'm very disappointed now. Table inheritance was the feature that
attracted me the most. Is it currently an experimental feature? Is it a
goal to achieve stability for future versions of postgresql? Which
version might be first with stable table inheritance?


pgsql-general by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Determining table size
Next
From: Tom Lane
Date:
Subject: Re: Alternative replication method.