From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | ALTER TABLE ... ALTER COLUMN ... SET DISTINCT |
Date: | 2009-04-04 04:13:30 |
Message-ID: | 603c8f070904032113p344a9e14s14738ef0e436b00d@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Per previous discussion.
http://archives.postgresql.org/message-id/8066.1229106059@sss.pgh.pa.us
http://archives.postgresql.org/message-id/603c8f070904021926g92eb55sdfc68141133957c1@mail.gmail.com
I decided on SET DISTINCT rather than SET NDISTINCT for the DDL
command because DISTINCT is already a keyword, and there didn't seem
to be any compelling reason to invent a new one.
...Robert
Attachment | Content-Type | Size |
---|---|---|
ndistinct-1.patch | text/x-patch | 68.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2009-04-04 06:59:40 | Re: Documentation Update: Document pg_start_backup checkpoint behavior |
Previous Message | Tom Lane | 2009-04-04 03:54:32 | Re: Python 3.0 does not work with PL/Python |