Connection limit exceeded, after updating to 0.9.4

[Taha Jahangir]

After move to sqlalchemy 0.9.4 in production environment, we encountered error FATAL: remaining connection slots are reserved for non-replication superuser connections.

Is there any change in session code, or connection pool manager in sqlalchemy 0.9? This issue occurred on production server, so it's hard (and costly) to do some debugging tasks. We temporarily fixed the issue by reverting to sqlalchemy 0.8.6.

(Environment is: python 3.3 with mod_wsgi/apache with postgreql 9.0, all on FreeBSD 9.0 servers)

[Mike Bayer]

or connection pool manager in sqlalchemy 0.9?

many things in the pool, all of which are documented at http://docs.sqlalchemy.org/en/latest/changelog/changelog_09.html.

when upgrading from 0.8 to 0.9 you should be doing some rudimentary performance testing of your server in a staging/test environment.

I'm not denying that there might be a possibly critical issue here but I can't take any action on this issue as raised. it has no supporting information or anything to go on. if you can't continue testing I'll have to close this and wait for someone else to report it. Please let me know ASAP.

[Mike Bayer]

OK, can't do anything here without more info, feel free to reopen