Re: Set 1s WaitLatch timeout if standby limit has expired in ResolveRecoveryConflictWithBufferPin
Anthony Hsu <erwaman@gmail.com>
From: Anthony Hsu <erwaman@gmail.com>
To: Álvaro Herrera <alvherre@kurilemu.de>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2026-02-22T19:20:50Z
Lists: pgsql-hackers
Attachments
- v2-0001-Set-1s-WaitLatch-timeout-if-standby-limit-has-exp.patch (application/octet-stream) patch v2-0001
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) >
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
postgres_fdw: Add Assert to estimate_path_cost_size().
- 21c9756db645 19 (unreleased) cited