pgsql: Fix "failed to re-find parent key" btree VACUUM failure by - Mailing list pgsql-committers

Log Message:
-----------
Fix "failed to re-find parent key" btree VACUUM failure by tweaking
_bt_pagedel to recover from the failure: just search the whole parent level
if searching to the right fails.  This does nothing for the underlying problem
that index keys became out-of-order in the grandparent level.  However, we
believe that there is no other consequence worse than slightly inefficient
searching, so this narrow patch seems like the safest solution for the back
branches.

Tags:
----
REL8_1_STABLE

Modified Files:
--------------
    pgsql/src/backend/access/nbtree:
        README (r1.8 -> r1.8.6.1)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/README.diff?r1=1.8&r2=1.8.6.1)
        nbtinsert.c (r1.127.2.1 -> r1.127.2.2)

(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtinsert.c.diff?r1=1.127.2.1&r2=1.127.2.2)
        nbtpage.c (r1.88.2.1 -> r1.88.2.2)

(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtpage.c.diff?r1=1.88.2.1&r2=1.88.2.2)