Re: hist boundary duplicates bug in head and 8.3

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Nathan Boley" <npboley(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: hist boundary duplicates bug in head and 8.3
Date: 2009-01-06 23:40:09
Message-ID: 13427.1231285209@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Nathan Boley" <npboley(at)gmail(dot)com> writes:
>> I don't think this is a bug.

> hmmm... Well, I assumed it was a bug from a comment in analyze.

> From ( near ) line 2130 in analyze.c

> * least 2 instances in the sample. Also, we won't suppress values
> * that have a frequency of at least 1/K where K is the intended
> * number of histogram bins; such values might otherwise cause us to
> * emit duplicate histogram bin boundaries.

That's talking about a case where we have a choice whether to include a
value in the MCV list or not. Once the MCV list is maxed out, we can't
do anything to avoid duplicates.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen R. van den Berg 2009-01-06 23:43:02 Re: Runaway backend at 100% CPU PostgreSQL v8.3.5
Previous Message Nathan Boley 2009-01-06 23:36:32 Re: hist boundary duplicates bug in head and 8.3