pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Gierth <andrew@tao11.riddles.org.uk>
Cc: André Hänsel <andre@webkr.de>
Cc: pgsql-bugs@postgresql.org
Subject: Re: Two constraints with the same name not always allowed
Date: Thu, 6 Sep 2018 23:53:47 +0200
Message-ID: <4a963af1-b199-ceae-6e55-804535bbf09b@2ndquadrant.com> (raw)
In-Reply-To: <10110.1535907645@sss.pgh.pa.us>
References: <0c1001d4428f$0942b430$1bc81c90$@webkr.de>
	<87in3ovy0r.fsf@news-spur.riddles.org.uk>
	<10110.1535907645@sss.pgh.pa.us>

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




view thread (9+ messages)  latest in thread

Message-ID: <4a963af1-b199-ceae-6e55-804535bbf09b@2ndquadrant.com>
Permalink:  ../4a963af1-b199-ceae-6e55-804535bbf09b@2ndquadrant.com/
Also on:    postgresql.org/message-id/4a963af1-b199-ceae-6e55-804535bbf09b@2ndquadrant.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: peter.eisentraut@2ndquadrant.com, tgl@sss.pgh.pa.us, andrew@tao11.riddles.org.uk, andre@webkr.de
  Subject: Re: Two constraints with the same name not always allowed
  In-Reply-To: <4a963af1-b199-ceae-6e55-804535bbf09b@2ndquadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox