Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 26B5B1337B83 for ; Wed, 29 Dec 2010 19:53:45 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 79282-09 for ; Wed, 29 Dec 2010 23:53:38 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail-vw0-f46.google.com (mail-vw0-f46.google.com [209.85.212.46]) by mail.postgresql.org (Postfix) with ESMTP id C623A1337B88 for ; Wed, 29 Dec 2010 19:53:36 -0400 (AST) Received: by vws16 with SMTP id 16so4268746vws.19 for ; Wed, 29 Dec 2010 15:53:36 -0800 (PST) Received: by 10.220.203.75 with SMTP id fh11mr4548456vcb.91.1293666815417; Wed, 29 Dec 2010 15:53:35 -0800 (PST) Received: from Craig-Jamess-MacBook-Pro.local (cpe-76-176-215-35.san.res.rr.com [76.176.215.35]) by mx.google.com with ESMTPS id e10sm986695vch.43.2010.12.29.15.53.32 (version=SSLv3 cipher=RC4-MD5); Wed, 29 Dec 2010 15:53:34 -0800 (PST) Message-ID: <4D1BC9F9.7060005@emolecules.com> Date: Wed, 29 Dec 2010 15:53:29 -0800 From: Craig James User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Tom Lane CC: pgsql-performance@postgresql.org Subject: Re: long wait times in ProcessCatchupEvent() References: <4D1B8BD9.4060105@emolecules.com> <304.1293652739@sss.pgh.pa.us> In-Reply-To: <304.1293652739@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.6 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7 X-Spam-Level: X-Archive-Number: 201012/330 X-Sequence-Number: 41782 On 12/29/10 11:58 AM, Tom Lane wrote: > Craig James 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