| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Joshua Tolley <eggyknap(at)gmail(dot)com> |
| Cc: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ALTER TABLE ... ALTER COLUMN ... SET DISTINCT |
| Date: | 2009-05-05 16:08:24 |
| Message-ID: | 603c8f070905050908j4ca6aefamc33e35b2170a89@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 4, 2009 at 10:41 PM, Joshua Tolley <eggyknap(at)gmail(dot)com> wrote:
> On Mon, May 04, 2009 at 10:13:31PM -0400, Robert Haas wrote:
>
> <nit>
>> + own analysis indicates otherwie). When set to a negative value, which
> s/otherwie/otherwise
> </nit>
>
>
> A question: why does attdistinct become entry #5 instead of going at the end?
> I assume it's because the order here controls the column order, and it makes
> sense to have attdistinct next to attstattarget, since they're related. Is
> that right? Thanks in advance...
Yep, that was my thought.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-05-05 16:13:15 | Re: ALTER TABLE ... ALTER COLUMN ... SET DISTINCT |
| Previous Message | Andrew Dunstan | 2009-05-05 16:05:34 | Re: windows doesn't notice backend death |