[sqlalchemy] Re: Too many database connections. - Ben Bangert - com.googlegroups.sqlalchemy

8 messages in com.googlegroups.sqlalchemy[sqlalchemy] Re: Too many database co...

From	Sent On	Attachments
caffecoder	28 Aug 2007 23:26
Mike Orr	29 Aug 2007 08:16
caffecoder	31 Aug 2007 05:36
Ben Bangert	31 Aug 2007 08:57
Ben Bangert	31 Aug 2007 10:34
Michael Bayer	31 Aug 2007 13:32
Michael Bayer	31 Aug 2007 13:50
Ben Bangert	31 Aug 2007 13:57

Subject:	[sqlalchemy] Re: Too many database connections.
From:	Ben Bangert (gasp...@gmail.com)
Date:	08/31/2007 10:34:50 AM
List:	com.googlegroups.sqlalchemy

On Aug 31, 8:58 am, Ben Bangert <gasp...@gmail.com> 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