Re: Typo in README.barrier - Mailing list pgsql-hackers

From David Rowley
Subject Re: Typo in README.barrier
Date
Msg-id CAApHDvq-FM66Biqqez8w-3Ryk5SBvkB18919mGAsh7uthTuKww@mail.gmail.com
Whole thread Raw
In response to Re: Typo in README.barrier  (Tatsuo Ishii <ishii@sraoss.co.jp>)
Responses Re: Typo in README.barrier
List pgsql-hackers
On Mon, 17 May 2021 at 01:29, Tatsuo Ishii <ishii@sraoss.co.jp> wrote:
> Yes, we'd better to fix them. Attached is a propsal for these.

Thanks for working on that.  I had a look and wondered if it might be
better to go into slightly less details about the exact atomic
function to use.  The wording there might lead you to believe you can
just call the atomic function on the non-atomic variable.

It might be best just to leave the details about how exactly to use
atomics by just referencing port/atomics.h.

Maybe something like the attached?

I'm also a bit on the fence if this should be backpatched or not.  The
reasons though maybe not is that it seems unlikely maybe people would
not be working in master if they're developing something new.   On the
other side of the argument, 0ccebe779, which adjusts another README
was backpatched.  I'm leaning towards backpatching.

David

Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: prion failed with ERROR: missing chunk number 0 for toast value 14334 in pg_toast_2619
Next
From: Justin Pryzby
Date:
Subject: Re: terminate called after throwing an instance of 'std::bad_alloc'