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 22:06:40
Message-ID: 1849.1251497200@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:47:15PM -0400, Tom Lane wrote:
>> 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.

> Do you have any idea on how (easily) to test if this is the cause of the
> situation?

Well, if you have something like oprofile it would probably prove or
disprove the theory that sinvaladt.c is taking all the time.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alban Hertroys 2009-08-29 11:31:50 Re: Question on round-robin partitioning
Previous Message Werner Echezuria 2009-08-28 19:50:40 C function doesn't return more than one tuple