Re: Patch to add a primary key using an existing index - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Patch to add a primary key using an existing index
Date
Msg-id 23884.1291481199@sss.pgh.pa.us
Whole thread Raw
In response to Re: Patch to add a primary key using an existing index  (Robert Treat <rob@xzilla.net>)
Responses Re: Patch to add a primary key using an existing index  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Treat <rob@xzilla.net> writes:
> Actually I think I'd even be comfortable with A, either you must name the
> constraint after the index, or you can leave the constraint name out, and
> we'll use the index name.

Or we could omit the "CONSTRAINT name" clause from the syntax
altogether.

I think that allowing the names to be different is a bad idea.  That
hasn't been possible in the past and there's no apparent reason why
this feature should suddenly make it possible.  We will have problems
with it, for instance failures on name collisions because generated
names are only checked against one catalog or the other.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: EXPLAIN Sort Method whitespace
Next
From: Tom Lane
Date:
Subject: Re: FK's to refer to rows in inheritance child