Re: Startup process deadlock: WaitForProcSignalBarriers vs aux process - Mailing list pgsql-hackers

From Masahiko Sawada
Subject Re: Startup process deadlock: WaitForProcSignalBarriers vs aux process
Date
Msg-id CAD21AoAE216FOGgz2UmOQ4acTj7Mm=6wMcAM_MNaMVTByHCSFQ@mail.gmail.com
Whole thread
In response to Re: Startup process deadlock: WaitForProcSignalBarriers vs aux process  (Matthias van de Meent <boekewurm+postgres@gmail.com>)
List 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



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: s/pg_attribute_always_inline/pg_always_inline/?
Next
From: Roberto Mello
Date:
Subject: Re: DBeaver Experiencing timeouts while connecting to New Linux PostgreSql server