From f3daa3116fad6aa85686aba5b54eaecc07e8f6cf Mon Sep 17 00:00:00 2001 From: Tomas Vondra Date: Sun, 19 Feb 2023 00:41:18 +0100 Subject: [PATCH] Fix handling of multi-column BRIN indexes When evaluating clauses on multiple scan keys of a multi-column BRIN index, we can stop processing as soon as we find a scan key eliminating the range, and the range should not be added to tbe bitmap. That's how it worked before 14, but since a681e3c107a the code treated the range as matching if it matched at least the last scan key. Backpatch to 14, where this code was introduced. Backpatch-through: 14 Discussion: https://postgr.es/m/ebc18613-125e-60df-7520-fcbe0f9274fc%40enterprisedb.com --- src/backend/access/brin/brin.c | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/backend/access/brin/brin.c b/src/backend/access/brin/brin.c index 21a2384259..de7e96c70e 100644 --- a/src/backend/access/brin/brin.c +++ b/src/backend/access/brin/brin.c @@ -686,6 +686,13 @@ bringetbitmap(IndexScanDesc scan, TIDBitmap *tbm) break; } } + + /* + * If we found a scan key eliminating the range, no need to + * check additional ones. + */ + if (!addrange) + break; } } }