Re: WAL replay failure after file truncation(?) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: WAL replay failure after file truncation(?)
Date
Msg-id 9011.1117145815@sss.pgh.pa.us
Whole thread Raw
In response to Re: WAL replay failure after file truncation(?)  (Manfred Koizar <mkoi-pg@aon.at>)
Responses Re: WAL replay failure after file truncation(?)  (Hans-Jürgen Schönig <postgres@cybertec.at>)
List pgsql-hackers
Manfred Koizar <mkoi-pg@aon.at> writes:
>>> [...]  Is it sufficient to
>>> remember just the relation and the block number or do we need the
>>> contents a well?

> I meant the contents of the WAL record, not the original block
> contents.  Anyway, I think it's not needed.

Oh, I see.  Yes, it might be worth hanging onto for debugging purposes.
If we did get a report of such a failure, I'm sure we'd wish to know
what sort of WAL record triggered it.  One trusts there won't be so many
that storing 'em all is a problem ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Manfred Koizar
Date:
Subject: Re: WAL replay failure after file truncation(?)
Next
From: Alvaro Herrera
Date:
Subject: A 2 phase commit weirdness