Re: [PATCH] Prevent repeated deadlock-check signals in standby buffer pin waits - Mailing list pgsql-hackers

From JoongHyuk Shin
Subject Re: [PATCH] Prevent repeated deadlock-check signals in standby buffer pin waits
Date
Msg-id CACSdjfNkUn07Xgf1oztzvO2p0yxvGkaVUtxtXUzkGPopPtwuzg@mail.gmail.com
Whole thread
In response to Re: [PATCH] Prevent repeated deadlock-check signals in standby buffer pin waits  (Andrey Borodin <x4mmm@yandex-team.ru>)
List pgsql-hackers
Hi Andrey,

Thanks for looking at this, and for handling the CF entry.

On Mon, Aug 31, 2026 at 2:19 AM Andrey Borodin <x4mmm@yandex-team.ru> wrote:
> One point seems worth recording for the
> next version: Xuneng's June 29 lost-wakeup and reply-stall interleaving
> has not been answered in this thread.  Could the rebased patch either
> lose that race or explain why it cannot occur?

It closes it. The prerequisite patch is still under review and may
change, but as of its latest version it already implements the
recheck-after-wake Xuneng proposed. The wait loop checks the buffer's
pin count directly after every wakeup and re-registers the waiter flag
before sleeping again, so a coalesced wakeup can no longer leave the
startup process waiting for a signal that will never arrive.

Thank you.

-- 
JH Shin

pgsql-hackers by date:

Previous
From: Ewan Young
Date:
Subject: Re: Use pg_neg_s*_overflow() for open-coded negation overflow checks
Next
From: Ewan Young
Date:
Subject: Re: pg_restore_attribute_stats() accepts non-finite values