pgsql: Remove volatile from latch API - Mailing list pgsql-committers

From Peter Eisentraut
Subject pgsql: Remove volatile from latch API
Date
Msg-id E1h0kv7-0003Zd-0F@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Remove volatile from latch API

This was no longer useful since the latch functions use memory
barriers already, which are also compiler barriers, and volatile does
not help with cross-process access.

Discussion:
https://www.postgresql.org/message-id/flat/20190218202511.qsfpuj5sy4dbezcw%40alap3.anarazel.de#18783c27d73e9e40009c82f6e0df0974

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/278584b526d71a3fe86f91be5870f99f38477e27

Modified Files
--------------
src/backend/storage/ipc/latch.c | 18 +++++++++---------
src/include/storage/latch.h     | 16 ++++++++--------
2 files changed, 17 insertions(+), 17 deletions(-)


pgsql-committers by date:

Previous
From: Michael Paquier
Date:
Subject: pgsql: Fix error handling of readdir() port implementation on firstfil
Next
From: Alvaro Herrera
Date:
Subject: pgsql: Test partition functions with legacy inheritance children, too