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 11262528BB for ; Wed, 20 Jul 2005 10:35:41 -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 74803-06 for ; Wed, 20 Jul 2005 13:35:22 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 7664352835 for ; Wed, 20 Jul 2005 10:35:22 -0300 (ADT) 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 j6KDZLhj015466; Wed, 20 Jul 2005 09:35:21 -0400 (EDT) To: Alvaro Herrera Cc: FM , Mailing List Postgres-Admin Subject: Re: PGSQL 7.4.8 : idle in transaction problem In-reply-to: <20050720051115.GA19849@alvh.no-ip.org> References: <42DD5955.8000501@lexum.umontreal.ca> <11430.1121827475@sss.pgh.pa.us> <20050720051115.GA19849@alvh.no-ip.org> Comments: In-reply-to Alvaro Herrera message dated "Wed, 20 Jul 2005 01:11:15 -0400" Date: Wed, 20 Jul 2005 09:35:21 -0400 Message-ID: <15465.1121866521@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: 200507/153 X-Sequence-Number: 18209 Alvaro Herrera writes: > 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? No, that's unrelated. What is of concern is the open-transaction horizon. We could tighten things up by keeping a more complicated set of information in the PGPROC array --- rather than advertising a single transaction XMIN, each transaction would have to calculate and advertise both a "global" XMIN and a "local" XMIN (the latter counting only open transactions within your own database). This would then allow a more refined calculation in GetOldestXmin(). I'm inclined to think that the benefit wouldn't be worth the distributed cost of doing this in every GetSnapshotData() call ... regards, tom lane