pgsql: Repair longstanding error in btree xlog replay: XLogReadBuffer - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Repair longstanding error in btree xlog replay: XLogReadBuffer
Date
Msg-id 20060328211731.6ABA711F6963@postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
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

Tags:
----
REL8_1_STABLE

Modified Files:
--------------
    pgsql/src/backend/access/nbtree:
        nbtxlog.c (r1.24 -> r1.24.2.1)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtxlog.c.diff?r1=1.24&r2=1.24.2.1)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Repair longstanding error in btree xlog replay: XLogReadBuffer
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Repair longstanding error in btree xlog replay: XLogReadBuffer