Request a Demo
Home   >   mailing lists

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

From Matthias van de Meent
Subject Re: Startup process deadlock: WaitForProcSignalBarriers vs aux process
Date
Msg-id CAEze2WgZoa2Wu4GM=7_buiY9=oGz4w7FynoqFBp=PNdaCsNstw@mail.gmail.com
Whole thread
In response to Startup process deadlock: WaitForProcSignalBarriers vs aux process  (Matthias van de Meent <boekewurm+postgres@gmail.com>)
Responses Re: Startup process deadlock: WaitForProcSignalBarriers vs aux process
List pgsql-hackers
Tree view 
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

pgsql-hackers by date:

Previous
From: Japin Li
Date:
Subject: Re: [PATCH] Add pg_get_policy_ddl() function to reconstruct CREATE POLICY statement
Next
From: Chao Li
Date:
Subject: Re: Fix pg_stat_wal_receiver to show CONNECTING status