Re: Removing select(2) based latch (was Unportable implementation of background worker start)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Removing select(2) based latch (was Unportable implementation of background worker start)
Date: 2017-04-20 21:50:39
Message-ID: 21379.1492725039@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2017-04-20 17:27:42 -0400, Tom Lane wrote:
>> In short: yeah, let's nuke the WAIT_USE_SELECT implementation.
>> It's dead code and it's unlikely to get resurrected.

> Ok, cool. v10 or wait till v11? I see very little reason to wait
> personally.

I feel no need to wait on that. Code removal is not a "new feature".

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-04-20 22:09:08 Re: Removing select(2) based latch (was Unportable implementation of background worker start)
Previous Message Tom Lane 2017-04-20 21:47:00 Re: Use sync commit for logical replication apply in TAP tests