On 10/24/2016 02:07 PM, Joe Zeff wrote:
A database running on a server probably doesn't want more than one process to be modifying it at any given time.
Yes, I get that. But why would it be better for the scheduler to start up database servers on multiple hosts and allow them to compete for a lock, rather than pick one host to start the database and start one instance? The former is what JD is suggesting (adapted to your proposal; as far as I can tell), while I suggest that the latter is probably a better approach if it's possible, and it usually is.
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
