From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: alvherre@commandprompt.com
To: duanlg@nec-as.nec.com.cn
To: pgsql-performance@postgresql.org
To: Matt Smiley <mss@rentrak.com>
Subject: Re: too many clog files
Date: Wed, 10 Sep 2008 09:58:45 -0500
Message-ID: <48C79A55.EE98.0025.0@wicourts.gov> (raw)
In-Reply-To: <48C6F7A5.D078.0028.0@rentrak.com>
References: <48C5CC04.D078.0028.0@rentrak.com>
<48C6F7A5.D078.0028.0@rentrak.com>
> "Matt Smiley" <mss@rentrak.com> wrote:
> Alvaro Herrera wrote:
>> Move the old clog files back where they were, and run VACUUM FREEZE
in
>> all your databases. That should clean up all the old pg_clog files,
if
>> you're really that desperate.
>
> Has anyone actually seen a CLOG file get removed under 8.2 or 8.3?
Some of my high-volume databases don't quite go back to 0000, but this
does seem to be a problem. I have confirmed that VACUUM FREEZE on all
but template0 (which doesn't allow connections) does not clean them
up. No long running transactions are present.
-Kevin
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-performance@postgresql.org
Cc: Kevin.Grittner@wicourts.gov, alvherre@commandprompt.com, duanlg@nec-as.nec.com.cn, mss@rentrak.com
Subject: Re: too many clog files
In-Reply-To: <48C79A55.EE98.0025.0@wicourts.gov>
* 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