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

diff --git a/src/backend/access/brin/brin.c b/src/backend/access/brin/brin.c
index 21a23842595f92d4c20947297a46787c53a38b92..de7e96c70e61db76738fdcba7234223eba94361c 100644 (file)
--- 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;
                }
            }
        }