Re: ALTER TABLE ... ALTER COLUMN ... SET DISTINCT

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
Cc: 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-08-01 04:08:06
Message-ID: 603c8f070907312108y22c61ae4le4c15e4fcc77157f@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jul 31, 2009 at 11:09 AM, Dimitri
Fontaine<dfontaine(at)hi-media(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-08-01 04:18:46 Re: machine-readable explain output v2
Previous Message Robert Haas 2009-08-01 03:58:56 Re: Revised signal multiplexer patch