Re: Removing select(2) based latch (was Unportable implementation of background worker start)
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>,
Alvaro Herrera <alvherre@2ndquadrant.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-04-23T15:50:55Z
Lists: pgsql-hackers
On Thu, Apr 20, 2017 at 5:50 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Andres Freund <andres@anarazel.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". One can imagine a situation in which code removal seemed to carry a risk of destabilizing something, but the change under discussion here seems more likely to improve stability rather than to regress anything. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Don't include sys/poll.h anymore.
- b182a4ae2f9a 10.0 landed
-
Remove select(2) backed latch implementation.
- 61c21ddad03d 10.0 landed