| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Hervé Piedvache <herve(at)elma(dot)fr> |
| Cc: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, Sébastien PALLEAU <spalleau(at)elma(dot)fr>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: question about seq scan and index scan |
| Date: | 2002-10-26 14:31:44 |
| Message-ID: | 27356.1035642704@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
=?iso-8859-15?q?Herv=E9=20Piedvache?= <herve(at)elma(dot)fr> writes:
> Le Vendredi 25 Octobre 2002 20:17, Stephan Szabo a crit :
>> Are the estimated number of rows for the scan of a (4379, 3987, and 29)
>> realistic for mynumber>(23000, 23500, 24000)
> I'm surpise about this answer for
>> 23000
> result is 98
>> 23350
> result is 96
>> 24000
> result is 93
Hmm, have you "ANALYZE"d this table recently? If so it would be
interesting to see the pg_stats row for tablea.mynumber.
If the distribution of mynumber is very uneven, it might be worth
your while to increase the statistics target for the column, so that
the planner has more data points with which to make a better estimate.
See ALTER TABLE SET STATISTICS.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hervé Piedvache | 2002-10-26 14:53:42 | Re: question about seq scan and index scan |
| Previous Message | Tom Lane | 2002-10-26 14:21:20 | Re: GROUP BY array |