Thanks for the quick reply.

On Thursday, July 25, 2013 3:39:17 PM UTC-7, Klauss wrote:
>
> As the message says, you have too many open connections. 
>
> When you have multiple machines, you must either provision your 
> postgres to be able to handle a full connection pool (max_overflow 
> preferrably, pool_size at least) for each nginx worker for each 
> machine, or have SQLA connect to a pgbouncer that will do the shared 
> pooling for you. 
>


I should have mentioned that all the connections are idle.. 

My postgres.conf has a parameter  max_connections = 100

I was led to believe the SA would manage pool of connections 
to some good default 
(http://docs.sqlalchemy.org/en/rel_0_7/core/pooling.html?highlight=connection%20pool),
but couldn't find the default values?  Just so I can relate the two figures 
(SA Pool parameters and PG max_connections)

Also Is there a good way to get it too close some idle connections?


Thx,
Kris

 

-- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to