Re: BRIN INDEX value - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject Re: BRIN INDEX value
Date
Msg-id 20150904.175332.2161241032515084861.t-ishii@sraoss.co.jp
Whole thread Raw
In response to Re: BRIN INDEX value  (Amit Kapila <amit.kapila16@gmail.com>)
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.

Thank you for the confirmation!

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: gin_fuzzy_search_limit and postgresql.conf.sample
Next
From: Simon Riggs
Date:
Subject: Re: Declarative partitioning