Hi, On Fri, Aug 09, 2024 at 02:03:55PM -0500, Nathan Bossart wrote: > On Thu, Aug 08, 2024 at 03:01:20PM -0500, Nathan Bossart wrote: > > Thanks. This one looks pretty good to me, and so I plan to commit it in > > the near future unless anyone voices concerns about the approach. > > As I am preparing this for commit, I'm wondering whether it makes sense to > name the new function vacuum_sleep() and keep it private to vacuum.c. > Nothing about this function is terribly specific to vacuum, and it's not > inconceivable that it might be useful elsewhere. Perhaps we should move it > to pgsleep.c and rename it to something to the effect of > pg_usleep_non_interruptable().
Yeah, I had the same thought in [1], so +1. [1]: https://www.postgresql.org/message-id/ZpDhS4nFX66ItAze%40ip-10-97-1-34.eu-west-3.compute.internal Regards, -- Bertrand Drouvot PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com
