public inbox for [email protected]  

help / color / mirror / Atom feed

From: Thom Brown <[email protected]>
To: Nathan Bossart <[email protected]>
Cc: Heikki Linnakangas <[email protected]>
Cc: [email protected]
Subject: Re: pgsql: Refactor how some aux processes advertise their ProcNumber
Date: Thu, 9 Jul 2026 12:09:23 +0100
Message-ID: <CAA-aLv6QWteZC6xnv=7K0ojR2f8SkOZBYp2VQ-ELuxf4ygvEkg@mail.gmail.com> (raw)
In-Reply-To: <ak8RP8xn5_H0BrJV@nathan>
References: <[email protected]>
	<ak8RP8xn5_H0BrJV@nathan>

On Thu, 9 Jul 2026 at 04:11, Nathan Bossart <[email protected]> wrote:
>
> On Wed, Jul 08, 2026 at 05:43:01PM +0000, Heikki Linnakangas wrote:
> > Switch to pg_atomic_uint32 for the fields. Seems easier to reason
> > about than volatile pointers. There was some precedence for that, as
> > were already using pg_atomic_uint32 for the procArrayGroupFirst and
> > clogGroupFirst fields, which also store ProcNumbers.
>
> Since removing volatile qualifiers is on my mind, I noticed that this patch
> makes it possible to remove two more.  Patch attached.

+1

view thread (8+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: pgsql: Refactor how some aux processes advertise their ProcNumber
  In-Reply-To: <CAA-aLv6QWteZC6xnv=7K0ojR2f8SkOZBYp2VQ-ELuxf4ygvEkg@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox