| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: BRIN INDEX value |
| Date: | 2015-09-04 04:05:48 |
| Message-ID: | 55E9189C.4070806@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/4/2015 12:01 PM, Alvaro Herrera wrote:
> Amit Langote wrote:
>> On 9/4/2015 9:22 AM, Tatsuo Ishii wrote:
>>>
>>> 3) I wonder if other index type is suffered by this type of bug.
>>>
>>
>> About 3, it seems unlikely. Both the IndexBuildHeapRangeScan() and
>> heap_setscanlimits() were introduced by the BRIN patch and I didn't find
>> anything else using it, yet.
>
> As I recall, there's some patch that Robert Haas or Amit Kapila that
> wants to use that function. Maybe something in the parallel seqscan
> patch series?
I just checked Amit Kapila's latest[1] patch, and found they have since
abandoned the heap_setscanlimits() approach.
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shulgin, Oleksandr | 2015-09-04 04:08:03 | Re: Proposal: Implement failover on libpq connect level. |
| Previous Message | Michael Paquier | 2015-09-04 04:02:11 | Re: Fwd: Core dump with nested CREATE TEMP TABLE |