Re: Multi-table-unique-constraint

Christopher Kings-Lynne <chriskl@familyhealth.com.au> writes:
> 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 :)

Aside from destroying the inheritance-for-partitioning stuff, this
wouldn't work for multiple inheritance, so I'm afraid it's not a very
attractive alternative.

Matt's idea about keeping the indexes separate seems that it probably
*would* work, modulo some lingering worries about when to take what kind
of lock on the index-set-as-a-whole.  It seems worth pursuing, anyway.
        regards, tom lane