From: Brad Nicholson <bnichols@ca.afilias.info>
To: Mailing List Postgres-Admin <pgsql-admin@postgresql.org>
Subject: Re: PGSQL 7.4.8 : idle in transaction problem
Date: Thu, 21 Jul 2005 10:46:25 -0400
Message-ID: <42DFB541.2060901@ca.afilias.info> (raw)
In-Reply-To: <15465.1121866521@sss.pgh.pa.us>
References: <42DD5955.8000501@lexum.umontreal.ca>
<11430.1121827475@sss.pgh.pa.us>
<20050720051115.GA19849@alvh.no-ip.org>
<15465.1121866521@sss.pgh.pa.us>
Tom Lane wrote:
>Alvaro Herrera <alvherre@alvh.no-ip.org> 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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: bnichols@ca.afilias.info
Subject: Re: PGSQL 7.4.8 : idle in transaction problem
In-Reply-To: <42DFB541.2060901@ca.afilias.info>
References: <42DD5955.8000501@lexum.umontreal.ca> <11430.1121827475@sss.pgh.pa.us> <20050720051115.GA19849@alvh.no-ip.org> <15465.1121866521@sss.pgh.pa.us> <42DFB541.2060901@ca.afilias.info>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox