Re: WIP: BRIN multi-range indexes

From: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Mark Dilger <hornschnorter(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WIP: BRIN multi-range indexes
Date: 2020-09-05 23:20:42
Message-ID: 20200905232042.4jegjfjfpzxsvowb@development
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Sat, Sep 05, 2020 at 10:46:48AM +0900, Michael Paquier wrote:
>On Fri, Aug 07, 2020 at 06:27:01PM +0200, Tomas Vondra wrote:
>> Attached is an updated version of the patch series, implementing this.
>> Adding the extra data types was fairly simple, because both bloom and
>> minmax-multi indexes already used "struct as varlena" approach, so all
>> that needed was a bunch of in/out functions and catalog records.
>> I've left the changes in separate patches for clarity, ultimately it'll
>> get merged into the other parts.
>This fails to apply per the CF bot, so please provide a rebase.

OK, here is a rebased version. Most of the breakage was due to changes
to the BRIN sgml docs.


Tomas Vondra
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment Content-Type Size
0001-Pass-all-keys-to-BRIN-consistent-function-a-20200906.patch text/plain 20.8 KB
0002-Move-IS-NOT-NULL-checks-to-bringetbitmap-20200906.patch text/plain 9.9 KB
0003-Move-processing-of-NULLs-from-BRIN-support--20200906.patch text/plain 16.1 KB
0004-BRIN-bloom-indexes-20200906.patch text/plain 129.5 KB
0005-add-special-pg_brin_bloom_summary-data-type-20200906.patch text/plain 5.8 KB
0006-BRIN-minmax-multi-indexes-20200906.patch text/plain 207.0 KB
0007-add-special-pg_brin_minmax_multi_summary-da-20200906.patch text/plain 15.3 KB
0008-tweak-costing-for-bloom-minmax-multi-indexe-20200906.patch text/plain 3.9 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2020-09-06 00:24:31 Re: Keep elog(ERROR) and ereport(ERROR) calls in the cold path
Previous Message Tom Lane 2020-09-05 22:42:16 Re: [PATCH] - Provide robust alternatives for replace_string