Thread: max_fsm_pages and check_points
HI,
I've looking around the log files of my server and lately they indicate that I should consider increase the check_point segments because they're beeing reading too often and also recommend increasing the max_fsm_pages over 169728...
those are the config values present in the postgresql.conf
shared_buffers = 1000 # min 16 or max_connections*2, 8KB each
work_mem = 8192 # min 64, size in KB
maintenance_work_mem = 262152 # min 1024, size in KB
max_fsm_pages = 40000 # min max_fsm_relations*16, 6 bytes each
max_fsm_relations = 2000 # min 100, ~70 bytes each
And the new values, acording to the HNIT in log files ...
shared_buffers = 1000 # min 16 or max_connections*2, 8KB each
work_mem = 8192 # min 64, size in KB
maintenance_work_mem = 262152 # min 1024, size in KB
max_fsm_pages = 170000 # min max_fsm_relations*16, 6 bytes each
max_fsm_relations = 10625 # min 100, ~70 bytes each
Consigue el nuevo Windows Live Messenger Pruébalo
On mið, 2006-12-20 at 05:31 +0000, ALVARO ARCILA wrote: > > HI, > > I've looking around the log files of my server and lately they > indicate that I should consider increase the check_point segments > because they're beeing reading too often and also recommend increasing > the max_fsm_pages over 169728... if this has been happening for some time, some tables might possibly have become bloated with dead rows, so a one-time VACUUM FULL or CLUSTER on these might be indicated to speed up reaching the steady state. I think the max_fsm_pages is a minimum recommendation, so you might want to look at VACUUM VERBOSE output after setting it, to see if an even higher value is indicated > those are the config values present in the postgresql.conf > > shared_buffers = 1000 > work_mem = 8192 if you have got a lot of memory, you might want to experiment with these a little gnari