Re: [PERFORM] Cpu usage 100% on slave. s_lock problem. - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: [PERFORM] Cpu usage 100% on slave. s_lock problem.
Date
Msg-id CAHyXU0xRyx8mpTX9S8zbMTuYp54CBzrAQjhwxVyKZqh3_mA7ww@mail.gmail.com
Whole thread Raw
In response to Re: [PERFORM] Cpu usage 100% on slave. s_lock problem.  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On Thu, Nov 21, 2013 at 9:09 AM, Andres Freund <andres@2ndquadrant.com> wrote:
> On 2013-11-21 09:08:05 -0600, Merlin Moncure wrote:
>> This code is in a very hot code path.  Are we *sure* that the read
>> barrier is fast enough that we don't want to provide an alternate
>> function that only returns the local flag?  I don't know enough about
>> them to say either way.
>
> A read barrier is just a compiler barrier on x86.

That's good enough for me then.

merlin



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: WITH ORDINALITY versus column definition lists
Next
From: Merlin Moncure
Date:
Subject: Re: Status of FDW pushdowns