Robert Haas <robertmh...@gmail.com> writes:
> I would feel a lot better about something that is deterministic, like,
> I dunno, if VACUUM visits more than 25% of the table, we use its
> estimate. And we always use ANALYZE's estimate. Or something.
This argument seems to rather miss the point. The data we are working
from is fundamentally not deterministic, and you can't make it so by
deciding to ignore what data we do have. That leads to a less useful
estimate, not a more useful estimate.
> Another thought: Couldn't relation_needs_vacanalyze() just scale up
> reltuples by the ratio of the current number of pages in the relation
> to relpages, just as the query planner does?
Hmm ... that would fix Florian's immediate issue, and it does seem like
a good change on its own merits. But it does nothing for the problem
that we're failing to put the best available information into pg_class.
Possibly we could compromise on doing just that much in the back
branches, and the larger change for 9.1?
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
