[OGo-Users] postgres connection limit exceeded

[Andreas 'ads' Scherbaum]

On Fri, 07 Mar 2008 17:03:11 +0100 Sebastian Reitenbach wrote:

> users@opengroupware.org wrote: 
  ^^^^^^^^^^^^^^^^^^^^^^^

Could you please fix your email program?
That's not the person who wrote the mail you are answering.


> > On 07.03.2008, at 13:06, Sebastian Reitenbach wrote:
> > > Meanwhile I raised it to 800
> > > or such, that should be sufficient for a while ;)
> > 
> > 
> > I think it might make more sense to try to lower  
> > LSSessionChannelTimeOut, eg -LSSessionChannelTimeOut 20.
> when I run into that trouble again, then I'll try that.

You will run into other kind of trouble like memory problems or
performance impacts. Maybe you cannot even pin down the problems in the
same way like you can right now with the error message telling you that
you reached a configured limit.

We discussed that topic a bit on IRC yesterday and just raising the
connection limit is not solving your problems at all. As example,
with 1000 or 2000 running but idle processes your OS hat to schedule
all this processes. Each PG backend needs some memory for the data
structures and for managing state. Ok, your OS can save you a lot
trouble with copy-on-write and/or overcommitting. But this wall will
break in the moment your system is low on mem anyway.

In addition, behind every open database connection is another process
(normally one OGo process) who is also consuming resources.


Kind regards

-- 
				Andreas 'ads' Scherbaum
German PostgreSQL User Group
European PostgreSQL User Group - Board of Directors