Received: from maia.hub.org (maia-5.hub.org [200.46.204.29])
	by mail.postgresql.org (Postfix) with ESMTP id 4EB501337BB7
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Thu, 10 Mar 2011 09:47:37 -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 10049-10 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Thu, 10 Mar 2011 13:47:28 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from mh4.mail.rice.edu (mh4.mail.rice.edu [128.42.199.11])
	by mail.postgresql.org (Postfix) with ESMTP id A58391337B97
	for <pgsql-admin@postgresql.org>; Thu, 10 Mar 2011 09:47:25 -0400 (AST)
Received: from mh4.mail.rice.edu (localhost.localdomain [127.0.0.1])
	by mh4.mail.rice.edu (Postfix) with ESMTP id E80D928FDC7;
	Thu, 10 Mar 2011 07:47:25 -0600 (CST)
X-Virus-Scanned: by amavis-2.6.4 at mh4.mail.rice.edu, auth channel
Received: from mh4.mail.rice.edu ([127.0.0.1])
	by mh4.mail.rice.edu (mh4.mail.rice.edu [127.0.0.1]) (amavis,
	port 10026)
	with ESMTP id LwGu80RdRWCq; Thu, 10 Mar 2011 07:47:25 -0600 (CST)
X-SMTP-Auth: no
X-SMTP-Auth: no
Received: from aart.is.rice.edu (aart.is.rice.edu [168.7.56.48])
	by mh4.mail.rice.edu (Postfix) with ESMTP id BA72028FDC6;
	Thu, 10 Mar 2011 07:47:25 -0600 (CST)
Received: by aart.is.rice.edu (Postfix, from userid 18612)
	id A92E12D5A6; Thu, 10 Mar 2011 07:47:24 -0600 (CST)
Date: Thu, 10 Mar 2011 07:47:23 -0600
From: Kenneth Marshall <ktm@rice.edu>
To: Scott Whitney <swhitney@journyx.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_clogs hanging around
Message-ID: <20110310134723.GX8169@aart.is.rice.edu>
References: <358079.14070.1299761935620.JavaMail.root@zimbra.int.journyx.com>
	<11997393.14072.1299762070874.JavaMail.root@zimbra.int.journyx.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <11997393.14072.1299762070874.JavaMail.root@zimbra.int.journyx.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201103/112
X-Sequence-Number: 36984

On Thu, Mar 10, 2011 at 07:01:10AM -0600, Scott Whitney wrote:
> Ooops...I accidentally took this off list, as Kevin was nice enough to point out.
> 
> 
> >> What am I looking for? 
> 
> >Outliers. 
> 
> > Yeah. It's just those 2. I'd assume that the db I created
> > yesterday would be an outlier, but template0 has been there all along
> > (of course) and is still listed as 648, a significantly smaller number. 
> 
> 
> >> The output shows me 345 rows, most of which are 132xxxxx numbers. 
> >> Two of them (template0 and a database created yesterday) say 648. 
> 
> >The template0 database is what's keeping the clog files from being 
> >cleaned up, but I guess the big question is why you care. They will 
> >go away eventually, and shouldn't affect performance. Are they 
> >taking enough space to merit extraordinary effort to clean them up? 
> > -Kevin 
> 
> 
> My concern is that when we had a failure a few years ago, and one of the clog files went bad. I had to manually recreate some customer data after bringing up the previous backup. So, I'd rather have them not there, because, well, if there are 200 of them in the dir, there's a higher chance in a case of a crash that one goes bad than if I have 15. 
> 
> Would adding -f (full) clean these up? I seem to recall it did in earlier versions. I've added the -F to it already, and that didn't seem to help. 
> 

If you have hardware problems like that you have way more problems.
You could have corruption (silent) occurring in any of the other database
files. Good luck.

Cheers,
Ken