Re: segfault in hot standby for hash indexes - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: segfault in hot standby for hash indexes
Date
Msg-id CAMkU=1xX-q-PzL=v6mfGoKq2Fya=FqdMW48+_fTEzcArqET_Ww@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] segfault in hot standby for hash indexes  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Fri, Mar 24, 2017 at 12:49 AM, Amit Kapila <amit.kapila16@gmail.com> wrote:
On Fri, Mar 24, 2017 at 12:25 PM, Ashutosh Sharma <ashu.coek88@gmail.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.

It solves the problem for me.  I'd like to test that I get the right answer on the standby, not just the absence of a crash, but I don't know how to do that effectively.  Has anyone used the new wal replay block consistency tool on hash indexes since this microvacuum code was committed?

Jeff

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: WIP: Faster Expression Processing v4
Next
From: Robert Haas
Date:
Subject: Re: crashes due to setting max_parallel_workers=0