Skip site navigation (1) Skip section navigation (2)

Re: PGSQL 7.4.8 : idle in transaction problem

From: Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info>
To: Mailing List Postgres-Admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: PGSQL 7.4.8 : idle in transaction problem
Date: 2005-07-21 14:46:25
Message-ID: 42DFB541.2060901@ca.afilias.info (view raw or flat)
Thread:
Lists: pgsql-admin
Tom Lane wrote:

>Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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.



In response to

Responses

pgsql-admin by date

Next:From: Bruce MomjianDate: 2005-07-21 14:50:24
Subject: Re: Statement logging per connection
Previous:From: Alexander StanierDate: 2005-07-21 14:21:18
Subject: Re: FATAL: could not read statistics message

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group