Re: [PERFORM] Cpu usage 100% on slave. s_lock problem.

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: Andres Freund <andres(at)2ndquadrant(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-22 11:11:22
Message-ID: 528F3BDA.1090905@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 21.11.2013 21:37, Merlin Moncure wrote:
> On Thu, Nov 21, 2013 at 10:37 AM, Heikki Linnakangas
>> In my patch, I put the barrier inside the if (!LocalRecoveryInProgress)
>> block. That codepath can only execute once in a backend, so performance is
>> not an issue there. Does that look sane to you?
>
> oh right -- certainly!

Ok, commmited.

- Heikki

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Kreen 2013-11-22 11:27:40 Re: PL/Python: domain over array support
Previous Message Rodolfo Campero 2013-11-22 10:45:56 Re: PL/Python: domain over array support