Re: WIP: BRIN bloom indexes

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WIP: BRIN bloom indexes
Date: 2017-10-27 05:20:32
Message-ID: CA+TgmoajaQKBUx=vaTUFo6z80dsRzBw__Nu41Q4t06baZep3Ug@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 19, 2017 at 10:15 PM, Tomas Vondra
<tomas(dot)vondra(at)2ndquadrant(dot)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.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2017-10-27 05:30:11 Re: proposal: schema variables
Previous Message Robert Haas 2017-10-27 05:11:14 Re: [PATCH] Lockable views