> 3. The patch introduces a slight weirdness: if you create two FKs on the
> same column at the same time you end up with two constraints with
> identical names. Drop constraint then removes them both, though in other
> respects they are both valid, just not uniquely. CREATE INDEX avoids
> this by way of the unique index on relname. The equivalent index on
> pg_constraint is not unique, though *cannot* be made unique without
> breaking some corner cases of table inheritance.
Urk... this seems pretty undesirable.
...Robert
