"Palle Girgensohn" <girgen@pingpong.net> writes:
> Are there any other things I can modify?
You might consider an index on <userid,when>. Keep in mind that every new
index imposes an incremental cost on every update and insert and increases the
time for vacuum.
> max_prepared_transactions = 100 # can be 0 or more
Are you actually using prepared transactions (are you synchronising multiple
databases using a transaction manager)? If not then set this to 0 as it takes
some resources.
> maintenance_work_mem = 16384 # min 1024, size in KB
Raising this might decrease vacuum times if that's a problem.
> fsync = off
You realize that this means if the system loses power or the kernel crashes
you could have data corruption? Do you take very frequent backups or can you
reconstruct your data?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!