Re: Query plan changes after pg_dump / pg_restore

On Thu, 9 Jun 2005, Jona wrote:

> It's the same (physical) server as well as the same PostGreSQL daemon,
> so yes.

The only thing that can differ then is the statistics collected and the
amount of dead space in tables and indexes (but since you both reindex and
run vacuum full that should not be it).

So comparing the statistics in the system tables is the only thing I can
think of that might bring some light on the issue. Maybe someone else have
some ideas.

And as KL said, the effective_cache_size looked like it was way to small.
With that setting bigger then pg should select index scans more often. It
doesn't explain why the databases behave like they do now, but it might
make pg select the same plan nevertheless.

--
/Dennis Björklund