| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Setting a pre-existing index as a primary key |
| Date: | 2008-05-11 00:33:24 |
| Message-ID: | 9090.1210466004@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Jonah H. Harris" <jonah(dot)harris(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Sullivan | 2008-05-11 02:41:56 | Re: Setting a pre-existing index as a primary key |
| Previous Message | Andrew Dunstan | 2008-05-10 22:48:23 | Re: Setting a pre-existing index as a primary key |