Repair longstanding error in btree xlog replay: XLogReadBuffer should be

Tom Lane <tgl@sss.pgh.pa.us>

Commit: b5c5c5d2838d2a9e80e58000138c50ed0aa0eff0
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date: 2006-03-28T21:17:44Z
Releases: 8.0.8
Repair longstanding error in btree xlog replay: XLogReadBuffer should be
passed extend = true whenever we are reading a page we intend to reinitialize
completely, even if we think the page "should exist".  This is because it
might indeed not exist, if the relation got truncated sometime after the
current xlog record was made and before the crash we're trying to recover
from.  These two thinkos appear to explain both of the old bug reports
discussed here:
http://archives.postgresql.org/pgsql-hackers/2005-05/msg01369.php

Files

PathChange+/−
src/backend/access/nbtree/nbtxlog.c modified +3 −3