pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Brian A. Seklecki <lavalamp@spiritual-machines.org>
To: Stephane Bailliez <sbailliez@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Frequent pg_clog on system
Date: Fri, 18 May 2007 10:40:48 -0400
Message-ID: <1179499248.41472.212.camel@soundwave.pgh.priv.collaborativefusion.com> (raw)
In-Reply-To: <464D7B05.4040109@gmail.com>
References: <464D7B05.4040109@gmail.com>

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.





view thread (6+ messages)  latest in thread

Message-ID: <1179499248.41472.212.camel@soundwave.pgh.priv.collaborativefusion.com>
Permalink:  ../1179499248.41472.212.camel@soundwave.pgh.priv.collaborativefusion.com/
Also on:    postgresql.org/message-id/1179499248.41472.212.camel@soundwave.pgh.priv.collaborativefusion.com

 · 

reply

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-admin@postgresql.org
  Cc: lavalamp@spiritual-machines.org, sbailliez@gmail.com
  Subject: Re: Frequent pg_clog on system
  In-Reply-To: <1179499248.41472.212.camel@soundwave.pgh.priv.collaborativefusion.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