aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2006-11-01 19:50:08 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2006-11-01 19:50:08 +0000
commitb4f5429fa84d08a6466f49b15d2586df9f183eb5 (patch)
tree44827c665fbe6c69694531de2dcfeb76470f3a45 /src/backend/executor
parent3aba3aa5b442213c2ab6fef079c9ce9356a96f91 (diff)
downloadpostgresql-b4f5429fa84d08a6466f49b15d2586df9f183eb5.tar.gz
postgresql-b4f5429fa84d08a6466f49b15d2586df9f183eb5.zip
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.
Diffstat (limited to 'src/backend/executor')
0 files changed, 0 insertions, 0 deletions