Re: race condition in sync rep

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: robertmhaas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, tgl <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: race condition in sync rep
Date: 2011-03-27 17:36:20
Message-ID: AANLkTi=eWpdaAyHaLfME8igPi7uFHGtom-L8egsUNU5e@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Mar 27, 2011 at 6:07 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Simon Riggs  wrote:
>
>> I'm surprised that a network roundtrip takes less time than the
>> backend takes to mark clog and then queue for the SyncRepLock.
>
> I'm not surprised by that at all.  Some of our replication involves
> Gb or faster connections on the same LAN segment (sometimes on the
> same switch).
>
> That's rather beside the point though -- on a busy system a process
> can get starved long enough to make some seemingly improbably timings
> occur.  PostgreSQL shouldn't fall over just because the load gets
> heavy enough to cause such timings.  A race condition is a race
> condition.

That has been fixed, without discussion. The discussion was about ...,
well, something else.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomáš Pospíšil 2011-03-27 19:01:37 Re: [HACKERS] Needs Suggestion
Previous Message Pavel Stehule 2011-03-27 17:30:43 Re: WIP: Allow SQL-language functions to reference parameters by parameter name