hey list - we've identified an issue with the connection pool released in 0.3.9 whereby threads can immediately throw a TimeoutError without waiting for the pool_timeout number of seconds to have elapsed. This can occur if many threads, greater than the number of total connections allowed, simultaneously request a connection, at a point at which the pool does have connections to return to start with, but by the end of all the thread's requests, would have reached timeout.
This issue *only* exists in 0.3.9, and not in any previous version, as its the result of a new mutex we added, which is for the purpose of ensuring that the "max_overflow" number is actually honored. in 0.3.8 and earlier, the pool would just chunk past the "max_overflow" number if many threads request a connection at once, and would then shrink back down normally when those connections were complete. Also note that this issue only affects the length of timeout when connections are no longer available. Theres no synchronization or integrity issues with the either the pool or the connections themselves which we can identify or reproduce. We will most likely be releasing 0.3.10 today with the fix, which is also available right now in the current trunk. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
