Re: High load on commit after important schema changes

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

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.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message hubert depesz lubaczewski 2009-08-28 16:48:55 Re: High load on commit after important schema changes
Previous Message hubert depesz lubaczewski 2009-08-28 16:44:36 Re: High load on commit after important schema changes