Re: VACUUM FULL needed sometimes to prevent transaction

Поиск
Список
Период
Сортировка
От Markus Schaber
Тема Re: VACUUM FULL needed sometimes to prevent transaction
Дата
Msg-id 44EC4F2E.1010304@logix-tt.com
обсуждение исходный текст
Ответ на Re: VACUUM FULL needed sometimes to prevent transaction  (Jeff Davis <pgsql@j-davis.com>)
Ответы Re: VACUUM FULL needed sometimes to prevent transaction  (Heikki Linnakangas <heikki@enterprisedb.com>)
Список 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

В списке pgsql-performance по дате отправления:

Предыдущее
От: Chris
Дата:
Сообщение: Re: Forcing index usage without 'enable_hashjoin = FALSE'
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: Re: VACUUM FULL needed sometimes to prevent transaction