aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2020-08-12 15:33:36 -0400
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2020-08-12 15:33:36 -0400
commit1f42d35a1d6144a23602b2c0bc7f97f3046cf890 (patch)
tree58fc88aa21fc52a479867904e1e1c9657f7cd169 /src/backend/access/gist
parent3546cf8a7a9dc57e6aa98f5fc1ac5476ad6b99ff (diff)
downloadpostgresql-1f42d35a1d6144a23602b2c0bc7f97f3046cf890.tar.gz
postgresql-1f42d35a1d6144a23602b2c0bc7f97f3046cf890.zip
BRIN: Handle concurrent desummarization properly
If a page range is desummarized at just the right time concurrently with an index walk, BRIN would raise an error indicating index corruption. This is scary and unhelpful; silently returning that the page range is not summarized is sufficient reaction. This bug was introduced by commit 975ad4e602ff as additional protection against a bug whose actual fix was elsewhere. Backpatch equally. Reported-By: Anastasia Lubennikova <a.lubennikova@postgrespro.ru> Diagnosed-By: Alexander Lakhin <exclusion@gmail.com> Discussion: https://postgr.es/m/2588667e-d07d-7e10-74e2-7e1e46194491@postgrespro.ru Backpatch: 9.5 - master
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions