Re: track_commit_timestamp and COMMIT PREPARED

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: track_commit_timestamp and COMMIT PREPARED
Дата
Msg-id 20150804171811.GC32119@awork2.anarazel.de
обсуждение исходный текст
Ответ на Re: track_commit_timestamp and COMMIT PREPARED  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: track_commit_timestamp and COMMIT PREPARED  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
On 2015-08-04 13:16:52 -0400, Robert Haas wrote:
> 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.

Yea, completely agreed. It's probably because twophase.c duplicates a
good bit of xact.c. How about we also add a warning to the respective
places that one should always check the others?



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

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: track_commit_timestamp and COMMIT PREPARED
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: FSM versus GIN pending list bloat