Re: Status of 64 bit atomics - Mailing list pgsql-hackers

From Arthur Silva
Subject Re: Status of 64 bit atomics
Date
Msg-id CAO_YK0XSEu8-zcQgYDyvUgtOi1i6QzW_+uqFv1rRtAQHOJUxOw@mail.gmail.com
Whole thread Raw
In response to Status of 64 bit atomics  (John Gorman <johngorman2@gmail.com>)
List pgsql-hackers
<div dir="ltr"><p dir="ltr"><br /> On May 27, 2016 5:01 PM, "John Gorman" <<a href="mailto:johngorman2@gmail.com"
target="_blank">johngorman2@gmail.com</a>>wrote:<br /> ><br /> > Hi All<br /> ><br /> > Someone recently
toldme that the postgresql atomics library was incomplete<br /> > for 64 bit operations such
as pg_atomic_fetch_add_u64()and should not be used.<br /> ><br /> > Can someone definitively confirm whether it
isokay to rely on the 64 bit atomics<br /> > or whether it is better to protect 64 bit operations with a
spinlock?<br/> ><br /> > Thanks!<br /> > John<p dir="ltr">Golang has asm implementations for these even on
32bitplatforms (see <a
href="https://github.com/golang/go/tree/master/src/sync/atomic">https://github.com/golang/go/tree/master/src/sync/atomic</a>).<p
dir="ltr">Couldn'twe borrow them? Or even better, fall back to spin lock on these, but transparently. </div> 

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [PROPOSAL] Move all am-related reloption code into src/backend/access/[am-name] and get rid of relopt_kind
Next
From: Andres Freund
Date:
Subject: Re: Status of 64 bit atomics