Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id A953F1337BDD
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Thu, 10 Mar 2011 11:48:18 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia,
	port 10024) with ESMTP id 28637-02 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Thu, 10 Mar 2011 15:48:11 +0000 (UTC)
X-Greylist: from auto-whitelisted 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 D2D8A133655C
	for <pgsql-admin@postgresql.org>; Thu, 10 Mar 2011 11:48:10 -0400 (AST)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mail.int.journyx.com (Postfix) with ESMTP id 88F34FC012;
	Thu, 10 Mar 2011 09:48:10 -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 AwvpWQLTGr4l; Thu, 10 Mar 2011 09:47:36 -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 28BE7FC005;
	Thu, 10 Mar 2011 09:47:25 -0600 (CST)
Date: Thu, 10 Mar 2011 09:47:24 -0600 (CST)
From: Scott Whitney <scott@journyx.com>
Reply-To: Scott Whitney <swhitney@journyx.com>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Scott Whitney <swhitney@journyx.com>, pgsql-admin@postgresql.org,
	Kenneth Marshall <ktm@rice.edu>
Message-ID: <7423332.14202.1299772044088.JavaMail.root@zimbra.int.journyx.com>
In-Reply-To: 
 <27682685.14194.1299771826678.JavaMail.root@zimbra.int.journyx.com>
Subject: Re: pg_clogs hanging around
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
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.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201103/122
X-Sequence-Number: 36994

> > This is also interesting. I just allowed connections to template0
> > for the express purpose of vacuuming it, did a full vac on
> > template0, and that did NOT clear up the hanging clogs.
> 
> Was it a VACUUM FREEZE followed by a CHECKPOINT? Did you also cover
> that new database?

Yes, yes and yes, actually. Unless I did it wrong, which is always a strong possibility. Especially early in the morning...

pg statement: update pg_database set datallowconn=true where datname='template0';
shell: vacuumdb -f -v -z -F template0
pg statement: checkpoint;
pg statement: update pg_database set datallowconn=true where datname='template0';

Like I said, I'm beginning to believe that something is rotten wrt my Saturday vacs...