Horton

Re: Startup process deadlock: WaitForProcSignalBarriers vs aux process

Masahiko Sawada <sawada.mshk@gmail.com>

View thread
From: Masahiko Sawada <sawada.mshk@gmail.com>
To: Matthias van de Meent <boekewurm+postgres@gmail.com>
Cc: Alexander Lakhin <exclusion@gmail.com>, Andres Freund <andres@anarazel.de>, Thomas Munro <thomas.munro@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Heikki Linnakangas <hlinnaka@iki.fi>, Andrey Borodin <x4mmm@yandex-team.ru>
Date: 2026-05-27T23:28:13Z
Lists: pgsql-hackers 
On Fri, May 22, 2026 at 4:26 PM Matthias van de Meent
<boekewurm+postgres@gmail.com> wrote:
>
> On Thu, 14 May 2026 at 14:48, Masahiko Sawada <sawada.mshk@gmail.com> wrote:
> >
> > While reviewing the patches, I realized that it would be better to use
> > pg_atomic_write_membarrier_u32() instead of pg_atomic_write_u32() +
> > pg_memory_barrier() where available. I've updated the patch for master
> > and 18, and slightly commit messages.
>
> LGTM, thanks for getting this fixed!
>

Pushed the fix down to v15. Thank you for reviewing the patches!

Regards,

-- 
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com