Re: [HACKERS] GSoC 2017 Proposal for predicate locking in hash index - Mailing list pgsql-hackers

From Shubham Barai
Subject Re: [HACKERS] GSoC 2017 Proposal for predicate locking in hash index
Date
Msg-id CALxAEPtFvaZr9_6Ef1Jh7fbFqgPLvDFXnOs_MrLDckPRt+rxuA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] GSoC 2017 Proposal for predicate locking in hash index  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Hi,

On 22 June 2017 at 21:12, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
Shubham Barai wrote:
> Hi,
>
> Now that hash index support write-ahead logging, it will be great if we add
> support for predicate locking to it.
> Implementation of predicate locking in hash index seems very simple.
> I have already made changes in the code. I am currently working on testing.

So if I understand correctly, this would only cause a false positive if
two transactions have a rw/ww conflict in different tuples in the same
bucket.  Is that what we expect?

Yes, I think so. Is there any way to further reduce false positives in the same bucket?

Regards,
Shubham


Sent with Mailtrack

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: [HACKERS] SQL MERGE patches for PostgreSQL Versions
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] possible self-deadlock window after bad ProcessStartupPacket