Re: [postgresSQL] [bug] Two or more different types of constraints with same name creates ambiguity while drooping. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [postgresSQL] [bug] Two or more different types of constraints with same name creates ambiguity while drooping.
Date
Msg-id 19074.1459356346@sss.pgh.pa.us
Whole thread Raw
In response to Re: [postgresSQL] [bug] Two or more different types of constraints with same name creates ambiguity while drooping.  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> Tom Lane wrote:
>> What we need is a unique index on pg_constraint.
>> The problem with that is that pg_constraint contains both table-related
>> and type (domain) related constraints; but it strikes me that we could
>> probably create a unique index on (conrelid, contypid, conname).

> Weren't you proposing elsewhere to split pg_constraint in two catalogs,
> one for table constraint and another for domain constraints?  That seems
> a cleaner solution to me.

Yeah, and you'll notice how much progress we've made towards that.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: snapshot too old, configured by time
Next
From: Amit Langote
Date:
Subject: Re: [GENERAL] pg_restore casts check constraints differently