| From: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | Alexander Lakhin <exclusion(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| Subject: | Re: Startup process deadlock: WaitForProcSignalBarriers vs aux process |
| Date: | 2026-05-22 23:26:00 |
| Message-ID: | CAEze2WgZoa2Wu4GM=7_buiY9=oGz4w7FynoqFBp=PNdaCsNstw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 14 May 2026 at 14:48, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chao Li | 2026-05-22 23:55:39 | Re: Fix pg_stat_wal_receiver to show CONNECTING status |
| Previous Message | Michael Paquier | 2026-05-22 23:23:00 | Re: Fix pg_stat_wal_receiver to show CONNECTING status |