From: Tomas Vondra <tomas.vondra@postgresql.org>
Date: Sat, 18 Feb 2023 23:41:18 +0000 (+0100)
Subject: Fix handling of multi-column BRIN indexes
X-Git-Tag: REL_16_BETA1~710
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=e72910f8080185b6ade9ef7caa5c891dba3cb51c;p=thirdparty%2Fpostgresql.git

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 de1427a1e0e..b5a5fa7b334 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;
 				}
 			}
 		}