Re: pgsql: Add pg_atomic_unlocked_write_u64

From: Andres Freund <andres(at)anarazel(dot)de>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Add pg_atomic_unlocked_write_u64
Date: 2025-12-09 04:12:34
Message-ID: 6ed3f3j3kufkiy5u2kdh7fv2oaqasyk4csapunkbswlikvpg7e@zqnn4qir2kjg
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Hi,

On 2025-12-04 12:41:26 -0600, Nathan Bossart wrote:
> On Thu, Dec 04, 2025 at 01:15:55PM -0500, Tom Lane wrote:
> > LGTM otherwise.
>
> +1

Thanks for the reviews Tom and Nathan. Pushed with minor further tweaks
(s/due to/via/, s/concurent/concurrent/).

Greetings,

Andres Freund

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2025-12-09 05:53:54 pgsql: Use palloc_object() and palloc_array() in more areas of the tree
Previous Message Andres Freund 2025-12-09 04:12:30 pgsql: Improve documentation for pg_atomic_unlocked_write_u32()

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-12-09 04:16:32 Re: BUG #19095: Test if function exit() is used fail when linked static
Previous Message Nitin Jadhav 2025-12-09 04:00:41 Re: Fix crash during recovery when redo segment is missing