NotificationsYou must be signed in to change notification settings
Fork6
Star31

Commite72910f

committed

Fix handling of multi-column BRIN indexes

When evaluating clauses on multiple scan keys of a multi-column BRINindex, we can stop processing as soon as we find a scan key eliminatingthe range, and the range should not be added to tbe bitmap.That's how it worked before 14, but sincea681e3c the code treatedthe range as matching if it matched at least the last scan key.Backpatch to 14, where this code was introduced.Backpatch-through: 14Discussion:https://postgr.es/m/ebc18613-125e-60df-7520-fcbe0f9274fc%40enterprisedb.com

1 parent393430f commite72910fCopy full SHA for e72910f

File tree

1 file changed

-0

lines changed

src/backend/access/brin
- brin.c

1 file changed

-0

lines changed

`‎src/backend/access/brin/brin.c`

Lines changed: 7 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -686,6 +686,13 @@ bringetbitmap(IndexScanDesc scan, TIDBitmap *tbm)`
`686`	`686`	`break;`
`687`	`687`	`}`
`688`	`688`	`}`
	`689`	`+`
	`690`	`+/*`
	`691`	`+ * If we found a scan key eliminating the range, no need to`
	`692`	`+ * check additional ones.`
	`693`	`+ */`
	`694`	`+if (!addrange)`
	`695`	`+break;`
`689`	`696`	`}`
`690`	`697`	`}`
`691`	`698`	`}`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commite72910f

File tree

1 file changed

1 file changed

`‎src/backend/access/brin/brin.c`

0 commit comments