From: Markus Schaber <schabi@logix-tt.com>
To: pgsql-performance@postgresql.org
Subject: Re: VACUUM FULL needed sometimes to prevent transaction
Date: Wed, 23 Aug 2006 14:50:54 +0200
Message-ID: <44EC4F2E.1010304@logix-tt.com> (raw)
In-Reply-To: <1156284025.15743.104.camel@dogma.v10.wvs>
References: <44EB48A9.7030704@geizhals.at>
<1156284025.15743.104.camel@dogma.v10.wvs>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: schabi@logix-tt.com
Subject: Re: VACUUM FULL needed sometimes to prevent transaction
In-Reply-To: <44EC4F2E.1010304@logix-tt.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox