From: Scott Whitney <scott@journyx.com>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Scott Whitney <swhitney@journyx.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_clog not getting cleared
Date: Wed, 22 Dec 2010 15:12:39 -0600 (CST)
Message-ID: <21700506.3248.1293052359046.JavaMail.root@zimbra.int.journyx.com> (raw)
In-Reply-To: <3773635.3245.1293052309856.JavaMail.root@zimbra.int.journyx.com>
I'm certain it was -f, not -F, since it's still in the script I use, albeit commented out.
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.
I'll try the -F on Sat and see if that resolves the issue. I'll also have logs available at that time, assuming all goes well.
Thanks for the advice.
Scott Whitney <scott@journyx.com> wrote:
> Each Saturday, I run: vacuumdb -a -v. I have autovac on all the
> time.
>
> However, my pg_clog directory lists clog files going back to
> July.
>
> This is pg 8.4.4 on Linux (CentOS 5.5).
>
> I know this isn't a whole lot of information at this time. What
> more would be useful in finding out what's failing and where?
Nothing is failing -- clog is needed to track what has committed
until transactions are "frozen".
> I seem to recall that doing vacuumdb -f -a -v resolved it
Are you sure that wasn't -F rather than -f ? The uppercase switch
freezes tuples, which would allow clog to be cleaned up. This
shouldn't normally be needed, unless you have some other reason to
need aggressive freezing.
-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-admin@postgresql.org
Cc: scott@journyx.com, Kevin.Grittner@wicourts.gov, swhitney@journyx.com
Subject: Re: pg_clog not getting cleared
In-Reply-To: <21700506.3248.1293052359046.JavaMail.root@zimbra.int.journyx.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