| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Andrey Borodin <amborodin86(at)gmail(dot)com> |
| Cc: | Rinat Shigapov <rinatshigapov(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Too coarse predicate locks granularity for B+ tree indexes |
| Date: | 2023-02-07 21:44:36 |
| Message-ID: | CA+hUKGKsivovnNAYyzQ6abpgKh_1c=qScgwDPACHHdnMVDRD4w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Wed, Feb 8, 2023 at 5:25 AM Andrey Borodin <amborodin86(at)gmail(dot)com> wrote:
> On Tue, Feb 7, 2023 at 4:01 AM Rinat Shigapov <rinatshigapov(at)gmail(dot)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(at){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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2023-02-07 21:51:08 | Re: Too coarse predicate locks granularity for B+ tree indexes |
| Previous Message | Peter J. Holzer | 2023-02-07 21:42:30 | Re: PostgreSQL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2023-02-07 21:51:08 | Re: Too coarse predicate locks granularity for B+ tree indexes |
| Previous Message | Kirk Wolak | 2023-02-07 21:08:02 | Re: possible proposal plpgsql GET DIAGNOSTICS oid = PG_ROUTINE_OID |