Re: Two constraints with the same name not always allowed - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: Two constraints with the same name not always allowed
Date
Msg-id 20180902170511.ibjquzhymvnfvkqs@alvherre.pgsql
Whole thread Raw
In response to Re: Two constraints with the same name not always allowed  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Two constraints with the same name not always allowed  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On 2018-Sep-02, Tom Lane wrote:

> This also points up the lack of a suitable unique index on pg_constraint.
> It's sort of difficult to figure out what that should look like given that
> pg_constraint contains two quasi-independent collections of constraints,
> but maybe UNIQUE(conrelid,contypid,conname) would serve given the
> reasonable assumption that exactly one of conrelid and contypid is zero.

Hmm ... c.f. 7eca575d1c28.  Maybe we should split them out?  Are there
reasons to have them together at all?

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Two constraints with the same name not always allowed
Next
From: Andres Freund
Date:
Subject: Re: BUG #15350: Getting invalid cache ID: 11 Errors