Re: Freezing without write I/O - Mailing list pgsql-hackers

From Ants Aasma
Subject Re: Freezing without write I/O
Date
Msg-id CA+CSw_vYdvZEURnwrf02kVyxfKWiOSsK6H7zA-jiH+yLRmwdPQ@mail.gmail.com
Whole thread Raw
In response to Re: Freezing without write I/O  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On Tue, Oct 1, 2013 at 2:13 PM, Andres Freund <andres@2ndquadrant.com> wrote:
> Agreed. The "wait free LW_SHARED" thing[1] I posted recently had a simple
>
> #define pg_atomic_read(atomic) (*(volatile uint32 *)&(atomic))
>
> That should be sufficient and easily greppable, right?

Looks good enough for me. I would consider using a naming scheme that
accounts for possible future uint64 atomics.

Regards,
Ants Aasma
--
Cybertec Schönig & Schönig GmbH
Gröhrmühlgasse 26
A-2700 Wiener Neustadt
Web: http://www.postgresql-support.de



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Cmpact commits and changeset extraction
Next
From: Andres Freund
Date:
Subject: Re: [PERFORM] Cpu usage 100% on slave. s_lock problem.