From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Whitney <swhitney@journyx.com>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_clog not getting cleared
Date: Wed, 22 Dec 2010 16:38:12 -0500
Message-ID: <10705.1293053892@sss.pgh.pa.us> (raw)
In-Reply-To: <21700506.3248.1293052359046.JavaMail.root@zimbra.int.journyx.com>
References: <21700506.3248.1293052359046.JavaMail.root@zimbra.int.journyx.com>
Scott Whitney <scott@journyx.com> writes:
> I understand the purpose of the clogs, but I would think that the transactions would have been frozen on all dbs (I've got about 300 in my cluster) by now. My logs go back to July 13th which, I think, is when the server was last restarted.
It doesn't really try to remove clog entries that are younger than
vacuum_freeze_table_age (see also vacuum_freeze_min_age). At two bits
per transaction, the general feeling is that eating the disk space is
better than forcing full-database vacuums more often. But if you're
hot to have the space released sooner, those are the knobs to frob.
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, swhitney@journyx.com, Kevin.Grittner@wicourts.gov
Subject: Re: pg_clog not getting cleared
In-Reply-To: <10705.1293053892@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