Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1X6R6y-000641-Fe for pgsql-hackers@arkaria.postgresql.org; Sun, 13 Jul 2014 21:15:08 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1X6R6x-0000Xh-TN for pgsql-hackers@arkaria.postgresql.org; Sun, 13 Jul 2014 21:15:07 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1X6R6v-0000Wb-V4 for pgsql-hackers@postgresql.org; Sun, 13 Jul 2014 21:15:06 +0000 Received: from mail.anarazel.de ([217.115.131.40]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1X6R6r-0008Ck-CZ for pgsql-hackers@postgresql.org; Sun, 13 Jul 2014 21:15:04 +0000 Received: from intern.anarazel.de (static-243-200-78-212.thenetworkfactory.nl [212.78.200.243]) (Authenticated sender: andres@anarazel.de) by mail.anarazel.de (Postfix) with ESMTPSA id 2177F4F0004; Sun, 13 Jul 2014 23:14:58 +0200 (CEST) Date: Sun, 13 Jul 2014 21:20:23 +0200 From: Andres Freund To: Amit Kapila Cc: Robert Haas , Tom Lane , Peter Geoghegan , Pg Hackers , Ants Aasma Subject: Re: better atomics - v0.5 Message-ID: <20140713192023.GJ1136@alap3.anarazel.de> References: <20140629092421.GH6450@awork2.anarazel.de> <20140630092401.GJ21422@awork2.anarazel.de> <20140701104058.GZ26930@awork2.anarazel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org 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