X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 183A9D1CCE0 for ; Mon, 24 Nov 2003 17:45:03 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 75930-10 for ; Mon, 24 Nov 2003 13:44:31 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id B0AECD1C96C for ; Mon, 24 Nov 2003 13:44:30 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id hAOHiU19021400; Mon, 24 Nov 2003 12:44:30 -0500 (EST) To: Rajesh Kumar Mallah Cc: pgsql-performance@postgresql.org Subject: Re: VACUUM problems with 7.4 In-reply-to: <200311242243.59296.mallah@trade-india.com> References: <200311242243.59296.mallah@trade-india.com> Comments: In-reply-to Rajesh Kumar Mallah message dated "Mon, 24 Nov 2003 22:43:59 +0530" Date: Mon, 24 Nov 2003 12:44:30 -0500 Message-ID: <21399.1069695870@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/211 X-Sequence-Number: 4771 Rajesh Kumar Mallah writes: > I am sure there is no transaction open with the table banner_stats2. > Still VACUUM FULL does not seems to effective in removing the > dead rows. That is not the issue --- the limiting factor is what is your oldest open transaction, period. Whether it has yet looked at this table is not relevant, because the system has no way to know whether it might decide to do so later. regards, tom lane