Received: from maia.hub.org (maia-5.hub.org [200.46.204.29])
	by mail.postgresql.org (Postfix) with ESMTP id D07F21337B4F
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Tue, 21 Dec 2010 16:34:27 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024)
	with ESMTP id 76530-06 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Tue, 21 Dec 2010 20:34:21 +0000 (UTC)
X-Greylist: delayed 00:09:20.918444 by SQLgrey-1.7.6
Received: from mail.int.journyx.com (mail.journyx.com [66.219.41.227])
	by mail.postgresql.org (Postfix) with ESMTP id 516721337990
	for <pgsql-admin@postgresql.org>; Tue, 21 Dec 2010 16:34:20 -0400 (AST)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mail.int.journyx.com (Postfix) with ESMTP id 5CFA07E45A6
	for <pgsql-admin@postgresql.org>; Tue, 21 Dec 2010 14:24:58 -0600 (CST)
X-Virus-Scanned: amavisd-new at zimbra.int.journyx.com
Received: from mail.int.journyx.com ([127.0.0.1])
	by localhost (mail.int.journyx.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id yi9iDbesEcuQ for <pgsql-admin@postgresql.org>;
	Tue, 21 Dec 2010 14:24:53 -0600 (CST)
Received: from mail.int.journyx.com (zimbra.int.journyx.com [192.168.100.5])
	by mail.int.journyx.com (Postfix) with ESMTP id 3A25AC407B
	for <pgsql-admin@postgresql.org>; Tue, 21 Dec 2010 14:24:53 -0600 (CST)
Date: Tue, 21 Dec 2010 14:24:53 -0600 (CST)
From: Scott Whitney <scott@journyx.com>
Reply-To: Scott Whitney <swhitney@journyx.com>
To: pgsql-admin@postgresql.org
Message-ID: <3784661.2704.1292963093042.JavaMail.root@zimbra.int.journyx.com>
In-Reply-To: 
 <16384123.2701.1292963013966.JavaMail.root@zimbra.int.journyx.com>
Subject: pg_clog not getting cleared
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_2703_1683237.1292963093039"
X-Originating-IP: [192.168.100.188]
X-Mailer: Zimbra 6.0.6_GA_2331.RHEL4 (ZimbraWebClient - FF3.0
	(Win)/6.0.6_GA_2331.RHEL4)
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.909 tagged_above=-10 required=5
	tests=BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201012/151
X-Sequence-Number: 36380

------=_Part_2703_1683237.1292963093039
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Hello. I posted this once before, but I'm encountering it again. 

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? 

I seem to recall that doing vacuumdb -f -a -v resolved it, which would seem to point to a database not being vacuumed, but that's sort of the point of the -a switch, right? I'm running this as the "postgres" user himself. 



------=_Part_2703_1683237.1292963093039
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'>Hello. I posted this once before, but I'm encountering it again.<br><br>Each Saturday, I run: vacuumdb -a -v. I have autovac on all the time.<br><br>However, my pg_clog directory lists clog files going back to July.<br><br>This is pg 8.4.4 on Linux (CentOS 5.5).<br><br>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?<br><br>I seem to recall that doing vacuumdb -f -a -v resolved it, which would seem to point to a database not being vacuumed, but that's sort of the point of the -a switch, right? I'm running this as the "postgres" user himself.<br><br><br></div></body></html>
------=_Part_2703_1683237.1292963093039--