Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 0FCA39FC1E6 for ; Fri, 18 May 2007 11:40:56 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 59741-05 for ; Fri, 18 May 2007 11:40:52 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mail.digitalfreaks.org (arbitor.digitalfreaks.org [216.151.95.158]) by postgresql.org (Postfix) with ESMTP id EE9379FB688 for ; Fri, 18 May 2007 11:40:52 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by mail.digitalfreaks.org (Postfix) with ESMTP id 45E5C1729F; Fri, 18 May 2007 10:40:51 -0400 (EDT) Received: from mail.digitalfreaks.org ([127.0.0.1]) by localhost (mail.digitalfreaks.org [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 14002-05; Fri, 18 May 2007 10:40:49 -0400 (EDT) Received: from soundwave.pgh.priv.collaborativefusion.com (pr40.pitbpa0.pub.collaborativefusion.com [206.210.89.202]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.digitalfreaks.org (Postfix) with ESMTP id 743EB1728B; Fri, 18 May 2007 10:40:49 -0400 (EDT) Subject: Re: Frequent pg_clog on system From: "Brian A. Seklecki" To: Stephane Bailliez Cc: pgsql-admin@postgresql.org In-Reply-To: <464D7B05.4040109@gmail.com> References: <464D7B05.4040109@gmail.com> Content-Type: text/plain Date: Fri, 18 May 2007 10:40:48 -0400 Message-Id: <1179499248.41472.212.camel@soundwave.pgh.priv.collaborativefusion.com> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.2 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/190 X-Sequence-Number: 25510 Anything in /var/log/messages at this time? Try turning up the debugging for transaction logging? ~BAS On Fri, 2007-05-18 at 12:08 +0200, Stephane Bailliez wrote: > n after a sql query performs a long scan of table A or B. > That's very weird since each time it seems to happen after performing > more or less the same query several times (trial and error narrowing > them data) and suddenly I have this error happening and I'm cooked > (fwiw, there is no insert/update happening at all during this period, > only select and a single user) > > Anyone has any idea what could be the cause of this ? It's a bit too > recurrent to me and it's a definite annoyance.