hi,
On 10/27/2017 09:34 AM, Simon Riggs wrote:
> On 27 October 2017 at 07:20, Robert Haas <robertmhaas@gmail.com> wrote:
>> On Thu, Oct 19, 2017 at 10:15 PM, Tomas Vondra
>> <tomas.vondra@2ndquadrant.com> wrote:
>>> Let's see a query like this:
>>>
>>> select * from bloom_test
>>> where id = '8db1d4a6-31a6-e9a2-4e2c-0e842e1f1772';
>>>
>>> The minmax index produces this plan
>>>
>>> Heap Blocks: lossy=2061856
>>> Execution time: 22707.891 ms
>>>
>>> Now, the bloom index:
>>>
>>> Heap Blocks: lossy=25984
>>> Execution time: 338.946 ms
>>
>> It's neat to see BRIN being extended like this. Possibly we could
>> consider making it a contrib module rather than including it in core,
>> although I don't have strong feelings about it.
>
> I see that SP-GIST includes two operator classes in core, one default.
>
> Makes sense to do the same thing with BRIN and add this new op class
> as a non-default option in core.
>
Not sure "a number of in-core opclasses" is a good reason to (not) add
new ones. Also, we already have two built-in BRIN opclasses (minmax and
inclusion).
In general, "BRIN bloom" can be packed as a contrib module (at least I
believe so). That's not the case for the "BRIN multi-range" which also
requires some changes to some code in brin.c (but the rest can be moved
to contrib module, of course).
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers