[OGo-Users] postgres connection limit exceeded

[Sebastian Reitenbach]

users@opengroupware.org wrote: 
> 
> Hello,
> 
> On Fri, 29 Feb 2008 14:39:12 +0100 Sebastian Reitenbach wrote:
> 
> > 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's wrong with the connection limit?
The limit was just exceeded, and then new connections were unable to use 
ogo, existing sessions did not had a problem. Meanwhile I raised it to 800 
or such, that should be sufficient for a while ;)

cheers
Sebastian

> 
> 
> > 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. 
> 
> PGbouncer have some implications which the application has to be aware
> of.
> 
> The only mode without limitations is "session pooling" - but
> this will be the same behavior like the current situation.
> 
> 
> > Is there an ogo default, allowing me to kill idle database sessions?
> > Or anybody uses such a postgresql connection pooling daemon in 
conjunction 
> > with OGo?
> 
> The database session is idle because one OGo process is still connected.
> One solution could be sOGo, but i think, Helge can tell you more.
> 
> 
> Bye
> 
> -- 
> 				Andreas 'ads' Scherbaum
> German PostgreSQL User Group
> European PostgreSQL User Group - Board of Directors
> -- 
> OpenGroupware.org Users
> users@opengroupware.org
> http://mail.opengroupware.org/mailman/listinfo/users
>