On Aug 29, 8:16 am, "Mike Orr" <[EMAIL PROTECTED]> wrote: > I've been getting a similar but not identical error after upgrading to > SQLAlchemy 0.4, and somebody else on the list also mentioned this > recently. I don't have the traceback but it was the error for > exceeding the 'max_overflow' number of connections. > > I worked around it by setting the 'max_overflow' engine option from 10 > to 30. I haven't tried the 'threadlocal' pooling strategy, which is > supposed to minimize the number of connections per thread.
I've started getting this same overflow error after upgrading to the latest beta4, I don't recall having the problem with beta3 but during beta3 I used Session.mapper and now I'm using plain mapper. Not sure if that affects it at all though. I'd love to know why all of a sudden, there's connection pooling issues though, when it was fine before. I'm tweaking overflow, and recycle options, but I never needed to do this before when using Postgres. - Ben --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
