Does Sequel creates connections and populated the pool on start or does it do on demand?
On Sun, Dec 24, 2017 at 10:18 AM, Jeremy Evans <[email protected]> wrote: > On Saturday, December 23, 2017 at 6:07:42 PM UTC-8, shashank Jain wrote: >> >> Reading the release notes of 5.0 which says >> >> += Other Improvements >> + >> +* Threaded connection pools no longer block while new connections >> + are being made. Previously, attempting to establish a new >> + connection blocked all connection pool activity until the new >> + connection was made. >> >> Does this mean the acquire connection method will not block the other >> threads? >> > > It means the ConnectionPool#make_new/Database#connect call will be made > without holding the connection pool mutex. So if establishing a new > connection takes 10 seconds, the connection pool will not be locked during > that time. > > Thanks, > Jeremy > > -- > You received this message because you are subscribed to a topic in the > Google Groups "sequel-talk" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/sequel-talk/5NNUNaHqIMY/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/sequel-talk. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
