From: Craig James <craig_james@emolecules.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: long wait times in ProcessCatchupEvent()
Date: Wed, 29 Dec 2010 15:53:29 -0800
Message-ID: <4D1BC9F9.7060005@emolecules.com> (raw)
In-Reply-To: <304.1293652739@sss.pgh.pa.us>
References: <lptyhw1wml.fsf@warpcore.i.openit.de>
<4D1B8BD9.4060105@emolecules.com>
<304.1293652739@sss.pgh.pa.us>
On 12/29/10 11:58 AM, Tom Lane wrote:
> Craig James<craig_james@emolecules.com> writes:
>> On 12/29/10 6:28 AM, Julian v. Bock wrote:
>>> I have the problem that on our servers it happens regularly under a
>>> certain workload (several times per minute) that all backend processes
>>> get a SIGUSR1 and spend several seconds in ProcessCatchupEvent().
>
>> This sounds like the exact same problem I had on Postgres 8.3 and 8.4:
>
>> http://archives.postgresql.org/pgsql-performance/2010-04/msg00071.php
>
>> Updating to Postgres version 9 fixed it. Here is what appeared to be the best analysis of what was happening, but we never confirmed it.
>
>> http://archives.postgresql.org/pgsql-performance/2010-06/msg00464.php
>
> It happened for you on 8.4 too? In that previous thread you were still
> on 8.3. If you did see it on 8.4 then it wasn't sinval ...
My mistake - it was only 8.3.
Craig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: craig_james@emolecules.com, tgl@sss.pgh.pa.us
Subject: Re: long wait times in ProcessCatchupEvent()
In-Reply-To: <4D1BC9F9.7060005@emolecules.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox