Re: track_commit_timestamp and COMMIT PREPARED

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: track_commit_timestamp and COMMIT PREPARED
Дата
Msg-id CA+TgmobONXRca2mZTm4GfFhBWg-acZ-hQhFDQLUaU_AGjgfRGg@mail.gmail.com
обсуждение исходный текст
Ответ на track_commit_timestamp and COMMIT PREPARED  (Fujii Masao <masao.fujii@gmail.com>)
Ответы Re: track_commit_timestamp and COMMIT PREPARED
Re: track_commit_timestamp and COMMIT PREPARED
Список pgsql-hackers
On Mon, Aug 3, 2015 at 10:31 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
> track_commit_timestamp tracks COMMIT PREPARED as expected in standby server,
> but not in master server. Is this intentional? It should track COMMIT PREPARED
> even in master? Otherwise, we cannot use commit_timestamp feature to check
> the replication lag properly while we use 2PC.

That sounds like it must be a bug.  I think you should add it to the
open items list.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: Doubt about AccessExclusiveLock in ALTER TABLE .. SET ( .. );
Следующее
От: Andres Freund
Дата:
Сообщение: Re: track_commit_timestamp and COMMIT PREPARED