On Thu, 3 Oct 2002 10:45:08 -0600 (MDT), "scott.marlowe"
<scott.marlowe@ihs.com> wrote:
> effective cache size is the default (i.e. commented out)
The default is 1000, meaning ca. 8 MB, which seems to be way too low.
If your server is (almost) exclusively used by Postgres, try setting
it to represent most of your OS cache (as reported by free on Linux).
Otherwise you have to estimate the fraction of the OS cache that gets
used by Postgres.
I'm still trying to get a feeling for how these settings play
together, so I'd be grateful if you report back the effects this has
on your cost estimates.
Caveat: effective_cache_size is supposed to be the number of cache
pages available to one query (or is it one scan?). So if you have
several concurrent queries (or complex queries with several scans),
you should choose a lower value. OTOH if most of your queries operate
on the same data, one query could benefit from pages cached by other
queries ... You have to experiment a little.
ServusManfred
