Re: Set 1s WaitLatch timeout if standby limit has expired in ResolveRecoveryConflictWithBufferPin - Mailing list pgsql-hackers

From Anthony Hsu
Subject Re: Set 1s WaitLatch timeout if standby limit has expired in ResolveRecoveryConflictWithBufferPin
Date
Msg-id CALQc50inhua_-5a1ALjhoFYCXjToGS5UAGyDoVBN1CcGdo3f_Q@mail.gmail.com
Whole thread Raw
In response to Re: Set 1s WaitLatch timeout if standby limit has expired in ResolveRecoveryConflictWithBufferPin  (Álvaro Herrera <alvherre@kurilemu.de>)
List pgsql-hackers
Thanks Álvaro for creating a commitfest entry. I've rebased my patch on master to fix the build issues. Also made some minor code comment changes and added a detailed commit message. Please let me know if you have any feedback or questions.

-Anthony

On Fri, Jan 30, 2026 at 9:42 AM Álvaro Herrera <alvherre@kurilemu.de> wrote:
On 2025-Jul-06, Anthony Hsu wrote:

> Hi,
>
> I think there is a race scenario where a backend holding a conflicting
> buffer pin isn't promptly canceled even when the standby limit has expired:

This patch seems to hav efallen through the cracks.  I created a
commitfest entry for it,
https://commitfest.postgresql.org/patch/6445/




--
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"No tengo por qué estar de acuerdo con lo que pienso"
                             (Carlos Caszeli)
Attachment

pgsql-hackers by date:

Previous
From: Alexandre Felipe
Date:
Subject: Re: index prefetching
Next
From: Peter Geoghegan
Date:
Subject: Re: index prefetching