Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 630481337B92 for ; Thu, 10 Mar 2011 11:18:18 -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 35260-08 for ; Thu, 10 Mar 2011 15:18:09 +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 6EBC31337B82 for ; Thu, 10 Mar 2011 11:18:07 -0400 (AST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.int.journyx.com (Postfix) with ESMTP id 4102FC4018; Thu, 10 Mar 2011 09:18:07 -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 iHA3xGyo9Qla; Thu, 10 Mar 2011 09:18:02 -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 846C1C4050; Thu, 10 Mar 2011 09:18:02 -0600 (CST) Date: Thu, 10 Mar 2011 09:18:02 -0600 (CST) From: Scott Whitney Reply-To: Scott Whitney To: Kenneth Marshall Cc: pgsql-admin@postgresql.org, Scott Whitney Message-ID: <31022840.14155.1299770282363.JavaMail.root@zimbra.int.journyx.com> In-Reply-To: <30674693.14151.1299770218945.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/120 X-Sequence-Number: 36992 > > > > > 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. > > > > > > > > I am, in fact, aware of that, but every single machine ever > > > > manufactured will have hardware problems such at this at some > > > > point. It stems quite simply from Ohm's Law, one gross > > > > over-simplification of which is as simple as "if it's got a > > > > resistor in it, it's going > > > > to fail at some point", as I'm sure you know. It's merely a > > > > matter of whether proactive replacement, backups, standby > > > > systems, etc > > > > ameliorate that risk. When we had our failure a couple of years > > > > ago, it did not. > > > > > > > > Regardless, my question still stands, and I do, in fact, care > > > > about ANY database blocking cleanup of clogs (or anything else). > > > > There's this concept of "if this then what else," and if > > > > template0 (or > > > > anyone else) is blocking that ability to properly clean those > > > > up, what else is possibly screwed up in a similar fashion. > > > > > > > > So, what can I do to resolve this issue? > > > > > > > > > > True, entropy rules. I think that you can use "VACUUM FREEZE" > > > to allow the clogs to be cleaned up. > > > > > I thought I was. I've got -F in there. vacuumdb -a -v -F > > > > Sorry about that, you are. I have never done it from the command-line > just from psql. I was thinking F for FULL... :) > 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. Thanks for the help so far, everyone. I'm going to assuming something is going wrong with my vacuuming on Saturdays (which I can't PROVE until my Saturday window), and take it from there. I'll reply next week with more info if needed.