Re: Condition variable live lock - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Condition variable live lock
Date
Msg-id CAEepm=3MAW-LVDPmF+6nAUewC3_8mD3gcUPi-VrdBWnCQh7Qrw@mail.gmail.com
Whole thread Raw
In response to Re: Condition variable live lock  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Condition variable live lock
List pgsql-hackers
On Mon, Jan 8, 2018 at 12:38 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I wrote:
>> Actually ... perhaps a better design would be to have
>> ConditionVariable[PrepareTo]Sleep auto-cancel any prepared sleep for
>> a different condition variable, analogously to what we just did in
>> ConditionVariableBroadcast, on the same theory that whenever control
>> returns to the other CV wait loop it can re-establish the relevant
>> state easily enough.  I have to think that if the use of CVs grows
>> much, the existing restriction is going to become untenable anyway,
>> so why not just get rid of it?
>
> Concretely, as per attached.

+1 for the idea.  Haven't looked at the code yet but I'll review this
and the proclist patch shortly.

-- 
Thomas Munro
http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: heads up: Fix for intel hardware bug will lead to performance regressions
Next
From: Tom Lane
Date:
Subject: Re: Condition variable live lock