Re: Make pg_waldump report replication origin ID, LSN, and timestamp.

Поиск
Список
Период
Сортировка
От Masahiko Sawada
Тема Re: Make pg_waldump report replication origin ID, LSN, and timestamp.
Дата
Msg-id CAD21AoDJhE0n-j3Ns201j4QjCvrR+t0xJrNpr_gzT_JL3xv66g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Make pg_waldump report replication origin ID, LSN, and timestamp.  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: Make pg_waldump report replication origin ID, LSN, and timestamp.  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers
On Thu, Dec 9, 2021 at 4:02 PM Michael Paquier <michael@paquier.xyz> wrote:
>
> On Wed, Dec 08, 2021 at 05:03:30PM +0900, Masahiko Sawada wrote:
> > Agreed. I've attached an updated patch that incorporated your review
> > comments. Please review it.
>
> That looks correct to me.  One thing that I have noticed while
> reviewing is that we don't check XactCompletionApplyFeedback() in
> xact_desc_commit(), which would happen if a transaction needs to do
> a remote_apply on a standby.  synchronous_commit is a user-settable
> parameter, so it seems to me that it could be useful for debugging?
>

Agreed.

Thank you for updating the patch. The patch looks good to me.

Regards,

-- 
Masahiko Sawada
EDB:  https://www.enterprisedb.com/



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

Предыдущее
От: Thomas Munro
Дата:
Сообщение: Re: stat() vs ERROR_DELETE_PENDING, round N + 1
Следующее
От: Masahiko Sawada
Дата:
Сообщение: Re: Skipping logical replication transactions on subscriber side