| From: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BRIN indexes vs. SK_SEARCHARRAY (and preprocessing scan keys) |
| Date: | 2023-02-18 19:49:46 |
| Message-ID: | 327064f1-276e-cb45-88c2-1ff498037cf5@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Apparently there was a bug in handling IS [NOT] NULL scan keys in the
bloom opclass, so here's a fixed patch.
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-BRIN-bloom-cleanup-20230218.patch | text/x-patch | 1.9 KB |
| 0002-BRIN-minmax-multi-cleanup-20230218.patch | text/x-patch | 2.2 KB |
| 0003-Introduce-bloom_filter_size-20230218.patch | text/x-patch | 3.5 KB |
| 0004-Add-minmax-multi-inequality-tests-20230218.patch | text/x-patch | 16.8 KB |
| 0005-Introduce-BRIN_PROCNUM_PREPROCESS-procedure-20230218.patch | text/x-patch | 5.2 KB |
| 0006-Support-SK_SEARCHARRAY-in-BRIN-minmax-20230218.patch | text/x-patch | 69.5 KB |
| 0007-Support-SK_SEARCHARRAY-in-BRIN-minmax-multi-20230218.patch | text/x-patch | 75.1 KB |
| 0008-Support-SK_SEARCHARRAY-in-BRIN-inclusion-20230218.patch | text/x-patch | 22.8 KB |
| 0009-Support-SK_SEARCHARRAY-in-BRIN-bloom-20230218.patch | text/x-patch | 41.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2023-02-18 20:05:10 | Re: PATCH: Using BRIN indexes for sorted output |
| Previous Message | Justin Pryzby | 2023-02-18 18:51:09 | Re: PATCH: Using BRIN indexes for sorted output |