Repair longstanding error in btree xlog replay: XLogReadBuffer should be

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

Commit: 3c3ed28c75455ab18f5f7fb11262b9cb28c36f8c
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date: 2006-03-28T21:17:31Z
Releases: 8.1.4
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