pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Andres Freund <andres@2ndquadrant.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Geoghegan <pg@heroku.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Cc: Ants Aasma <ants@cybertec.at>
Subject: Re: better atomics - v0.5
Date: Sun, 13 Jul 2014 21:20:23 +0200
Message-ID: <20140713192023.GJ1136@alap3.anarazel.de> (raw)
In-Reply-To: <CAA4eK1LSzPPiBfJVPC2dLuuvgdgz2sWO_pBwpdkgC=75OP2XeA@mail.gmail.com>
References: <CAA4eK1+j2xp-xGLh2M8xATnv_X=0j1678Pw-wuGy1O8Kw-qWnw@mail.gmail.com>
	<20140629092421.GH6450@awork2.anarazel.de>
	<CAA4eK1JqqqZuqvKzfUB-XX381xxfGYHSCVmtYA307GKf5X1uyQ@mail.gmail.com>
	<20140630092401.GJ21422@awork2.anarazel.de>
	<CAA4eK1Jygpgm-uCz4Hj+wQ8mfPP6rJ102326H5=OMgzfpktgoA@mail.gmail.com>
	<20140701104058.GZ26930@awork2.anarazel.de>
	<CAA4eK1KsUMTErTDf-ht3-Qb7NvkVPGd-=Uy7NrEi2oviJgk9tA@mail.gmail.com>
	<CAA4eK1J9EAn7U5pH0587WmBKceLNzq9jKTZWEY74HBTT4bfq+g@mail.gmail.com>
	<CA+TgmoZCQD50m82NgTeYEr+iSoWdK7_5di8+E8ph67yG4iw9Tw@mail.gmail.com>
	<CAA4eK1LSzPPiBfJVPC2dLuuvgdgz2sWO_pBwpdkgC=75OP2XeA@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

On 2014-07-10 08:46:55 +0530, Amit Kapila wrote:
> As per my understanding of the general theory around barriers,
> read and write are defined to avoid reordering due to compiler and
> full memory barriers are defined to avoid reordering due to
> processors.

No, that's not the case. There's several processors where write/read
barriers are an actual thing on the hardware level.

Greetings,

Andres Freund

-- 
 Andres Freund	                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (58+ messages)  latest in thread

Message-ID: <20140713192023.GJ1136@alap3.anarazel.de>
Permalink:  ../20140713192023.GJ1136@alap3.anarazel.de/
Also on:    postgresql.org/message-id/20140713192023.GJ1136@alap3.anarazel.de

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: andres@2ndquadrant.com, amit.kapila16@gmail.com, robertmhaas@gmail.com, tgl@sss.pgh.pa.us, pg@heroku.com, ants@cybertec.at
  Subject: Re: better atomics - v0.5
  In-Reply-To: <20140713192023.GJ1136@alap3.anarazel.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox