Re: Optimizer misses big in 10.4 with BRIN index - Mailing list pgsql-hackers

From Emre Hasegeli
Subject Re: Optimizer misses big in 10.4 with BRIN index
Date
Msg-id CAE2gYzwxkaudNt9S5cxSZv1pdcLhJOj4kHbc3p_ASSYZAdsKDQ@mail.gmail.com
Whole thread Raw
In response to Re: Optimizer misses big in 10.4 with BRIN index  (Arcadiy Ivanov <arcadiy@gmail.com>)
List pgsql-hackers
> So I basically spent most of the time trying to create a reproducible case
> and I can say I failed. I can however reproduce this with specific large
> data set with specific data distribution, but not an artificial one.

The query plans posted that has the statistics prefer Bitmap Index
Scan.  This is not reproduction of the originally posted case.

> ** Wait... What??? "Rows Removed by Index Recheck: 1643390" but data is
> almost sequential! Let's take a look at it.

I don't think it has anything to do with query planning.  Have you
tried "pages_per_range" option of BRIN?


pgsql-hackers by date:

Previous
From: Cynthia Shang
Date:
Subject: Re: Allow COPY's 'text' format to output a header
Next
From: Tom Lane
Date:
Subject: libpq should not look up all host addresses at once