Postgres Pro
Downloads
Home   >   mailing lists

Re: VACUUM FULL needed sometimes to prevent transaction - Mailing list pgsql-performance

From Markus Schaber
Subject Re: VACUUM FULL needed sometimes to prevent transaction
Date
Msg-id 44EC4F2E.1010304@logix-tt.com
Whole thread Raw
In response to Re: VACUUM FULL needed sometimes to prevent transaction  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: VACUUM FULL needed sometimes to prevent transaction
List pgsql-performance
Tree view 
Hi, Jeff & all,

Jeff Davis wrote:


> (2) You have a long-running transaction that never completed for some
> strange reason.

I just asked myself whether a 2-phase-commit transaction that was
prepared, but never committed, can block vacuuming and TID recycling.

Markus

--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf.     | Software Development GIS

Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org

pgsql-performance by date:

Previous
From: Chris
Date:
Subject: Re: Forcing index usage without 'enable_hashjoin = FALSE'
Next
From: Heikki Linnakangas
Date:
Subject: Re: VACUUM FULL needed sometimes to prevent transaction