pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Benjamin Krajmalnik <kraj@illumen.com>
Cc: pgsql-admin@postgresql.org, Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Matthew T. O'Connor <matthew@zeut.net>
Subject: Re: pg_clog questions
Date: Thu, 25 May 2006 16:20:44 -0400
Message-ID: <15596.1148588444@sss.pgh.pa.us> (raw)
In-Reply-To: <8511B4970E0D124898E973DF496F9B432516E3@stash.stackdump.local>
References: <8511B4970E0D124898E973DF496F9B432516E3@stash.stackdump.local>

"Benjamin Krajmalnik" <kraj@illumen.com> writes:
>>> While checking our server, I noticed quite a few files in the pg_clog
>>> directory.
>>> Is there a maintenance task which can be run to purge the files which
>>> are no longer needed?

>> VACUUM.  If they're not disappearing, you aren't running an adequate
>> vacuum regime --- missing out some databases, perhaps?

> I have autovacuum turned on with the default settings.

Hm.  I believe that autovac only does database-wide vacuums when it
thinks they're necessary to prevent transaction wraparound failures.
Which would mean that it'd let pg_clog grow to something on the order
of half a gig before any truncation would happen.  That's probably
insufficiently aggressive :-(

Alvaro, Matthew, any thoughts about improving that?  It strikes me that
Alvaro's work-in-progress on maintaining per-table xmin info would allow
truncation of clog without actually insisting on a database-wide VACUUM,
but that's not going to be any help for existing releases.

			regards, tom lane



view thread (12+ messages)  latest in thread

Message-ID: <15596.1148588444@sss.pgh.pa.us>
Permalink:  ../15596.1148588444@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/15596.1148588444@sss.pgh.pa.us

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, kraj@illumen.com, alvherre@alvh.no-ip.org, matthew@zeut.net
  Subject: Re: pg_clog questions
  In-Reply-To: <15596.1148588444@sss.pgh.pa.us>
  References: <8511B4970E0D124898E973DF496F9B432516E3@stash.stackdump.local> <15596.1148588444@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