Re: reporting TID/table with corruption error

Поиск
Список
Период
Сортировка
От Andrey Borodin
Тема Re: reporting TID/table with corruption error
Дата
Msg-id AE9F48F0-C081-4130-A848-149B29D93251@yandex-team.ru
обсуждение исходный текст
Ответ на reporting TID/table with corruption error  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Список pgsql-hackers

> 19 авг. 2021 г., в 21:37, Alvaro Herrera <alvherre@alvh.no-ip.org> написал(а):
>
> A customer recently hit this error message:
>
> ERROR:  t_xmin is uncommitted in tuple to be updated

Sorry for one more message, it occurred to me only after sending previous one that I know this exact message.

We encountered this error twice:
1. When dealing with broken WAL-delta backups in WAL-G (a kind of fast incremental backup, the bug was fixed back in
2019)The page simply was of an old version. 
2. As a result of broken page cache in patched linux kernel (clog was fsynced succesfully, but the page fsync was lost
beforerestart) 

Best regards, Andrey Borodin.


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

Предыдущее
От: Andrey Borodin
Дата:
Сообщение: Re: reporting TID/table with corruption error
Следующее
От: Dagfinn Ilmari Mannsåker
Дата:
Сообщение: Re: reporting TID/table with corruption error