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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-07-21 14:50:24 | Re: Statement logging per connection |
Previous Message | Alexander Stanier | 2005-07-21 14:21:18 | Re: FATAL: could not read statistics message |