Postgres Pro
Downloads
Home   >   mailing lists

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

From Andres Freund
Subject Re: [PERFORM] Cpu usage 100% on slave. s_lock problem.
Date
Msg-id 20131121150913.GD31748@awork2.anarazel.de
Whole thread Raw
In response to Re: [PERFORM] Cpu usage 100% on slave. s_lock problem.  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: [PERFORM] Cpu usage 100% on slave. s_lock problem.  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
Tree view 
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.

Greetings,

Andres Freund

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

pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: [PERFORM] Cpu usage 100% on slave. s_lock problem.
Next
From: Tom Lane
Date:
Subject: Re: WITH ORDINALITY versus column definition lists