aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2018-03-01 18:07:46 -0300
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2018-03-01 18:07:46 -0300
commit477ad05e165c15dc9241376f0fce9664063cff46 (patch)
tree1a969e5bed82ab3300e7ad6438f54484a3534f76 /src/backend/access/gist
parentb5febc1d125cac37c626cb7c96936db6839ec733 (diff)
downloadpostgresql-477ad05e165c15dc9241376f0fce9664063cff46.tar.gz
postgresql-477ad05e165c15dc9241376f0fce9664063cff46.zip
Relax overly strict sanity check for upgraded ancient databases
Commit 4800f16a7ad0 added some sanity checks to ensure we don't accidentally corrupt data, but in one of them we failed to consider the effects of a database upgraded from 9.2 or earlier, where a tuple exclusively locked prior to the upgrade has a slightly different bit pattern. Fix that by using the macro that we fixed in commit 74ebba84aeb6 for similar situations. Reported-by: Alexandre Garcia Reviewed-by: Andres Freund Discussion: https://postgr.es/m/CAPYLKR6yxV4=pfW0Gwij7aPNiiPx+3ib4USVYnbuQdUtmkMaEA@mail.gmail.com Andres suspects that this bug may have wider ranging consequences, but I couldn't find anything.
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions