Re: Multi-table-unique-constraint - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: Multi-table-unique-constraint
Date
Msg-id 4376D9F2.4050807@familyhealth.com.au
Whole thread Raw
In response to Re: Multi-table-unique-constraint  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Multi-table-unique-constraint  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> Most of the people who have thought about this have figured that the
> right solution involves a single index spanning multiple tables (hence,
> adding a table ID to the index entry headers in such indexes).  This
> fixes the lookup and entry problems, but it's not any help for the
> lock-against-schema-mods problem, and it leaves you with a real headache
> if you want to drop just one of the tables.
> 
> 'Tis a hard problem :-(

Maybe the solution is to make inherited tables actually the same table, 
and jank it with an extra per-row attribute to differentiate them or 
something :)

Might make constraint_exclusion less useful then.

Chris


pgsql-hackers by date:

Previous
From: Samer Abukhait
Date:
Subject: Re: CONNECT BY PRIOR
Next
From: Kevin Brown
Date:
Subject: Re: SIGSEGV taken on 8.1 during dump/reload