Re: BRIN INDEX value - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: BRIN INDEX value
Date
Msg-id CAA4eK1+R2snN09_7b9TVgY-Ke6T8Z+oZz+pVU5ULxofeWTo33w@mail.gmail.com
Whole thread Raw
In response to Re: BRIN INDEX value  (Tatsuo Ishii <ishii@postgresql.org>)
Responses Re: BRIN INDEX value  (Tatsuo Ishii <ishii@postgresql.org>)
List pgsql-hackers
On Fri, Sep 4, 2015 at 10:03 AM, Tatsuo Ishii <ishii@postgresql.org> wrote:
>
> I have looked into your patch and am a little bit worried because it
> calls RelationGetNumberOfBlocks() which is an expensive function.
> I think there are two ways to avoid it.
>
> 1) fall back to your former patch. However it may break existing
>    behavior what you said. I think there's very little chance it
>    actually happens because IndexBuildHeapRangeScan() is only used by
>    brin (I confirmed this). But Alvaro said some patches may be it's
>    customers. Robert, Amit, Can you please confirm this?
>

In earlier version of parallel_seqscan patch, heap_setscanlimits() was being
used, but now altogether a different mechanism is used.


With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: Freeze avoidance of very large table.
Next
From: Fujii Masao
Date:
Subject: gin_fuzzy_search_limit and postgresql.conf.sample