Re: High load on commit after important schema changes

From: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: High load on commit after important schema changes
Date: 2009-08-28 16:48:55
Message-ID: 20090828164855.GA21766@depesz.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Aug 28, 2009 at 12:47:15PM -0400, Tom Lane wrote:
> hubert depesz lubaczewski <depesz(at)depesz(dot)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(at)depesz(dot)com / aim:depeszhdl / skype:depesz_hdl / gg:6749007

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Edwin Plauchu 2009-08-28 16:52:53 Re: details locks
Previous Message Tom Lane 2009-08-28 16:47:15 Re: High load on commit after important schema changes