Re: Atomic ops for unlogged LSN

Nathan Bossart <nathandbossart@gmail.com>

From: Nathan Bossart <nathandbossart@gmail.com>

To: John Morris <john.morris@crunchydata.com>

Cc: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, Andres Freund <andres@anarazel.de>, Stephen Frost <sfrost@snowman.net>, Michael Paquier <michael@paquier.xyz>, Robert Haas <robertmhaas@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2023-11-06T20:33:50Z

Lists: pgsql-hackers

Attachments

unlogged_lsn_v4.patch (text/x-diff) patch v4

On Wed, Nov 01, 2023 at 10:40:06PM -0500, Nathan Bossart wrote:
> Since this isn't a tremendously performance-sensitive area, IMHO we should
> code defensively to eliminate any doubts about correctness and to make it
> easier to reason about.

Concretely, like this.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com

Commits

Convert unloggedLSN to an atomic variable.
- 963d3072af21 17.0 landed
Introduce atomic read/write functions with full barrier semantics.
- bd5132db558b 17.0 cited