pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Fix handling of multi-column BRIN indexes 3+ messages / 1 participants [nested] [flat]
* pgsql: Fix handling of multi-column BRIN indexes @ 2023-02-19 00:47 Tomas Vondra <tomas.vondra@postgresql.org> 0 siblings, 0 replies; 3+ messages in thread From: Tomas Vondra @ 2023-02-19 00:47 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/e72910f8080185b6ade9ef7caa5c891dba3cb51c Modified Files -------------- src/backend/access/brin/brin.c | 7 +++++++ 1 file changed, 7 insertions(+) ^ permalink raw reply [nested|flat] 3+ messages in thread
* pgsql: Fix handling of multi-column BRIN indexes @ 2023-02-19 00:48 Tomas Vondra <tomas.vondra@postgresql.org> 0 siblings, 0 replies; 3+ messages in thread From: Tomas Vondra @ 2023-02-19 00:48 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_15_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/305d89ad93ff6eb3eecae485bbfb2531a349906f Modified Files -------------- src/backend/access/brin/brin.c | 7 +++++++ 1 file changed, 7 insertions(+) ^ permalink raw reply [nested|flat] 3+ messages in thread
* pgsql: Fix handling of multi-column BRIN indexes @ 2023-02-19 00:48 Tomas Vondra <tomas.vondra@postgresql.org> 0 siblings, 0 replies; 3+ messages in thread From: Tomas Vondra @ 2023-02-19 00:48 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/f3daa3116fad6aa85686aba5b54eaecc07e8f6cf Modified Files -------------- src/backend/access/brin/brin.c | 7 +++++++ 1 file changed, 7 insertions(+) ^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2023-02-19 00:48 UTC | newest] Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2023-02-19 00:47 pgsql: Fix handling of multi-column BRIN indexes Tomas Vondra <tomas.vondra@postgresql.org> 2023-02-19 00:48 pgsql: Fix handling of multi-column BRIN indexes Tomas Vondra <tomas.vondra@postgresql.org> 2023-02-19 00:48 pgsql: Fix handling of multi-column BRIN indexes Tomas Vondra <tomas.vondra@postgresql.org>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox