| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Ants Aasma <ants(at)cybertec(dot)at>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Дмитрий Дегтярёв <degtyaryov(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PERFORM] Cpu usage 100% on slave. s_lock problem. |
| Date: | 2013-11-21 15:13:29 |
| Message-ID: | CAHyXU0xRyx8mpTX9S8zbMTuYp54CBzrAQjhwxVyKZqh3_mA7ww@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 21, 2013 at 9:09 AM, Andres Freund <andres(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2013-11-21 15:17:47 | Re: Status of FDW pushdowns |
| Previous Message | Tom Lane | 2013-11-21 15:11:06 | Re: WITH ORDINALITY versus column definition lists |