Fujii Masao wrote:
> This assertion failure derives from the recent refactoring of ReadRecord().
> Which changed the startup process so as to re-fetch the last applied WAL
> record at the end of recovery from the buffer instead of the WAL file if it's
> stored in the buffer. In this case, the last
On Fri, Feb 5, 2010 at 10:46 PM, Martin Pihlak wrote:
> Encountered the following FailedAssertion while testing database
> recovery (actually this would be HS) with partial WAL file:
>
> LOG: restored log file "00010003" from archive
> LOG: consistent recovery state reached at 0/
Encountered the following FailedAssertion while testing database
recovery (actually this would be HS) with partial WAL file:
LOG: restored log file "00010003" from archive
LOG: consistent recovery state reached at 0/3001EEC
LOG: record with zero length at 0/3001EEC
LOG: redo do
