Re: Spinlocks and compiler/memory barriers - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Spinlocks and compiler/memory barriers
Date
Msg-id 20140628134543.GG6450@awork2.anarazel.de
Whole thread Raw
In response to Re: Spinlocks and compiler/memory barriers  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On 2014-06-28 15:41:46 +0200, Andres Freund wrote:
> On 2014-06-28 09:25:32 -0400, Robert Haas wrote:
> > No, I think it's going to be *much* simpler than that.  How about I
> > take a crack at this next week and then either (a) I'll see why it's a
> > bad idea and we can go from there or (b) you can review what I come up
> > with and tell me why it sucks?
> 
> Ok. I think that's going in the wrong direction (duplication of
> nontrivial knowledge), but maybe I'm taking a to 'purist' approach
> here. Prove me wrong :)

What I forgot: I'm also pretty sure that the more lockless stuff we
introduce the more places are going to need acquire/release semantics...

Greetings,

Andres Freund

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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Spinlocks and compiler/memory barriers
Next
From: Kevin Grittner
Date:
Subject: Re: delta relations in AFTER triggers