On Aug 31, 8:58 am, Ben Bangert <[EMAIL PROTECTED]> wrote: > 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 just downgraded to beta3, and the bug is gone. I noticed with beta4, there seemed to be a discrepency between how many connections the pool *thinks* it has, and how many it really has open. I never saw more than 6 postgres connections open, but it started erroring out saying its overflow and connection limit was hit. Beta3 seems to be fine, and actually has 10-14 connections open, and recycles them properly (all using the defaults). Mike: I'd suggest downgrading to beta3 to remedy the problem, as I still had connection problems on beta4 after awhile no matter what I set the top limits to, plus it wasn't really even holding those connections open. Cheers, 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 -~----------~----~----~----~------~----~------~--~---
