[OGo-Users] postgres connection limit exceeded

[Sebastian Reitenbach]

users@opengroupware.org wrote: 
> > as the company grows, more and  more people are using ogo. From time to 
time 
> > it happens that people that try to login, get an error message, ogo 
cannot 
> > reach its database. Users with an already active session, can still 
work. I 
> > figured out, that the postgres database had its connection limit 
exceeded. 
> > Raising the connection limit fixes the problem for a while, but I don't 
> > think that this is the best idea, if good at all.
> 
> What did you raise it too?  The defaults in PostgreSQL are so low it is
> silly,  so unless you raised them ALLOT I wouldn't be concerned.
right now, I doubled the default value from 100 to 200. Not sure to what 
values I can raise it until I run into trouble.

> 
> > Well, after googling for a solution to the problem, the recommended 
answer 
> > is either fix the application, or use a connection pooling daemon like 
> > pgbouncer. 
> 
> Depends on how many connections we are talking about?
above mentioned connections, 100 was not enough, there the problems 
happened. Well, as long as I can raise the connection limit without noticing 
problems I'm fine, and do not need pgbouncer.  
> 
> > Is there an ogo default, allowing me to kill idle database sessions?
> 
> The old XML-RPC daemon can leak connections.  I haven't see that with
> ZideStore or OGo.
> 
> http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=1884
ah, interesting.

thanks
Sebastian