At 01:00 PM 18/12/2002 +0100, Roel Rozendaal - IC&S wrote:
it got me a value of 38; the system has default config of
max_fsm_relations (100) so that shouldn't be the problem either.
A simple (heavy-handed) approach would be:
set max_fsm_relations to 1000
set vacuum frequency to daily
get the output of a VACUUM VERBOSE:
psql -c "vacuum verbose" dbmail > vacuum.out 2>&1
grep "Changed" vacuum.out | grep -v "Changed 0,"
add all the 'changed' values together, double it, and set
max_fsm_pages to this value.
Bear in mind that (max_fsm_pages*4 bytes) of shared memory will be
consumed, so if the value is very high it may need kernel config changes
(Linux it is dynamic).
The reason I say 'double it' is on the assumption that you will have busier
days. Also bear in mind that you should run a VACUUM ASAP after starting
the server to build the FSM.
I do strongly recommend that you VACUUM FULL the database (or
backup/restore), then set a VACUUM VERBOSE running hourly (we do it
two-hourly, but have a lower load) - and keep the logs to check the
settings. You may well find that VACUUMing a cleaner database will put less
strain on your server.
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 03 5330 3172 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
