Re: broken tables on hot standby after migration on PostgreSQL 16 (3x times last month)

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: broken tables on hot standby after migration on PostgreSQL 16 (3x times last month)
Дата
Msg-id CAH2-WzkGE_QYm1ZF0NhR4S=c2GomUb3o7ecPCwe--Trapu898g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: broken tables on hot standby after migration on PostgreSQL 16 (3x times last month)  (Andres Freund <andres@anarazel.de>)
Ответы Re: broken tables on hot standby after migration on PostgreSQL 16 (3x times last month)  (Andres Freund <andres@anarazel.de>)
Список pgsql-hackers
Дерево обсуждения 
On Fri, May 17, 2024 at 3:50 PM Andres Freund <andres@anarazel.de> wrote:
> You're saying that the data is correctly accessible on primaries, but broken
> on standbys? Is there any difference in how the page looks like on the primary
> vs standby?

There clearly is. The relevant infomask bits are different. I didn't
examine it much closer than that, though.

--
Peter Geoghegan

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

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index.
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: broken tables on hot standby after migration on PostgreSQL 16 (3x times last month)