Use nanosleep() to implement pg_usleep().
authorThomas Munro <tmunro@postgresql.org>
Wed, 15 Mar 2023 04:38:11 +0000 (17:38 +1300)
committerThomas Munro <tmunro@postgresql.org>
Wed, 15 Mar 2023 04:57:12 +0000 (17:57 +1300)
commita948e49e2ef11815be0b211723bfc5b53b7f75a8
tree00f15dbe881ef93930be988d429ce79d3ff861af
parente4da2a44c17a36904d4d083f9a96e90041d28f76
Use nanosleep() to implement pg_usleep().

The previous coding based on select() had commentary about historical
portability concerns.  Use POSIX nanosleep() instead.

This has independently been suggested a couple of times before, but
never managed to stick.  Since recent and proposed work removes other
uses of select(), and associated code and comments relating to its
non-portable interaction with signals, it seems like a good time to tidy
up this case, too.

Also modernize the explanation of why WaitLatch() is a better way to
wait.

Reviewed-by: Nathan Bossart <nathandbossart@gmail.com>
Suggested-by: Paul Guo <paulguo@gmail.com>
Suggested-by: Tom Lane <tgl@sss.pgh.pa.us>
Discussion: https://postgr.es/m/CAAKRu_b-q0hXCBUCAATh0Z4Zi6UkiC0k2DFgoD3nC-r3SkR3tg%40mail.gmail.com
Discussion: https://postgr.es/m/CABQrizfxpBLZT5mZeE0js5oCh1tqEWvcGF3vMRCv5P-RwUY5dQ@mail.gmail.com
Discussion: https://postgr.es/m/4902.1552349020@sss.pgh.pa.us
src/port/pgsleep.c