Re: pg_threads.h take II

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Jelte Fennema <postgres(at)jeltef(dot)nl>, Bryan Green <dbryan(dot)green(at)gmail(dot)com>
Subject: Re: pg_threads.h take II
Date: 2026-07-06 12:32:12
Message-ID: CA+hUKG+e3Obh98PauhmcgkfNAkPR=7Om6Y6BbwwfSbSJiR2TmA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jul 7, 2026 at 12:09 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> used here isn't what we want to go with for the future, but to do it
> the way Heikki and Jelte are suggesting will probably require deciding
> how to access atomics or at least compiler barrires in front-end code,
> which I'll look into this week.

Correction: at least memory barriers

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2026-07-06 12:38:48 Re: clean up size_t/ssize_t use with POSIX file system APIs
Previous Message Peter Eisentraut 2026-07-06 12:31:57 Re: pg_threads.h take II