Re: index v. seqscan for certain values

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: jdunn(at)autorevenue(dot)com
Cc: "'Postgresql Performance'" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: index v. seqscan for certain values
Date: 2004-04-13 17:55:49
Message-ID: 24670.1081878949@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

"Jeremy Dunn" <jdunn(at)autorevenue(dot)com> writes:
> Interestingly, I tried increasing the stat size for the CID column to
> 2000, analyzing, and checking the accuracy of the stats again.

There's a hard limit of 1000, I believe. Didn't it give you a warning
saying so?

At 1000 the ANALYZE sample size would be 300000 rows, or about a quarter
of your table. I would have thought this would give frequency estimates
with much better precision than you seem to be seeing --- but my
statistics are rusty enough that I'm not sure about it. Possibly the
nonuniform clumping of CID has something to do with the poor results.

Any stats majors on the list?

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Robert Treat 2004-04-13 18:02:39 query slows down with more accurate stats
Previous Message Jeremy Dunn 2004-04-13 14:41:30 Re: index v. seqscan for certain values