aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeBitmapOr.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2007-04-19 20:24:04 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2007-04-19 20:24:04 +0000
commit9d37c038fcfe362343a9622236e344438ccef7a6 (patch)
tree499c178aaddf348403dc84523984e68866e017d3 /src/backend/executor/nodeBitmapOr.c
parent77a41e71a3550a438e579da170db86c61bd61e4b (diff)
downloadpostgresql-9d37c038fcfe362343a9622236e344438ccef7a6.tar.gz
postgresql-9d37c038fcfe362343a9622236e344438ccef7a6.zip
Repair PANIC condition in hash indexes when a previous index extension attempt
failed (due to lock conflicts or out-of-space). We might have already extended the index's filesystem EOF before failing, causing the EOF to be beyond what the metapage says is the last used page. Hence the invariant maintained by the code needs to be "EOF is at or beyond last used page", not "EOF is exactly the last used page". Problem was created by my patch of 2006-11-19 that attempted to repair bug #2737. Since that was back-patched to 7.4, this needs to be as well. Per report and test case from Vlastimil Krejcir.
Diffstat (limited to 'src/backend/executor/nodeBitmapOr.c')
0 files changed, 0 insertions, 0 deletions