Thread: pgsql: Improve a number of elog messages for not-supposed-to-happen
pgsql: Improve a number of elog messages for not-supposed-to-happen
From
tgl@postgresql.org (Tom Lane)
Date:
Log Message:
-----------
Improve a number of elog messages for not-supposed-to-happen cases in btrees,
since these seem to happen after all in corrupted indexes. Make sure we
supply the index name in all cases, and provide relevant block numbers where
available. Also consistently identify the index name as such.
Back-patch to 8.2, in hopes that this might help Mason Hale figure out his
problem.
Tags:
----
REL8_2_STABLE
Modified Files:
--------------
pgsql/src/backend/access/nbtree:
nbtinsert.c (r1.146.2.1 -> r1.146.2.2)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtinsert.c?r1=1.146.2.1&r2=1.146.2.2)
nbtpage.c (r1.101 -> r1.101.2.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtpage.c?r1=1.101&r2=1.101.2.1)
nbtsearch.c (r1.107.2.1 -> r1.107.2.2)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtsearch.c?r1=1.107.2.1&r2=1.107.2.2)