Re: High load on commit after important schema changes - Mailing list pgsql-general

From hubert depesz lubaczewski
Subject Re: High load on commit after important schema changes
Date
Msg-id 20090828164855.GA21766@depesz.com
Whole thread Raw
In response to Re: High load on commit after important schema changes  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Fri, Aug 28, 2009 at 12:47:15PM -0400, Tom Lane wrote:
> hubert depesz lubaczewski <depesz@depesz.com> writes:
> > On Fri, Aug 28, 2009 at 12:28:06PM -0400, Tom Lane wrote:
> >> Hm, do you have forty or so idle backends hanging around while this
> >> happens?  The only thing I can think of that might be causing this is
> >> shared cache invalidation messages being broadcast to all the other
> >> sessions.
> > I have about 1000 backends running.
> Ouch.  You need to update to 8.4 --- the SI messaging stuff will
> definitely be hurting you with that many backends.  Or consider
> using connection pooling or something to cut the number of backends.

thanks. it looks like i will not be spared this fun :)

Best regards,

depesz

--
Linkedin: http://www.linkedin.com/in/depesz  /  blog: http://www.depesz.com/
jid/gtalk: depesz@depesz.com / aim:depeszhdl / skype:depesz_hdl / gg:6749007

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: High load on commit after important schema changes
Next
From: Edwin Plauchu
Date:
Subject: Re: details locks