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 6AB6652832 for ; Wed, 20 Jul 2005 02:11:37 -0300 (ADT) 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 72069-10 for ; Wed, 20 Jul 2005 05:11:34 +0000 (GMT) Received: from mr2.surnet.cl (smtp2.surnet.cl [216.155.73.163]) by svr1.postgresql.org (Postfix) with ESMTP id AD7A252814 for ; Wed, 20 Jul 2005 02:11:32 -0300 (ADT) Received: from smtp2.surnet.cl (216.155.73.169) by mr2.surnet.cl (7.0.031.3) id 4259ADFA016C5A82; Wed, 20 Jul 2005 01:10:25 -0400 Received: from smtp2.surnet.cl (mr2.surnet.cl []) by mr2.surnet.cl ([216.155.73.169]); Wed, 20 Jul 2005 05:10:25 +0000 Received: from cluster.surnet.cl (216.155.73.164) by smtp2.surnet.cl (7.0.031.3) id 4259ADE300DE9DEB; Wed, 20 Jul 2005 01:10:25 -0400 Received: from alvh.no-ip.org (200.85.218.66) by cluster.surnet.cl (7.0.043) (authenticated as alvherre@surnet.cl) id 42B3EF600047B3FB; Wed, 20 Jul 2005 01:10:47 -0400 Received: by alvh.no-ip.org (Postfix, from userid 1000) id 3D011C3711D; Wed, 20 Jul 2005 01:11:15 -0400 (CLT) Date: Wed, 20 Jul 2005 01:11:15 -0400 From: Alvaro Herrera To: Tom Lane Cc: FM , Mailing List Postgres-Admin Subject: Re: PGSQL 7.4.8 : idle in transaction problem Message-ID: <20050720051115.GA19849@alvh.no-ip.org> References: <42DD5955.8000501@lexum.umontreal.ca> <11430.1121827475@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <11430.1121827475@sss.pgh.pa.us> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.388 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, FORGED_RCVD_HELO, RCVD_IN_NJABL_PROXY X-Spam-Level: * X-Archive-Number: 200507/139 X-Sequence-Number: 18195 On Tue, Jul 19, 2005 at 10:44:35PM -0400, Tom Lane wrote: > If it's a matter of whether VACUUM removes rows or not, that's expected: > open-transaction bookkeeping is done across the whole cluster. (This is > not something simple to change, since we may have to consider > transaction IDs in shared catalogs.) I wonder if this restriction could be lifted if we tracked last-vacuum- Xid per relation? -- Alvaro Herrera () "Cuando maņana llegue pelearemos segun lo que maņana exija" (Mowgli)