Re: BRIN INDEX value

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: amit(dot)kapila16(at)gmail(dot)com
Cc: Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp, pgsql-hackers(at)postgresql(dot)org
Subject: Re: BRIN INDEX value
Date: 2015-09-04 08:53:32
Message-ID: 20150904.175332.2161241032515084861.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Fri, Sep 4, 2015 at 10:03 AM, Tatsuo Ishii <ishii(at)postgresql(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2015-09-04 09:41:51 Re: Declarative partitioning
Previous Message Fujii Masao 2015-09-04 08:48:56 gin_fuzzy_search_limit and postgresql.conf.sample