Re: segfault in hot standby for hash indexes

From: Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Subject: Re: segfault in hot standby for hash indexes
Date: 2017-03-28 01:02:38
Message-ID: CAE9k0PmZPG5FRdN92BGDuAc0Rqny+WPtO5aRv3KO_hUv4Sjuwg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mar 27, 2017 22:25, "Robert Haas" <robertmhaas(at)gmail(dot)com> wrote:

On Fri, Mar 24, 2017 at 3:49 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
wrote:
> On Fri, Mar 24, 2017 at 12:25 PM, Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>
wrote:
>>>
>>> I think it would have been probably okay to use *int* for ntuples as
>>> that matches with what you are actually assigning in the function.
>>
>> okay, corrected it. Attached is newer version of patch.
>
> Thanks, this version looks good to me.

Committed.

Thank you.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2017-03-28 01:06:46 Re: [POC] hash partitioning
Previous Message Amit Langote 2017-03-28 00:59:30 Re: Partitioned tables and relfilenode