Re: WIP: BRIN multi-range indexes
Tomas Vondra <tomas.vondra@2ndquadrant.com>
From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Alexander Korotkov <a.korotkov@postgrespro.ru>, Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@anarazel.de>, Mark Dilger <hornschnorter@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2019-09-14T17:30:49Z
Lists: pgsql-hackers
Attachments
- 0001-Introduce-opclass-parameters.patch.gz (application/gzip) patch 0001
- 0002-Introduce-amattoptions.patch.gz (application/gzip) patch 0002
- 0003-Use-amattoptions-in-contrib-bloom.patch.gz (application/gzip) patch 0003
- 0004-Use-opclass-parameters-in-GiST-tsvector_ops.patch.gz (application/gzip) patch 0004
- 0005-Remove-pg_index.indoption.patch.gz (application/gzip) patch 0005
- 0006-fix-amvalidate.patch.gz (application/gzip) patch 0006
- 0007-Pass-all-keys-to-BRIN-consistent-function-at-once.patch.gz (application/gzip) patch 0007
- 0008-Move-IS-NOT-NULL-checks-to-bringetbitmap.patch.gz (application/gzip) patch 0008
- 0009-Move-processing-of-NULLs-from-BRIN-support-functions.patch.gz (application/gzip) patch 0009
- 0010-BRIN-bloom-indexes.patch.gz (application/gzip) patch 0010
- 0011-BRIN-multi-range-minmax-indexes.patch.gz (application/gzip) patch 0011
On Tue, Sep 03, 2019 at 06:05:04PM -0400, Alvaro Herrera wrote: >On 2019-Jun-11, Tomas Vondra wrote: > >> Attached is this patch series, rebased on top of current master and the >> opclass parameters patch [1]. I previously planned to keep those two >> efforts separate for a while, but I decided to give it a try and the >> breakage is fairly minor so I'll keep it this way - this patch has zero >> chance of getting committed with the opclass parameters patch anyway. >> >> Aside from rebase and changes due to adopting opclass parameters, the >> patch is otherwise unchanged. > >This patch series doesn't apply, but I'm leaving it alone since the >brokenness is the opclass part, for which I have pinged the other >thread. > Attached is an updated version of this patch series, rebased on top of the opclass parameter patches, shared by Nikita a couple of days ago. There's one extra fixup patch, addressing a bug in those patches. Firstly, while I have some comments on the opclass parameters patches (shared in the other thread), I think that patch series is moving in the right direction. After rebase the code is somewhat simpler and easier to read, which is good. I'm sure there's some more work needed on the APIs and so on, but I'm optimistic about that. The rest of this patch series (0007-0011) is mostly unchanged. I've fixed a couple of bugs and added some comments (particularly to the bloom opclass), but that's about it. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
BRIN minmax-multi indexes
- ab596105b55f 14.0 landed
-
BRIN bloom indexes
- 77b88cd1bb90 14.0 landed
-
Support the old signature of BRIN consistent function
- a681e3c107aa 14.0 landed
-
Remove unnecessary pg_amproc BRIN minmax entries
- a68dfa27d42f 14.0 landed
-
Optimize allocations in bringetbitmap
- 8e4b332e88b8 14.0 landed
-
Move IS [NOT] NULL handling from BRIN support functions
- 72ccf55cb99c 14.0 landed
-
Pass all scan keys to BRIN consistent function at once
- a1c649d889bd 14.0 landed
-
Properly detoast data in brin_form_tuple
- d2d3a4bd33d2 9.5.24 landed
- bae31e75f777 9.6.20 landed
- 0b96fc977c5b 10.15 landed
- 895d0f0e8218 11.10 landed
- 8149e9f9a0d6 12.5 landed
- 6a7b55f3716f 13.1 landed
- 7577dd84807a 14.0 landed