Re: WIP: BRIN bloom indexes
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-10-27T05:20:32Z
Lists: pgsql-hackers
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. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
BRIN minmax-multi indexes
- ab596105b55f 14.0 landed
-
BRIN bloom indexes
- 77b88cd1bb90 14.0 landed