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

From Thomas Munro
Subject Re: Condition variable live lock
Date
Msg-id CAEepm=2xt_M0PquwBKC6SPm0gpmCUajGsiQ7PLTBAbSuo4O34g@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 Fri, Jan 5, 2018 at 7:42 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Indeed, it looks like no other caller is paying attention to the result.
> We could live with the uncertainty in the back branches, and redefine
> ConditionVariableSignal as returning void in master.

+1

Could we install the sentinel and pop the first entry at the same
time, so that we're not adding an extra spinlock acquire/release?

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


pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: [HACKERS] [PATCH] Incremental sort
Next
From: "Tels"
Date:
Subject: Re: [Patch] Make block and file size for WAL and relations definedat cluster creation