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 1623B53A1C for ; Fri, 1 Apr 2005 22:23:57 +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 64234-05 for ; Fri, 1 Apr 2005 21:23:53 +0000 (GMT) Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by svr1.postgresql.org (Postfix) with ESMTP id 5F96953A12 for ; Fri, 1 Apr 2005 22:23:52 +0100 (BST) Received: from sj-core-3.cisco.com (171.68.223.137) by sj-iport-4.cisco.com with ESMTP; 01 Apr 2005 13:23:55 -0800 Received: from cjwhitew2k02 ([128.107.172.206]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j31LNpgS000922; Fri, 1 Apr 2005 13:23:52 -0800 (PST) Message-Id: <200504012123.j31LNpgS000922@sj-core-3.cisco.com> Reply-To: From: "Chris White (cjwhite)" To: "'Tom Lane'" Cc: Subject: Re: Help understanding VACUUM info on 7.4.5 Date: Fri, 1 Apr 2005 13:23:52 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <28606.1112389598@sss.pgh.pa.us> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 thread-index: AcU2/yVIfd4IpR1fSmaZqxTBKqRDNwAAUokA X-PMX-Version: 4.7.0.111621 X-from-outside-Cisco: [128.107.172.206] X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.288 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE X-Spam-Level: X-Archive-Number: 200504/23 X-Sequence-Number: 17036 Does this mean it could be any transaction, even one that has not done anything with large objects, but one that started prior to the large objects being deleted? All access to the DB is done via JDBC, so has this JDBC issue been fixed in 7.4.5? Chris -----Original Message----- From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Tom Lane Sent: Friday, April 01, 2005 1:07 PM To: cjwhite@cisco.com Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Help understanding VACUUM info on 7.4.5 "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 ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster