Re: PGSQL 7.4.8 : idle in transaction problem - Mailing list pgsql-admin

From Brad Nicholson
Subject Re: PGSQL 7.4.8 : idle in transaction problem
Date
Msg-id 42DFB541.2060901@ca.afilias.info
Whole thread Raw
In response to Re: PGSQL 7.4.8 : idle in transaction problem  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PGSQL 7.4.8 : idle in transaction problem  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-admin
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.



pgsql-admin by date:

Previous
From: Alexander Stanier
Date:
Subject: Re: FATAL: could not read statistics message
Next
From: Bruce Momjian
Date:
Subject: Re: Statement logging per connection