>>> "Tory M Blue" <tmblue@xxxxxxxxx> wrote: > DETAIL: A total of 501440 page slots are in use (including overhead). > 501440 page slots are required to track all free space. > Current limits are: 1087500 page slots, 430 relations, using 6401 kB. As already pointed out, that's a lot of free space. You don't use VACUUM FULL on this database, do you? That would keep the data relatively tight but seriously bloat indexes, which is consistent with your symptoms. VACUUM FULL should not be used routinely, it is basically for recovery from serious heap bloat when you don't have space for another copy of the data, and it should usually be followed by a REINDEX to clean up the index bloat it causes. > And effective_cache, ya I didn't change that as I wanted to see how > the results were with just adding memory and in all honesty it was > night and day without changing that param, what will modifying that > param accomplish? It may allow PostgreSQL to pick more efficient plans for some of your queries. Be honest with it about the available resources and give it the chance. In particular, you may see fewer queries resorting to sequential scans of entire tables. -Kevin -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
