From: | Andrew Sullivan <ajs(at)commandprompt(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Load spikes on 8.1.11 |
Date: | 2008-07-21 22:13:59 |
Message-ID: | 20080721221359.GI32548@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jul 22, 2008 at 02:41:55AM +0530, Gurjeet Singh wrote:
> I am aware of the heavy locking involved with Slony, which should mean that
> it blocks the application connections; that's be completely acceptable,
> given all the warnings in the Slony docs. But what I am concerned about and
> trying to hunt down is why <IDLE> backend processes are all consuming up all
> of CPU (!!!) so much so that I am unable to fire up any new process!
Ah, well, then, yes, the spinlock improvements probably will help
you. But you should disabuse yourself of the idea that <IDLE>
processes have no cost. You still have to talk to all those
connections when doing schema changes.
A
--
Andrew Sullivan
ajs(at)commandprompt(dot)com
+1 503 667 4564 x104
http://www.commandprompt.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2008-07-21 22:15:53 | Re: Concurrent VACUUM and ANALYZE |
Previous Message | Jonah H. Harris | 2008-07-21 21:50:46 | Concurrent VACUUM and ANALYZE |