Re: VACUUM FULL needed sometimes to prevent transaction

From: Markus Schaber <schabi(at)logix-tt(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: VACUUM FULL needed sometimes to prevent transaction
Date: 2006-08-23 12:50:54
Message-ID: 44EC4F2E.1010304@logix-tt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Heikki Linnakangas 2006-08-23 13:24:05 Re: VACUUM FULL needed sometimes to prevent transaction
Previous Message Chris 2006-08-23 03:31:57 Re: Forcing index usage without 'enable_hashjoin = FALSE'