Re: Too coarse predicate locks granularity for B+ tree indexes - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Too coarse predicate locks granularity for B+ tree indexes
Date
Msg-id CA+hUKGKsivovnNAYyzQ6abpgKh_1c=qScgwDPACHHdnMVDRD4w@mail.gmail.com
Whole thread Raw
In response to Re: Too coarse predicate locks granularity for B+ tree indexes  (Andrey Borodin <amborodin86@gmail.com>)
Responses Re: Too coarse predicate locks granularity for B+ tree indexes
List pgsql-hackers
On Wed, Feb 8, 2023 at 5:25 AM Andrey Borodin <amborodin86@gmail.com> wrote:
> On Tue, Feb 7, 2023 at 4:01 AM Rinat Shigapov <rinatshigapov@gmail.com> wrote:
> > Thomas, thank you for the details!
> >
> > Have you kept the branch that you used to generate the patch? Which commit should the patch apply to?
>
> You can try something like
> git checkout 'master@{2018-05-13 13:37:00}'
> to get a commit by date from rev-parse.

I don't have time to work on this currently but if Rinat or others
want to look into it... maybe I should rebase that experiment on top
of current master.  Here's the branch:

https://github.com/macdice/postgres/tree/ssi-index-locking-refinements



pgsql-hackers by date:

Previous
From: Kirk Wolak
Date:
Subject: Re: possible proposal plpgsql GET DIAGNOSTICS oid = PG_ROUTINE_OID
Next
From: Thomas Munro
Date:
Subject: Re: Too coarse predicate locks granularity for B+ tree indexes