Skip site navigation (1) Skip section navigation (2)

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

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix "failed to re-find parent key" btree VACUUM failure by
Date: 2006-11-01 19:50:15
Message-ID: 20061101195015.5BFC69FB82C@postgresql.org (view raw or flat)
Thread:
Lists: 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:
----
REL7_4_STABLE

Modified Files:
--------------
    pgsql/src/backend/access/nbtree:
        README (r1.7 -> r1.7.4.1)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/README.diff?r1=1.7&r2=1.7.4.1)
        nbtinsert.c (r1.106.2.2 -> r1.106.2.3)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtinsert.c.diff?r1=1.106.2.2&r2=1.106.2.3)
        nbtpage.c (r1.72.2.1 -> r1.72.2.2)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtpage.c.diff?r1=1.72.2.1&r2=1.72.2.2)

pgsql-committers by date

Next:From: User DiogobDate: 2006-11-01 21:16:17
Subject: press - pr: almost done
Previous:From: Tom LaneDate: 2006-11-01 19:50:08
Subject: pgsql: Fix "failed to re-find parent key" btree VACUUM failure by

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group