Re: [HACKERS] Failed recovery with new faster 2PC code

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: [HACKERS] Failed recovery with new faster 2PC code
Дата
Msg-id CAB7nPqQUzRQrSxycnFsWX8=ztyQrt_MXTPjN=R-864Yhe8M=Ww@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Failed recovery with new faster 2PC code  (Jeff Janes <jeff.janes@gmail.com>)
Список pgsql-hackers
On Wed, Apr 19, 2017 at 11:09 AM, Jeff Janes <jeff.janes@gmail.com> wrote:
> Would this bug have been seen in a replica server in the absence of crashes,
> or was it only vulnerable during crash recovery rather than streaming
> replication?

This issue could have been seen on a streaming standby as well,
letting around a TwoPhaseState impacts as well their linked PGPROC so
CLOG truncation would have been messed up as well. That's also the
case of the first issue involving as well incorrect XID updates,
though the chances to see it are I think lower as only the beginning
of recovery was impacted.
-- 
Michael



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

Предыдущее
От: Petr Jelinek
Дата:
Сообщение: [HACKERS] Use sync commit for logical replication apply in TAP tests
Следующее
От: David Rowley
Дата:
Сообщение: Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn()