[OGo-Users] postgres connection limit exceeded

[Adam Tauno Williams]

On Fri, 2008-03-07 at 00:33 +0100, Helge Hess wrote:
> On 02.03.2008, at 00:49, Helge Hess wrote:
> > Having more instances doesn't raise the number of sessions (hence  
> > open channels), they are load balanced, thats the idea after all.  
> > Each of the servers will have less channels open.
> BTW: I checked. OGo does *not* keep the connections open, so its not 1  
> connection per session. There is a timeout which closes connections  
> after some time.

Potentially stupid question:  why does OGo need to open a connection per
session in the first place?  Why can't/doesn't each session just use
(and share) a common connection?   My understanding is that OGo (SOPE?)
serializes requests, only doing one-at-a-time.

> The actual timeout can be configured using the LSSessionChannelTimeOut  
> default, which is in seconds (defaults to 300s aka 5min).

Understood, and will be in the next edition of WMOGAG.