Re: Too much clients connected to the PostgreSQL Database
От | rodrigo@paripassu.com.br |
---|---|
Тема | Re: Too much clients connected to the PostgreSQL Database |
Дата | |
Msg-id | 62351.189.101.235.92.1351559164.squirrel@webmail.paripassu.com.br обсуждение исходный текст |
Ответ на | Re: Too much clients connected to the PostgreSQL Database ("Kevin Grittner" <kgrittn@mail.com>) |
Ответы |
Re: Too much clients connected to the PostgreSQL Database
|
Список | pgsql-general |
150 maxActive setting, but we have some low usage application getting direct db connection(out of the pool). The interesting is that the server suddently get a lot of connections and reach the limit and then release them. I'm willing to change to Tomcat 7 connection pool. We are using c3pO and apache ones, maybe that's a problem. Thank you, Well, > Rodrigo Pereira da Silva wrote: > >> We have about 10 web applications deployed in a Tomcat 7.0 >> accessing a Postgresql 9.1 database. We do use connection pooling. >> We have the max_connections parameter set to 200 connections, >> however, we are reaching the max connections sporadically(about 4 >> time/day). > > What is the pooler's maxActive setting? (It should be less than the > PostgreSQL max_connections setting.) > > BTW, 200 seems alwfully high unless a *really* high end machine. Â You > may have fewer timeouts if you avoid swamping the server with a > "thundering herd" of requests. > > http://wiki.postgresql.org/wiki/Number_Of_Database_Connections > > -Kevin > > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general >
В списке pgsql-general по дате отправления: