DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=wa59fDeWpWvn3gPFmg0/bP3ms+PEJmyn2XkXJ6OcgV9jk6sZ244Y7Xt0aro3Wmt0sq
	DzehLBg1gHSfjCJDIm1ka2UmviHMRSNewb1RtWdPjNTJ2vjc4CJ07BWWVBP21Qd3hLBB
	KaWrFo+Bhde+42EkV3SZpS+XaOgC+18IEHBJg=
Message-ID: <dcc563d10809101018u1f77199bpcc134121d7d040ad@mail.gmail.com>
Date: Wed, 10 Sep 2008 11:18:02 -0600
From: "Scott Marlowe" <scott.marlowe@gmail.com>
To: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Subject: Re: too many clog files
Cc: alvherre@commandprompt.com, duanlg@nec-as.nec.com.cn,
	pgsql-performance@postgresql.org, "Matt Smiley" <mss@rentrak.com>
In-Reply-To: <48C79A55.EE98.0025.0@wicourts.gov>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <48C5CC04.D078.0028.0@rentrak.com>
	<48C6F7A5.D078.0028.0@rentrak.com> <48C79A55.EE98.0025.0@wicourts.gov>

On Wed, Sep 10, 2008 at 8:58 AM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
>> "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.

I have a pretty high volume server that's been online for one month
and it had somewhere around 53, going back in order to 0000, and it
was recently vacuumdb -az 'ed. Running another one.  No long running
transactions, etc...