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 AB9E453ACE for ; Fri, 1 Apr 2005 23:21:29 +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 79210-09 for ; Fri, 1 Apr 2005 22:21:26 +0000 (GMT) Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by svr1.postgresql.org (Postfix) with ESMTP id BD207533BA for ; Fri, 1 Apr 2005 23:21:22 +0100 (BST) Received: from sj-core-3.cisco.com (171.68.223.137) by sj-iport-5.cisco.com with ESMTP; 01 Apr 2005 14:21:25 -0800 Received: from cjwhitew2k02 ([128.107.172.206]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j31MLLgS024313; Fri, 1 Apr 2005 14:21:22 -0800 (PST) Message-Id: <200504012221.j31MLLgS024313@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 14:21:21 -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: <28891.1112392136@sss.pgh.pa.us> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 thread-index: AcU3BTtZe//glrb/TG6wA25LQSc2dQAA+DIQ 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.286 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE X-Spam-Level: X-Archive-Number: 200504/29 X-Sequence-Number: 17042 Thanks, for the input. -----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:49 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: > 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? Exactly. > All access to the DB is done via JDBC, so has this JDBC issue been > fixed in 7.4.5? You'd have to ask the JDBC guys ... regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster