Re: walsender "wakeup storm" on PG16, likely because of bc971f4025c (Optimize walsender wake up logic using condition variables) - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: walsender "wakeup storm" on PG16, likely because of bc971f4025c (Optimize walsender wake up logic using condition variables)
Date
Msg-id CA+hUKGLizA9-Hms7Co5P4UEiHJStCmuOg73PQ_+bRqUj-v27jA@mail.gmail.com
Whole thread Raw
In response to Re: walsender "wakeup storm" on PG16, likely because of bc971f4025c (Optimize walsender wake up logic using condition variables)  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
Responses Re: walsender "wakeup storm" on PG16, likely because of bc971f4025c (Optimize walsender wake up logic using condition variables)
List pgsql-hackers
On Tue, Aug 15, 2023 at 2:23 AM Tomas Vondra
<tomas.vondra@enterprisedb.com> wrote:
> I'm not familiar with the condition variable code enough to have an
> opinion, but the patch seems to resolve the issue for me - I can no
> longer reproduce the high CPU usage.

Thanks, pushed.



pgsql-hackers by date:

Previous
From: Juan Rodrigo Alejandro Burgos Mella
Date:
Subject: ECPG Semantic Analysis
Next
From: Bruce Momjian
Date:
Subject: Re: PG 16 draft release notes ready