Re: Index Scans become Seq Scans after VACUUM ANALYSE

> > ... I have seen many instances of when
> > PostgreSQL refuses to use an index because the data distribution is uneven.
>
> This is fixed, or at least attacked, in 7.2. Again, I do not see
> this as an argument for making the planner stupider instead of
> smarter.

Could someone fork out some decent criteria for these "stats" that way
someone could generate a small app that would recommend these values
on a per site basis. Having them hardwired and stuffed into a system
catalog does no good to the newbie DBA. Iterating over a set of SQL
statements, measuring the output, and then sending the user the
results in the form of recommended values would be huge.
<dumb_question>Where could I look for an explanation of all of these
values?</dumb_question>

-sc

--
Sean Chittenden