On 29/06/10 15:01, Sachin Kumar wrote:
> At times we have observed that postgres stops responding for several
> minutes, even couldn't fetch the number of entries in a particular
> table.
Quick guess: checkpoints. Enable checkpoint logging, follow the logs,
see if there's any correspondance.
In
We did see a small spike in disk I/O, but only had wait I/O for less than 10
seconds total. The low CPU idle event goes on for several minutes, wait I/O or
heavier I/O does not correlate to the extended period.
System time does jump up at the same time as the user time. System times of 15%
when
Hi,
We are using postgresql-8.4.0 on 64-bit Linux machine (open-SUSE 11.x).
It's a master/slave deployment & slony-2.0.4.rc2 is used for DB
replication on the slave box.
At times we have observed that postgres stops responding for several
minutes, even couldn't fetch the number of entries i
