[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [HACKERS] Setting a pre-existing index as a primary key
From:       Tom Lane <tgl () sss ! pgh ! pa ! us>
Date:       2008-05-11 0:33:24
Message-ID: 9090.1210466004 () sss ! pgh ! pa ! us
[Download RAW message or body]

"Jonah H. Harris" <jonah.harris@gmail.com> writes:
> ALTER TABLE blah ADD ... PRIMARY KEY (...) USING PREBUILT INDEX index_hame

> If the user doesn't specify CONSTRAINT constraint_name, it will
> default to current implicit behavior of col_pkey.

IOW, the default behavior is to rename the index?  Doesn't seem to me
to satisfy the principle of least surprise.

I agree with Andrew that creating new keywords just for noise purposes
is not gonna happen.

			regards, tom lane

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic