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
Branch
------
REL_11_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/7af39993a47c56099e8cfea4191e7e686c7a6d0e
Modified Files
--------------
src/backend/access/brin/brin_revmap.c | 13 ++++++++++---
1 file changed, 10 insertions(+), 3 deletions(-)
