From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Chris Wilson <chris(dot)wilson(at)cantabcapital(dot)com> |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: EXPLAIN ANALYZE of BRIN bitmap index scan with disjunction |
Date: | 2019-06-20 16:18:33 |
Message-ID: | CANP8+j++Vhbwh1V0hxrA_jeMzxuzzFh833-ere-iuob0KDE=Wg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, 20 Jun 2019 at 17:01, Chris Wilson <chris(dot)wilson(at)cantabcapital(dot)com>
wrote:
> I deliberately included r in the index, to demonstrate the issue that I’m
> seeing. I know that there is very little locality in this particular,
> dummy, arbitrary test case. I can try to produce a test case that has some
> locality, but I expect it to show exactly the same results, i.e. that the
> BRIN index performs much worse when we try to query on this column as well.
>
I'm suggesting that adding the second column to the index is the source of
your problem, not adding the column to the query.
How does it perform with just the id column in the index?
--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Solutions for the Enterprise
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2019-06-20 16:30:44 | Re: EXPLAIN ANALYZE of BRIN bitmap index scan with disjunction |
Previous Message | Chris Wilson | 2019-06-20 16:00:43 | RE: EXPLAIN ANALYZE of BRIN bitmap index scan with disjunction |