Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 2ED0A9F9D5B for ; Tue, 9 Oct 2007 14:44:56 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 29348-06 for ; Tue, 9 Oct 2007 14:44:50 -0300 (ADT) Received: from mx2.hub.org (mx2.hub.org [200.46.204.254]) by postgresql.org (Postfix) with ESMTP id 527269F9B95 for ; Tue, 9 Oct 2007 14:44:52 -0300 (ADT) X-Greylist: delayed 00:27:51.707662 by SQLgrey-1.7.5 Received: from mail.int.journyx.com (mail.journyx.com [66.219.41.227]) by mx2.hub.org (Postfix) with ESMTP id C1BD28B861E for ; Tue, 9 Oct 2007 14:44:18 -0300 (ADT) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.int.journyx.com (Postfix) with ESMTP id DBB613F23E3 for ; Tue, 9 Oct 2007 12:16:21 -0500 (CDT) X-Virus-Scanned: amavisd-new at 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 D0fMuIQipdVZ for ; Tue, 9 Oct 2007 12:16:16 -0500 (CDT) Received: from whitneys (dhcp-100-201.int.journyx.com [192.168.100.201]) by mail.int.journyx.com (Postfix) with ESMTP id E8AF83F2398 for ; Tue, 9 Oct 2007 12:16:15 -0500 (CDT) From: "Scott Whitney" To: Subject: PG 8.1.4 not clearing pg_clog Date: Tue, 9 Oct 2007 12:19:50 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Thread-Index: AcgKmJkLvJT3IwRlSAivyTx+CSZCcg== Message-Id: <20071009171615.E8AF83F2398@mail.int.journyx.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=BAYES_50=0.001 X-Spam-Level: X-Archive-Number: 200710/62 X-Sequence-Number: 26976 I've seen several posts on this issue in the past, but none seems to address my situation. In my pg_clog directory, I have 225 files dating back to August 8th, when I installed this PostgreSQL server. In my pg_xlog directory, I have 128 files dating back to October 8th. Autovacuum is on. Settings are as follows: autovacuum = on # enable autovacuum subprocess? autovacuum_naptime = 3 # time between autovacuum runs, in secs autovacuum_vacuum_threshold = 400 # min # of tuple updates before # vacuum autovacuum_analyze_threshold = 200 # min # of tuple updates before # analyze autovacuum_vacuum_scale_factor = 0.2 # fraction of rel size before # vacuum autovacuum_analyze_scale_factor = 0.1 # fraction of rel size before # analyze Using: SELECT datname, age(datfrozenxid) FROM pg_database order by age; The ages of my frozenxids are in a range from: 6/9/1977 (this is strange..I have 4 dbs listing that, including template0 and 2 of my own. The difference of those databases is that those 3 (not including template0) are owned by a different user. Then a range from 1/11/2004 through 6/2/2004. There are 217 of these. Specifically, some examples are: datname | age -------------------+------------ template0 | 234824829 postgres | 1073922288 template1 | 1073923008 Which I assume to be epoch dates and thusly converted. If "today" is Saturday, a cronjob runs this command runs on each database: PGCMD = 'vacuumdb -f -v -z %s' where %s is each database in the system. I don't have the log at the moment to prove it ran Saturday, but, yeah it does. So... I'm performing a full vacuum on each database in the system every Saturday. My pg_clog files date back to August 8th. What am I doing wrong? Thanks, Scott Whitney Journyx, Inc.