Re: BUG #8347: PANIC: heap_insert_redo: failed to add tuple when applying WAL

Поиск
Список
Период
Сортировка
От Daniel Farina
Тема Re: BUG #8347: PANIC: heap_insert_redo: failed to add tuple when applying WAL
Дата
Msg-id CAAZKuFZEEFNVywTVk4CKXbT2j9D0FrCUM6s-zooiDgYURk4dxQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #8347: PANIC: heap_insert_redo: failed to add tuple when applying WAL  (Klaus Ita <klaus@worstofall.com>)
Список pgsql-bugs
On Fri, Aug 2, 2013 at 12:51 AM, Klaus Ita <klaus@worstofall.com> wrote:
> Isn't it a funny coincidence, that we also had a corruption of that
> same/similar type?
>
> my disk was quite confidently not tampered. I am wondering: Does PG sign, or
> checksum wal_files? Is the integrity of wal_files ensured by any mechanism?
> Because if it IS, then - in our case - it's a corruption caused BY the
> postgres master server. I can replay the wal's and re-create the same error
> over and over.

Corruption can hitch a ride on a WAL full page image without much
difficulty, as long as the page header looks legit (from what I've
seen so far, a bad page header will prevent the system from doing much
with it, so no FPIs will be generated).

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

Предыдущее
От: Klaus Ita
Дата:
Сообщение: Re: BUG #8347: PANIC: heap_insert_redo: failed to add tuple when applying WAL
Следующее
От: Klaus Ita
Дата:
Сообщение: Re: [GENERAL] Recovery_target_time misinterpreted?