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

From Tom Lane
Subject Re: High load on commit after important schema changes
Date
Msg-id 1849.1251497200@sss.pgh.pa.us
Whole thread Raw
In response to Re: High load on commit after important schema changes  (hubert depesz lubaczewski <depesz@depesz.com>)
List pgsql-general
hubert depesz lubaczewski <depesz@depesz.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

pgsql-general by date:

Previous
From: Werner Echezuria
Date:
Subject: C function doesn't return more than one tuple
Next
From: Steven Lembark
Date:
Subject: Question on round-robin partitioning