Re: Spinlocks and compiler/memory barriers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Mark Cave-Ayland <mark(dot)cave-ayland(at)ilande(dot)co(dot)uk>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Spinlocks and compiler/memory barriers
Date: 2014-07-02 00:21:37
Message-ID: 14348.1404260497@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> On 2014-07-01 23:21:07 +0100, Mark Cave-Ayland wrote:
>> Also if you're struggling for Sun buildfarm animals, recent versions of QEMU
>> will quite happily install and run later versions of 32-bit Solaris over
>> serial, and 2.0 even manages to give you a cgthree framebuffer for the full
>> experience.

> Well. I have to admit I'm really not interested in investing that much
> time in something I've no stake in. If postgres developers have to put
> emulated machines to develop features something imo went seriously
> wrong. That's more effort than at least I'm willing to spend.

Perhaps more to the point, I have no faith at all that an emulator will
mimic multiprocessor timing behavior to the level of detail needed to
tell whether memory-barrier-related logic works. See the VAX discussion
just a couple days ago.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-07-02 00:35:16 Re: buildfarm and "rolling release" distros
Previous Message Gurjeet Singh 2014-07-02 00:18:07 Re: Proposing pg_hibernate