| 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:59 |
| Message-ID: | 20060328211759.1BD7111F68E4@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
Tags:
----
REL7_4_STABLE
Modified Files:
--------------
pgsql/src/backend/access/nbtree:
nbtxlog.c (r1.7 -> r1.7.2.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtxlog.c.diff?r1=1.7&r2=1.7.2.1)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | User Jpargudo | 2006-03-28 21:39:25 | pgloader - pgloader: This new version allows importing data from all |
| Previous Message | Tom Lane | 2006-03-28 21:17:44 | pgsql: Repair longstanding error in btree xlog replay: XLogReadBuffer |