Carlos Moreno skrev:
The system does very frequent insertions and updates --- the longest table has, perhaps, some 20 million rows, and it's indexed (the primary key is the combination of two integer fields). This longest table only has inserts (and much less frequent selects), at a peak rate of maybe one or a few insertions per second.
One or a few inserts per second doesn't sound like that much. I would have expected it to work. If you can you might want to group several inserts into a single transaction.
A standard hint is also to move the WAL onto its own disk. Or get a disk controller with battery backed up ram.
But it's hard to say from your description what the bottleneck is and thus hard to give any advice.
Any help/tips/guidance in troubleshooting this issue? It will be much appreciated!
You could try to find specific queries that are slow. Pg can for example log queries for you that run for longer than X seconds.
/Dennis
