On Wed, Feb 8, 2023 at 10:44 AM Thomas Munro wrote:
> On Wed, Feb 8, 2023 at 5:25 AM Andrey Borodin wrote:
> > On Tue, Feb 7, 2023 at 4:01 AM Rinat Shigapov
> > wrote:
> > > Thomas, thank you for the details!
> > >
> > > Have you kept the branch that you used to generate the patch? Which
> >
On Wed, Feb 8, 2023 at 5:25 AM Andrey Borodin wrote:
> On Tue, Feb 7, 2023 at 4:01 AM Rinat Shigapov 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
>
On Tue, Feb 7, 2023 at 4:01 AM Rinat Shigapov 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
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?
With kindest regards, Rinat Shigapov
вт, 7 февр. 2023 г. в 17:11, Thomas Munro :
> On Tue, Feb 7, 2023 at 11:24 PM Rinat Shigapov
> wrote:
> > Does the
On Tue, Feb 7, 2023 at 11:24 PM Rinat Shigapov wrote:
> Does the current PostgreSQL release support B+ tree index predicate locks
> more granular then page-level locks?
No. I tried to follow some breadcrumbs left by Kevin and Dan that
should allow unique index scans that find a match to skip
