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 F3C5A5298B for ; Thu, 21 Jul 2005 11:46:31 -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 79407-05 for ; Thu, 21 Jul 2005 14:46:22 +0000 (GMT) Received: from mail.libertyrms.com (unknown [207.219.45.62]) by svr1.postgresql.org (Postfix) with ESMTP id E22F952AC5 for ; Thu, 21 Jul 2005 11:46:20 -0300 (ADT) Received: from dba5.int.libertyrms.com ([10.1.3.44]) by mail.libertyrms.com with esmtp (Exim 4.22) id 1DvcJd-0008Cz-8r for pgsql-admin@postgresql.org; Thu, 21 Jul 2005 10:46:25 -0400 Message-ID: <42DFB541.2060901@ca.afilias.info> Date: Thu, 21 Jul 2005 10:46:25 -0400 From: Brad Nicholson User-Agent: Mozilla Thunderbird 0.8 (X11/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mailing List Postgres-Admin Subject: Re: PGSQL 7.4.8 : idle in transaction problem References: <42DD5955.8000501@lexum.umontreal.ca> <11430.1121827475@sss.pgh.pa.us> <20050720051115.GA19849@alvh.no-ip.org> <15465.1121866521@sss.pgh.pa.us> In-Reply-To: <15465.1121866521@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SA-Exim-Mail-From: bnichols@ca.afilias.info X-SA-Exim-Scanned: No; SAEximRunCond expanded to false X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.035 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200507/176 X-Sequence-Number: 18232 Tom Lane wrote: >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. > From a Slony-I users standpoint - the idle transactions cause pg_listener bloat, which can impact replication performance on busy sites. -- Brad Nicholson 416-673-4106 Database Administrator, Afilias Canada Corp.