From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Anjan Dave" <adave(at)vantage(dot)com> |
Cc: | "Rod Taylor" <pg(at)rbt(dot)ca>, "Postgresql Performance" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: can't handle large number of INSERT/UPDATEs |
Date: | 2004-10-26 21:53:14 |
Message-ID: | 13823.1098827594@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
"Anjan Dave" <adave(at)vantage(dot)com> writes:
> None of the locks are in state false actually.
In that case you don't have a locking problem.
> I don't have iostat on that machine, but vmstat shows a lot of writes to
> the drives, and the runnable processes are more than 1:
I get the impression that you are just saturating the write bandwidth of
your disk :-(
It's fairly likely that this happens during checkpoints. Look to see if
the postmaster has a child that shows itself as a checkpointer in "ps"
when the saturation is occurring. You might be able to improve matters
by altering the checkpoint frequency parameters (though beware that
either too small or too large will likely make matters even worse).
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Anjan Dave | 2004-10-26 22:14:10 | Re: can't handle large number of INSERT/UPDATEs |
Previous Message | Anjan Dave | 2004-10-26 21:15:49 | Re: can't handle large number of INSERT/UPDATEs |