Cond: ((id >= 900) AND (r >= 1) AND (r <= 1))
Planning Time: 0.393 ms
Execution Time: 0.280 ms
(7 rows)
From: Chris Wilson
Sent: 21 June 2019 10:20
To: 'Simon Riggs'
Cc: pgsql-performa...@postgresql.org
Subject: RE: EXPLAIN ANALYZE of BRIN bitmap index scan with disjunction
That makes perfect sense, thanks Simon!
Chris.
From: Simon Riggs
Sent: 21 June 2019 10:17
To: Chris Wilson
Cc: pgsql-performa...@postgresql.org
Subject: Re: EXPLAIN ANALYZE of BRIN bitmap index scan with disjunction
On Thu, 20 Jun 2019 at 16:13, Chris Wilson
mailto:chris.wil
. that the BRIN index
performs much worse when we try to query on this column as well.
Thanks, Chris.
From: Simon Riggs
Sent: 20 June 2019 16:57
To: Chris Wilson
Cc: pgsql-performa...@postgresql.org
Subject: Re: EXPLAIN ANALYZE of BRIN bitmap index scan with disjunction
On Thu, 20 Jun 2019 at 16
Dear Postgres performance experts,
I noticed that when I added a BRIN index to a very large table, attempting to
make a particular query faster, it became much slower instead. While trying to
understand this, I noticed that the actual number of rows in the EXPLAIN
ANALYZE output was much higher
