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 27E5D535F8 for ; Fri, 1 Apr 2005 22:07:43 +0100 (BST) 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 58347-09 for ; Fri, 1 Apr 2005 21:07:38 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 60D7C53247 for ; Fri, 1 Apr 2005 22:07:38 +0100 (BST) 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 j31L6cw0028607; Fri, 1 Apr 2005 16:06:38 -0500 (EST) To: cjwhite@cisco.com Cc: pgsql-admin@postgresql.org Subject: Re: Help understanding VACUUM info on 7.4.5 In-reply-to: <200504011940.j31JeT3S006624@sj-core-4.cisco.com> References: <200504011940.j31JeT3S006624@sj-core-4.cisco.com> Comments: In-reply-to "Chris White (cjwhite)" message dated "Fri, 01 Apr 2005 11:40:29 -0800" Date: Fri, 01 Apr 2005 16:06:38 -0500 Message-ID: <28606.1112389598@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200504/22 X-Sequence-Number: 17035 "Chris White (cjwhite)" writes: > Below I have info which shows a DB which has had all objects deleted and > then vacuumed. As can been seen it say it has "9014 dead rows that can't > been removed". What does that mean? That means there's an open transaction that is old enough to be able to see those rows under MVCC rules, so VACUUM dare not remove them. Check for clients that are issuing a BEGIN and then sitting with the transaction open. Older versions of JDBC did that behind your back, IIRC. regards, tom lane