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 603c8f070907312108y22c61ae4le4c15e4fcc77157f@mail.gmail.com
Whole thread Raw
In response to Re: ALTER TABLE ... ALTER COLUMN ... SET DISTINCT  (Dimitri Fontaine <dfontaine@hi-media.com>)
Responses Re: ALTER TABLE ... ALTER COLUMN ... SET DISTINCT  (Dimitri Fontaine <dfontaine@hi-media.com>)
List pgsql-hackers
On Fri, Jul 31, 2009 at 11:09 AM, Dimitri
Fontaine<dfontaine@hi-media.com> wrote:
> I failed to have 0 to allow for analyze to compute a value again, as shown
> in the raw notes in attachement:

I'm lost.  I think you're getting the new column attdistinct mixed up
with the existing column stadistinct.  attdistinct is always going to
have whatever value you assign it.  stadistinct will get attdistinct
!= 0 ? attdistinct : <result of analyze calculation>.

...Robert


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Revised signal multiplexer patch
Next
From: Robert Haas
Date:
Subject: Re: machine-readable explain output v2