Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id CFF9B650123 for ; Wed, 10 Sep 2008 11:59:15 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 88059-02-6 for ; Wed, 10 Sep 2008 11:59:06 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gwmta.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by postgresql.org (Postfix) with ESMTP id 3C1C3650107 for ; Wed, 10 Sep 2008 11:59:04 -0300 (ADT) Received: from Courts-MTA by gwmta.wicourts.gov with Novell_GroupWise; Wed, 10 Sep 2008 09:59:01 -0500 Message-Id: <48C79A55.EE98.0025.0@wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 7.0.3 Date: Wed, 10 Sep 2008 09:58:45 -0500 From: "Kevin Grittner" To: ,, , "Matt Smiley" Subject: Re: too many clog files References: <48C5CC04.D078.0028.0@rentrak.com> <48C6F7A5.D078.0028.0@rentrak.com> In-Reply-To: <48C6F7A5.D078.0028.0@rentrak.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200809/106 X-Sequence-Number: 31419 > "Matt Smiley" 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