Re: ALTER TABLE ... ALTER COLUMN ... SET DISTINCT - Mailing list pgsql-hackers

From Robert Haas
Subject Re: ALTER TABLE ... ALTER COLUMN ... SET DISTINCT
Date
Msg-id 603c8f070905050908j4ca6aefamc33e35b2170a89@mail.gmail.com
Whole thread Raw
In response to Re: ALTER TABLE ... ALTER COLUMN ... SET DISTINCT  (Joshua Tolley <eggyknap@gmail.com>)
Responses Re: ALTER TABLE ... ALTER COLUMN ... SET DISTINCT  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, May 4, 2009 at 10:41 PM, Joshua Tolley <eggyknap@gmail.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


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: windows doesn't notice backend death
Next
From: Tom Lane
Date:
Subject: Re: ALTER TABLE ... ALTER COLUMN ... SET DISTINCT