Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly
Дата
Msg-id 870747.1750191510@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly  ("Vitaly Davydov" <v.davydov@postgrespro.ru>)
Список pgsql-hackers
vignesh C <vignesh21@gmail.com> writes:
> While tracking buildfarm for one of other commits, I noticed this failure:
> TRAP: failed Assert("s->data.restart_lsn >=
> s->last_saved_restart_lsn"), File:
> "../pgsql/src/backend/replication/slot.c", Line: 1813, PID: 3945797

My animal mamba is also showing this assertion failure, but in a
different test (recovery/t/040_standby_failover_slots_sync.pl).
It's failed in two out of its three runs since ca307d5ce went in,
so it's more reproducible than scorpion's report, though still not
perfectly so.

I suspect that mamba is prone to this simply because it's slow,
although perhaps there's a different reason.  Anyway, happy to
investigate manually if there's something you'd like me to
check for.

            regards, tom lane



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