Re: Set 1s WaitLatch timeout if standby limit has expired in ResolveRecoveryConflictWithBufferPin

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Anthony Hsu <erwaman(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Set 1s WaitLatch timeout if standby limit has expired in ResolveRecoveryConflictWithBufferPin
Date: 2026-01-30 17:42:27
Message-ID: 202601301739.kgakwiqulimr@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2026-01-30 18:06:30 Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta
Previous Message Andres Freund 2026-01-30 17:20:01 Re: Refactor how we form HeapTuples for CatalogTuple(Insert|Update)