X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 9718C568D5 for ; Tue, 15 Mar 2005 20:46:27 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 15093-05 for ; Tue, 15 Mar 2005 20:46:22 +0000 (GMT) Received: from mail.astudios.com (ns1.astudios.com [66.49.77.3]) by svr1.postgresql.org (Postfix) with ESMTP id 36BFD56915 for ; Tue, 15 Mar 2005 20:46:20 +0000 (GMT) thread-index: AcUpoFaxsOT1DI8wSzi6zdwPOfuh9w== Received: from [10.4.13.50] ([66.194.26.150]) by mail.astudios.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 15 Mar 2005 15:48:27 -0500 Message-ID: <423749C1.2030803@sermonaudio.com> Content-Class: urn:content-classes:message Importance: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.181 Date: Tue, 15 Mar 2005 15:46:57 -0500 From: "Chris Hoover" User-Agent: Mozilla Thunderbird 0.8 (X11/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Subject: Vacuum questions Content-Type: text/plain; format=flowed; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 15 Mar 2005 20:48:27.0546 (UTC) FILETIME=[56AAAFA0:01C529A0] X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200503/231 X-Sequence-Number: 16729 Question on vacuuming. When you do a vacuum , are the "freed" tuples available only the table, or to the entire db, or to the entire cluster? The reason I'm asking is that we are getting ready to preform a major upgrade to our application that involves adding some new fields to almost every table and populating them. This is causing our test conversion db's to double in size (we are assuming that every update is causing a delete and re-insert behind the scenes due to the populating of the new columns). Anyway, we are working on trying to find the fastest way to recover the space. We have also had one test occurrence where after the upgrade, a vacuum full would not recover the space. However, when we bounced the postmaster, and then performed a vacuum full, the space was recovered. Any ideas on what might cause this? This happened on a newly restored db that was converted and then vacuumed full. There would have been no connections to the db after the conversion. PG 7.3.4 RH 2.1 Thanks, Chris