Re: "PANIC: could not open critical system index 2662" - twice

Поиск
Список
Период
Сортировка
От Evgeny Morozov
Тема Re: "PANIC: could not open critical system index 2662" - twice
Дата
Msg-id 010201877c0423c8-0a35b03c-d274-4857-ba99-ff7ea51d676b-000000@eu-west-1.amazonses.com
обсуждение исходный текст
Ответ на Re: "PANIC: could not open critical system index 2662" - twice  (Laurenz Albe <laurenz.albe@cybertec.at>)
Ответы Re: "PANIC: could not open critical system index 2662" - twice  (Laurenz Albe <laurenz.albe@cybertec.at>)
Список pgsql-general
Дерево обсуждения 
On 13/04/2023 5:02 pm, Laurenz Albe wrote:
> It means that if the error is caused by a faulty disk changing your data,
> you'll notice as soon as you touch the page.
>
> That would perhaps not have made a lot of difference in your case,
> except that the error message would have been different and proof
> that the disk was the problem.

OK, but we had data checksums on the whole time. So that means that the
disk was NOT the problem in our case?

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Unexpected behavior when combining `generated always` columns and update rules
Следующее
От: Bryn Llewellyn
Дата:
Сообщение: Why does "fetch last from cur" always cause error 55000 for non-scrollable cursor?