Re: VACUUM FULL needed sometimes to prevent transaction

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Markus Schaber <schabi@xxxxxxxxxxxx>, pgsql-performance@xxxxxxxxxxxxxx
Subject: Re: VACUUM FULL needed sometimes to prevent transaction
From: Heikki Linnakangas <heikki@xxxxxxxxxxxxxxxx>
Date: Wed, 23 Aug 2006 14:24:05 +0100
In-reply-to: <44EC4F2E.1010304@xxxxxxxxxxxx>
References: <44EB48A9.7030704@xxxxxxxxxxx> <1156284025.15743.104.camel@xxxxxxxxxxxxx> <44EC4F2E.1010304@xxxxxxxxxxxx>
User-agent: Thunderbird 1.5.0.4 (X11/20060713)

Markus Schaber wrote:

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


Yes.

--
 Heikki Linnakangas
 EnterpriseDB   http://www.enterprisedb.com

References:
- VACUUM FULL needed sometimes to prevent transaction ID wraparound?
  - From: Marinos Yannikos
- Re: VACUUM FULL needed sometimes to prevent transaction
  - From: Jeff Davis
- Re: VACUUM FULL needed sometimes to prevent transaction
  - From: Markus Schaber

Prev by Date: Re: VACUUM FULL needed sometimes to prevent transaction
Next by Date: Re: Query tuning
Previous by thread: Re: VACUUM FULL needed sometimes to prevent transaction
Next by thread: Benchmarks
Index(es):
- Date
- Thread

[Postgresql General] [Postgresql PHP] [PHP Users] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Yosemite]

Powered by Linux