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

From Peter Eisentraut
Subject Re: Two constraints with the same name not always allowed
Date
Msg-id 4a963af1-b199-ceae-6e55-804535bbf09b@2ndquadrant.com
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 02/09/2018 19:00, 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.

Sketches for assertions set both conrelid and contypid to zero.  I think
the unique constraint would have to include connamespace to support that
properly.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-bugs by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: BUG #15358: PostgreSQL fails to build on 10.14 when Perl isenabled.
Next
From: Michael Paquier
Date:
Subject: Re: BUG #15367: Crash in pg_fe_scram_free when using foreign tables