diff options
| author | Peter Geoghegan <pg@bowt.ie> | 2020-09-16 10:42:28 -0700 |
|---|---|---|
| committer | Peter Geoghegan <pg@bowt.ie> | 2020-09-16 10:42:28 -0700 |
| commit | c287f585865b81c96602db995dacf2c006c79d58 (patch) | |
| tree | 2f6011443883ce2f9b5cc50e2d957c164185a41c /src/backend/utils/adt/jsonpath_exec.c | |
| parent | 17280b31c2f218f1b1f0c1fbacae7e781010a01b (diff) | |
| download | postgresql-c287f585865b81c96602db995dacf2c006c79d58.tar.gz postgresql-c287f585865b81c96602db995dacf2c006c79d58.zip | |
Fix amcheck child check pg_upgrade bug.
Commit d114cc53 overlooked the fact that pg_upgrade'd B-Tree indexes
have leaf page high keys whose offset numbers do not match the one from
the copy of the tuple one level up (the copy stored with a downlink for
leaf page's right sibling page). This led to false positive reports of
corruption from bt_index_parent_check() when it was called to verify a
pg_upgrade'd index.
To fix, skip comparing the offset number on pg_upgrade'd B-Tree indexes.
Author: Anastasia Lubennikova <a.lubennikova@postgrespro.ru>
Author: Peter Geoghegan <pg@bowt.ie>
Reported-By: Andrew Bille <andrewbille@gmail.com>
Diagnosed-By: Anastasia Lubennikova <a.lubennikova@postgrespro.ru>
Bug: #16619
Discussion: https://postgr.es/m/16619-aaba10f83fdc1c3c@postgresql.org
Backpatch: 13-, where child check was enhanced.
Diffstat (limited to 'src/backend/utils/adt/jsonpath_exec.c')
0 files changed, 0 insertions, 0 deletions