Re: pg_waldump error message fix

Поиск
Список
Период
Сортировка
Искать
От
Michael Paquier
Тема
Re: pg_waldump error message fix
Дата
Msg-id
X9bVVaGinZEusb73@paquier.xyz
Ответ на
Список
Дерево обсуждения
pg_waldump error message fix "Bossart, Nathan" <bossartn@amazon.com>
Re: pg_waldump error message fix Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Re: pg_waldump error message fix Michael Paquier <michael@paquier.xyz>
Re: pg_waldump error message fix Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Re: pg_waldump error message fix Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Re: pg_waldump error message fix "Bossart, Nathan" <bossartn@amazon.com>
Re: pg_waldump error message fix Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Re: pg_waldump error message fix Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Re: pg_waldump error message fix Michael Paquier <michael@paquier.xyz>
Re: pg_waldump error message fix "Bossart, Nathan" <bossartn@amazon.com>
Re: pg_waldump error message fix Michael Paquier <michael@paquier.xyz>
On Mon, Dec 14, 2020 at 10:26:01AM +0900, Kyotaro Horiguchi wrote:
> Yeah, I had the same feeling. At least, the two LSNs in the message
> under discussion are simply redundant. So +1 to just remove the LSN at
> the caller site.

That would mean that we are ready to accept that we will never forget
to a LSN in any of the messages produced by xlogreader.c or any of the
callbacks used by pg_waldump.  FWIW, I'd rather let a position in this
report than none.  At least it allows users to know the area where the
problem happened.
--
Michael
В списке pgsql-hackers по дате отправления
От: k.jamison@fujitsu.com
Дата:
От: Michael Paquier
Дата:
FAQ