On 10/24/2016 01:28 PM, Gordon Messmer wrote:
I honestly can't think of any good reason to spawn multiple children that compete for a lock to do work, when the process that's starting them*should* have adequate information about which clients are active and which are idle, and can use that information to select a client on which to start the process.
A database running on a server probably doesn't want more than one process to be modifying it at any given time.
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
