Re: Failed assertion during recovery of partial WAL file - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Failed assertion during recovery of partial WAL file
Date
Msg-id 4B726D9F.2050304@enterprisedb.com
Whole thread Raw
In response to Re: Failed assertion during recovery of partial WAL file  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
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 applied WAL file remains closed.
> So readFile (which ought to have been the file descriptor of that WAL file)
> might be -1 in exitArchiveRecovery().
> 
> In the now, that assertion is obsolete. So I attached the patch that removes
> the assert() from exitArchiveRecovery().

Committed.

--  Heikki Linnakangas EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL
Next
From: Kurt Harriman
Date:
Subject: Re: Patch: Remove gcc dependency in definition of inline functions