OK, you might also want to look at the current values of shared_buffers,
temp_buffers & work_mem in postgresql.conf.
If they seem correct/appropritate for your total shmmax memory (kernel.shmmax parameter), then if the slowdown occurs again, monitor top and see if it's really PostgreSQL that is slowing down, or perhaps some other process grabbing CPU time.