| From: | tgl(at)postgresql(dot)org (Tom Lane) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Repair longstanding error in btree xlog replay: XLogReadBuffer |
| Date: | 2006-03-28 21:17:23 |
| Message-ID: | 20060328211723.DD88E11F692B@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
Modified Files:
--------------
pgsql/src/backend/access/nbtree:
nbtxlog.c (r1.27 -> r1.28)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtxlog.c.diff?r1=1.27&r2=1.28)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-03-28 21:17:31 | pgsql: Repair longstanding error in btree xlog replay: XLogReadBuffer |
| Previous Message | User Ksrikanth | 2006-03-27 22:57:39 | bizgres - bizgres: File Modified :path.sh BUG BG-4 Fix : Use BIZHOME to |