| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi> |
| Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Refactor how some aux processes advertise their ProcNumber |
| Date: | 2026-07-09 03:10:55 |
| Message-ID: | ak8RP8xn5_H0BrJV@nathan |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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.
--
nathan
| Attachment | Content-Type | Size |
|---|---|---|
| remove_more_volatile.patch | text/plain | 1.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2026-07-09 05:40:27 | pgsql: Reject incorrect range_bounds_histograms in stats import functio |
| Previous Message | Amit Kapila | 2026-07-09 02:55:59 | pgsql: Doc: Clarify sequence synchronization commands. |