diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2006-11-01 19:43:17 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2006-11-01 19:43:17 +0000 |
| commit | 70ce5c908202ada7616f7afded8a91bbf2742471 (patch) | |
| tree | 82bac8aac8c437a381c9837e5fb8a46758beecaf /src/backend/access/gist/gist.c | |
| parent | 19d0c46def867119219e8362aecd3ba2fa745ee2 (diff) | |
| download | postgresql-70ce5c908202ada7616f7afded8a91bbf2742471.tar.gz postgresql-70ce5c908202ada7616f7afded8a91bbf2742471.zip | |
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.
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions