pool.end() does not render the pool unusable afterward.
2 things actually.
await pool.end() doesn't properly wait for the pool to end AFAIK, so that should be fixed.- I don't see a reason calling
await pool.end() couldn't leave the pool in a usable state going forward. This would mostly be backwards compatible, but would make it easy in serverless environments to end the pool when the worker shuts down but still be able to keep a global pool reference which is a common pattern.
Originally posted by @brianc in #3598 (comment)
pool.end() does not render the pool unusable afterward.
2 things actually.
await pool.end()doesn't properly wait for the pool to end AFAIK, so that should be fixed.await pool.end()couldn't leave the pool in a usable state going forward. This would mostly be backwards compatible, but would make it easy in serverless environments to end the pool when the worker shuts down but still be able to keep a global pool reference which is a common pattern.Originally posted by @brianc in #3598 (comment)