Re: Startup process deadlock: WaitForProcSignalBarriers vs aux process
Matthias van de Meent <boekewurm+postgres@gmail.com>
From: Matthias van de Meent <boekewurm+postgres@gmail.com>
To: Masahiko Sawada <sawada.mshk@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-22T23:26:00Z
Lists: pgsql-hackers
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! Kind regards, Matthias van de Meent Databricks