Paul J Stevens wrote: > > We're using a single, global database connection pool. Since dbmail >
And how exactly database connection pool works ? How open connections are reused between threads? My guess - there's a connection pool, which allocate _int_max_db_connections_ of available connections. What I want to know is how connections are reused by different threads? Let's say pop3 daemon has for the moment 100 open pop3 sessions. When pop3 client issue a command, the daemon uses db connection, and the command is completed with some internally processed query result. Now, if in the meantime another thread (pop3 client), issue another command, the command (thread) uses first free connection, or if all possible connections are doing something, the command is delayed (actually for miliseconds) until there's a connection available to be used with command - is it this, how it works ? Regards, Piotr Wadas -- View this message in context: http://www.nabble.com/priviledge-separation%2C-threading-tp24492944p24513690.html Sent from the dbmail dev mailing list archive at Nabble.com. _______________________________________________ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
