On Thursday 04 December 2003 19:50, Jack Coates wrote:
>
> I'm trying to set Postgres's shared memory usage in a fashion that
> allows it to return requested results quickly. Unfortunately, none of
> these changes allow PG to use more than a little under 300M RAM.
> vacuumdb --analyze is now taking an inordinate amount of time as well
> (40 minutes and counting), so that change needs to be rolled back.
You don't want PG to use all your RAM, it's designed to let the underlying OS
do a lot of caching for it. Probably worth having a look at vmstat/iostat and
see if it's saturating on I/O.
--
Richard Huxton
Archonet Ltd
