FSM Corruption (was: Could not read block at end of the relation)
В списке pgsql-bugs по дате отправления:
| От | Ronan Dunklau |
|---|---|
| Тема | FSM Corruption (was: Could not read block at end of the relation) |
| Дата | |
| Msg-id | 1958255.PYKUYFuaPT@aivenlaptop обсуждение исходный текст |
| Ответ на | Could not read block at end of the relation (Ronan Dunklau <ronan.dunklau@aiven.io>) |
| Ответы |
Re: FSM Corruption (was: Could not read block at end of the relation)
Re: FSM Corruption (was: Could not read block at end of the relation) |
| Список | pgsql-bugs |
Le mardi 27 février 2024, 11:34:14 CET Ronan Dunklau a écrit : > I suspected the FSM could be corrupted in some way but taking a look at it > just after the errors have been triggered, the offending (non > existing)blocks are just not present in the FSM either. I think I may have missed something on my first look. On other affected clusters, the FSM is definitely corrupted. So it looks like we have an FSM corruption bug on our hands. The occurence of this bug happening makes it hard to reproduce, but it's definitely frequent enough we witnessed it on a dozen PostgreSQL clusters. In our case, we need to repair the FSM. The instructions on the wiki do work, but maybe we should add something like the attached patch (modeled after the same feature in pg_visibility) to make it possible to repair the FSM corruption online. What do you think about it ? The investigation of the corruption is still ongoing. Best regards, -- Ronan Dunklau
В списке pgsql-bugs по дате отправления:
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера