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

From Alvaro Herrera
Subject Re: [HACKERS] GSoC 2017 Proposal for predicate locking in hash index
Date
Msg-id 20170622154252.cazet5q4rpdm6umv@alvherre.pgsql
Whole thread Raw
In response to [HACKERS] GSoC 2017 Proposal for predicate locking in hash index  (Shubham Barai <shubhambaraiss@gmail.com>)
Responses Re: [HACKERS] GSoC 2017 Proposal for predicate locking in hash index  (Shubham Barai <shubhambaraiss@gmail.com>)
List pgsql-hackers
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?

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] [patch] pg_dump/pg_restore zerror() and strerror()mishap
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] PATCH: Batch/pipelining support for libpq