postgres connection limit exceeded

[Ernest Ellingson <erne (at) powernav.com>]

John Hampton wrote:
> Mark Rowe wrote:
> > The way mod_python is designed the database connections aren't able 
> > to be shared between different Apache processes, and I think that 
> > with separate databases per environment a new database connection is 
> > required.
>
> That's what I thought
>
> > I'm unsure how the general problem could be better solved for 
> > mod_python, as the issue seems to be primarily due to the forking 
> > nature of Apache.
>
> Well, my schema patch alleviates it by changing the scenario.  Instead 
> of having X database connections times Apache processes, you just have 
> one database connection[1] as all the trac instances reside in the 
> same db, just different schemas.
>
> -John
>
> [1] per apache process that is.
> _______________________________________________
> Trac mailing list
> Trac (at) lists.edgewall.com
> http://lists.edgewall.com/mailman/listinfo/trac
The problem exists in tracd also.  I have one project running in tracd.  
I login with a browser.  I close the browser I log in with another 
instance of the browser another connection.  The number of connections 
in pg_stat_activity keeps growing until I kill tracd.  Once it's gone.  
The number of records in pg_stat_activity returns to previous levels 
(before tracd).  I have repeated this many times to double check.

It does no appear to be a mod_python and apache problem.

Ernie

--

"Keep an open mind, but not so open that your brain falls out." (Richard 
Feynman)
_______________________________________________
Trac mailing list
Trac (at) lists.edgewall.com
http://lists.edgewall.com/mailman/listinfo/trac