Re: Possible bug in logical replication.

Поиск
Список
Период
Сортировка
Искать
От
Arseny Sher
Тема
Re: Possible bug in logical replication.
Дата
в 09:57:18
Msg-id
878t88ql2p.fsf@ars-thinkpad
Ответ на
Список
Дерево обсуждения
Possible bug in logical replication. Konstantin Knizhnik <k.knizhnik@postgrespro.ru>
Re: Possible bug in logical replication. Konstantin Knizhnik <k.knizhnik@postgrespro.ru>
Re: Possible bug in logical replication. Michael Paquier <michael@paquier.xyz>
Re: Possible bug in logical replication. Arseny Sher <a.sher@postgrespro.ru>
Re: Possible bug in logical replication. Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
Re: Possible bug in logical replication. Arseny Sher <a.sher@postgrespro.ru>
Re: Possible bug in logical replication. Masahiko Sawada <sawada.mshk@gmail.com>
Re: Possible bug in logical replication. Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
Re: Possible bug in logical replication. Michael Paquier <michael@paquier.xyz>
Re: Possible bug in logical replication. Arseny Sher <a.sher@postgrespro.ru>
Re: Possible bug in logical replication. Alvaro Herrera <alvherre@2ndquadrant.com>
Re: Possible bug in logical replication. Simon Riggs <simon@2ndquadrant.com>
Re: Possible bug in logical replication. Michael Paquier <michael@paquier.xyz>
Re: Possible bug in logical replication. Alvaro Herrera <alvherre@2ndquadrant.com>
Re: Possible bug in logical replication. Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
Re: Possible bug in logical replication. Michael Paquier <michael@paquier.xyz>
Re: Possible bug in logical replication. Arseny Sher <a.sher@postgrespro.ru>
Re: Possible bug in logical replication. Michael Paquier <michael@paquier.xyz>
Re: Possible bug in logical replication. Michael Paquier <michael@paquier.xyz>
Re: Possible bug in logical replication. Arseny Sher <a.sher@postgrespro.ru>
Re: Possible bug in logical replication. Petr Jelinek <petr.jelinek@2ndquadrant.com>
Re: Possible bug in logical replication. Michael Paquier <michael@paquier.xyz>
Re: Possible bug in logical replication. Michael Paquier <michael@paquier.xyz>
Re: Possible bug in logical replication. Alvaro Herrera <alvherre@2ndquadrant.com>
Re: Possible bug in logical replication. Michael Paquier <michael@paquier.xyz>
Re: Possible bug in logical replication. Michael Paquier <michael@paquier.xyz>
Re: Possible bug in logical replication. Alvaro Herrera <alvherre@2ndquadrant.com>
Re: Possible bug in logical replication. Michael Paquier <michael@paquier.xyz>
Re: Possible bug in logical replication. Alvaro Herrera <alvherre@2ndquadrant.com>
Re: Possible bug in logical replication. Michael Paquier <michael@paquier.xyz>
Re: Possible bug in logical replication. Alvaro Herrera <alvherre@2ndquadrant.com>
Re: Possible bug in logical replication. Michael Paquier <michael@paquier.xyz>
Re: Possible bug in logical replication. Alvaro Herrera <alvherre@2ndquadrant.com>
Re: Possible bug in logical replication. Erik Rijkers <er@xs4all.nl>
Re: Possible bug in logical replication. Arseny Sher <a.sher@postgrespro.ru>
Re: Possible bug in logical replication. Michael Paquier <michael@paquier.xyz>
Re: Possible bug in logical replication. Arseny Sher <a.sher@postgrespro.ru>
Re: Possible bug in logical replication. Masahiko Sawada <sawada.mshk@gmail.com>

Michael Paquier  writes:

> Maybe I am being too naive, but wouldn't it be just enough to update the
> confirmed flush LSN to ctx->reader->ReadRecPtr?  This way, the slot
> advances up to the beginning of the last record where user wants to
> advance, and not the beginning of the next record:

Same problem should be handled at pg_logical_slot_get_changes_guts and
apply worker feedback; and there is a convention that all commits since
confirmed_flush must be decoded, so we risk decoding such boundary
commit twice.

--
Arseny Sher
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

В списке pgsql-hackers по дате отправления
От: Andres Freund
Дата:
От: Michael Paquier
Дата:
FAQ