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 <[email protected]> Diagnosed-By: Alexander Lakhin <[email protected]> Discussion: https://postgr.es/m/[email protected] Backpatch: 9.5 - master Branch ------ REL9_5_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/ce3a8fde8e62c62c29e4342ad32b07b2bbf33b64 Modified Files -------------- src/backend/access/brin/brin_revmap.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)
