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 10347566AD for ; Wed, 16 Mar 2005 07:28:08 +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 66233-08 for ; Wed, 16 Mar 2005 07:27:49 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 5D52656646 for ; Wed, 16 Mar 2005 07:27:47 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j2G7RmRM003244; Wed, 16 Mar 2005 02:27:48 -0500 (EST) To: "Chris Hoover" Cc: pgsql-admin@postgresql.org Subject: Re: Vacuum questions In-reply-to: <423749C1.2030803@sermonaudio.com> References: <423749C1.2030803@sermonaudio.com> Comments: In-reply-to "Chris Hoover" message dated "Tue, 15 Mar 2005 15:46:57 -0500" Date: Wed, 16 Mar 2005 02:27:48 -0500 Message-ID: <3243.1110958068@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/236 X-Sequence-Number: 16734 "Chris Hoover" writes: > 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? Most likely, you had an open transaction lurking that was old enough that it could still "see" the deleted data, and so VACUUM couldn't safely reclaim the data. VACUUM's decisions about this are cluster-wide; so even though you'd recently created the database in question, a long-running transaction in another database under the same postmaster could still cause the problem. regards, tom lane