| From: | Anthony Hsu <erwaman(at)gmail(dot)com> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Set 1s WaitLatch timeout if standby limit has expired in ResolveRecoveryConflictWithBufferPin |
| Date: | 2026-02-22 19:20:50 |
| Message-ID: | CALQc50inhua_-5a1ALjhoFYCXjToGS5UAGyDoVBN1CcGdo3f_Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)kurilemu(dot)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 | Content-Type | Size |
|---|---|---|
| v2-0001-Set-1s-WaitLatch-timeout-if-standby-limit-has-exp.patch | application/octet-stream | 5.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2026-02-22 19:28:00 | Re: index prefetching |
| Previous Message | Alexandre Felipe | 2026-02-22 16:23:11 | Re: index prefetching |