| From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
|---|---|
| To: | Matthias van de Meent <boekewurm+postgres(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-27 23:28:13 |
| Message-ID: | CAD21AoAE216FOGgz2UmOQ4acTj7Mm=6wMcAM_MNaMVTByHCSFQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 22, 2026 at 4:26 PM Matthias van de Meent
<boekewurm+postgres(at)gmail(dot)com> wrote:
>
> 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!
>
Pushed the fix down to v15. Thank you for reviewing the patches!
Regards,
--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Roberto Mello | 2026-05-27 23:49:14 | Re: DBeaver Experiencing timeouts while connecting to New Linux PostgreSql server |
| Previous Message | Matheus Alcantara | 2026-05-27 23:25:12 | Re: postgres_fdw: Use COPY to speed up batch inserts |