Horton
Menu

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

Álvaro Herrera <alvherre@kurilemu.de>

View thread
From: Álvaro Herrera <alvherre@kurilemu.de>
To: Anthony Hsu <erwaman@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2026-01-30T17:42:27Z
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)

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. postgres_fdw: Add Assert to estimate_path_cost_size().