X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 554D39FA2F8 for ; Tue, 9 May 2006 17:47:34 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 19333-09 for ; Tue, 9 May 2006 17:47:25 -0300 (ADT) X-Greylist: delayed 00:43:59.218207 by SQLgrey- Received: from eastrmmtai09.cox.net (eastrmmtai09.cox.net [68.230.240.50]) by postgresql.org (Postfix) with ESMTP id 3BED19F9C9E for ; Tue, 9 May 2006 17:47:24 -0300 (ADT) Received: from eastrmwml05.mgt.cox.net ([172.18.52.68]) by eastrmmtao02.cox.net (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP id <20060509200315.CFTR15470.eastrmmtao02.cox.net@eastrmwml05.mgt.cox.net> for ; Tue, 9 May 2006 16:03:15 -0400 Message-ID: <15254425.1147204995912.JavaMail.root@eastrmwml05.mgt.cox.net> Date: Tue, 9 May 2006 16:03:14 -0400 From: To: pgsql-admin@postgresql.org Subject: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) Sensitivity: Normal X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.178 tagged_above=0 required=5 tests=BAYES_00, MISSING_SUBJECT, NO_REAL_NAME X-Spam-Level: X-Archive-Number: 200605/88 X-Sequence-Number: 21620 Everyone, I had an odd situation occur this morning with PGSQL 7.4 run on Red Hat Enterprise 4 (update 3) and could really use some wisdom. ... Single postmaster running. ... vacuum full is run every night as part of a cron job ... At start, data files consume about 28 GB ... This morning I dropped the database and reloaded from current backup ... New instance consumes about 6 GB I can only assume that the database was not compacted, but I thought vacuum full performed that function along with tuple maintenance. Can anyone expound on the problem and suggest a solution other than dropping and reloading the database? Thanks in advance