From: Tom Lane <tgl@sss.pgh.pa.us>
To: bock@openit.de
Cc: pgsql-performance@postgresql.org
Subject: Re: long wait times in ProcessCatchupEvent()
Date: Wed, 29 Dec 2010 10:18:41 -0500
Message-ID: <10249.1293635921@sss.pgh.pa.us> (raw)
In-Reply-To: <lptyhw1wml.fsf@warpcore.i.openit.de>
References: <lptyhw1wml.fsf@warpcore.i.openit.de>
bock@openit.de (Julian v. Bock) writes:
> 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 is fixed in 8.4 and up.
http://archives.postgresql.org/pgsql-committers/2008-06/msg00227.php
If you aren't willing to move off 8.3 you might be able to ameliorate
the problem by reducing the volume of catalog changes, but that can be
pretty hard if you're dependent on temp tables.
regards, tom lane
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: tgl@sss.pgh.pa.us, bock@openit.de
Subject: Re: long wait times in ProcessCatchupEvent()
In-Reply-To: <10249.1293635921@sss.pgh.pa.us>
* 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