Fix "failed to re-find parent key" btree VACUUM failure by revising page
deletion code to avoid the case where an upper-level btree page remains "half
dead" for a significant period of time, and to block insertions into a key
range that is in process of being re-assigned to the right sibling of the
deleted page's parent. This prevents the scenario reported by Ed L. wherein
index keys could become out-of-order in the grandparent index level.
Since this is a moderately invasive fix, I'm applying it only to HEAD.
The bug exists back to 7.4, but the back branches will get a different patch.
README (r1.13 -> r1.14)
nbtinsert.c (r1.144 -> r1.145)
nbtpage.c (r1.100 -> r1.101)
nbtree.c (r1.152 -> r1.153)
nbtxlog.c (r1.38 -> r1.39)
nbtree.h (r1.105 -> r1.106)
pgsql-committers by date
|Next:||From: Tom Lane||Date: 2006-11-01 19:50:03|
|Subject: pgsql: Fix "failed to re-find parent key" btree VACUUM failure by |
|Previous:||From: Tom Lane||Date: 2006-11-01 15:59:31|
|Subject: pgsql: pg_restore failed on tar-format archives if they contained large |