Re: logical decoding of two-phase transactions

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: logical decoding of two-phase transactions
Дата
Msg-id 20170327212528.cwf4aotytwrsowwx@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: logical decoding of two-phase transactions  (Stas Kelvich <s.kelvich@postgrespro.ru>)
Ответы Re: logical decoding of two-phase transactions  (Craig Ringer <craig@2ndquadrant.com>)
Re: logical decoding of two-phase transactions  (Stas Kelvich <s.kelvich@postgrespro.ru>)
Список pgsql-hackers
Дерево обсуждения 
Hi,

On 2017-03-28 00:19:29 +0300, Stas Kelvich wrote:
> Ok, here it is.

On a very quick skim, this doesn't seem to solve the issues around
deadlocks of prepared transactions vs. catalog tables.  What if the
prepared transaction contains something like LOCK pg_class; (there's a
lot more realistic examples)? Then decoding won't be able to continue,
until that transaction is committed / aborted?

- Andres

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

Предыдущее
От: Stas Kelvich
Дата:
Сообщение: Re: logical decoding of two-phase transactions
Следующее
От: Fabien COELHO
Дата:
Сообщение: Re: \if, \elseif, \else, \endif (was Re: PSQL commands:\quit_if, \quit_unless)