aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/functions.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2007-01-27 20:53:46 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2007-01-27 20:53:46 +0000
commitf109cb128553162fef3e8f945ef5a4d8f4698269 (patch)
tree956e39145315040c3942ae48fc3a42f72d0d22f8 /src/backend/executor/functions.c
parent6b8a7cfadc9653884cc09864d305f3adb245ecb0 (diff)
downloadpostgresql-f109cb128553162fef3e8f945ef5a4d8f4698269.tar.gz
postgresql-f109cb128553162fef3e8f945ef5a4d8f4698269.zip
Correct an old logic error in btree page splitting: when considering a split
exactly at the point where we need to insert a new item, the calculation used the wrong size for the "high key" of the new left page. This could lead to choosing an unworkable split, resulting in "PANIC: failed to add item to the left sibling" (or "right sibling") failure. Although this bug has been there a long time, it's very difficult to trigger a failure before 8.2, since there was generally a lot of free space on both sides of a chosen split. In 8.2, where the user-selected fill factor determines how much free space the code tries to leave, an unworkable split is much more likely. Report by Joe Conway, diagnosis and fix by Heikki Linnakangas.
Diffstat (limited to 'src/backend/executor/functions.c')
0 files changed, 0 insertions, 0 deletions