pgsql: Remove volatile from latch API

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Remove volatile from latch API
Date: 2019-03-04 10:34:05
Message-ID: E1h0kv7-0003Zd-0F@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2019-03-04 18:54:30 pgsql: Test partition functions with legacy inheritance children, too
Previous Message Michael Paquier 2019-03-04 00:51:35 pgsql: Fix error handling of readdir() port implementation on first fil