Re: valgrind versus pg_atomic_init()
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2020-06-09T03:25:09Z
Lists: pgsql-hackers
Hi, On 2020-06-08 18:21:06 -0400, Tom Lane wrote: > > Yea, it could just do that. It seemed slightly easier/clearer, back when > > I wrote it, to just use pg_atomic_write* for the initialization, but > > this seems enough of a reason to stop doing so. Will change it in all > > branches, unless somebody sees a reason to not do so? > > Works for me. And done. - Andres
Commits
-
Avoid need for valgrind suppressions for pg_atomic_init_u64 on some platforms.
- 3801532918eb 9.5.23 landed
- e3c878ffdddc 9.6.19 landed
- 20fd90febc2c 10.14 landed
- fd6daa006e7b 11.9 landed
- 980a3cd48a08 12.4 landed
- de4a25989611 13.0 landed
- 47c718792b88 14.0 landed