postgres connection limit exceeded

[John Hampton <pacopablo (at) asylumware.com>]

Stephen A. Cochran Lists wrote:
> On Feb 16, 2006, at 3:40 PM, 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.
>
> This wouldn't explain why I still saw four database connections after 
> turning on KeepAlive, restarting Apache, and visiting one trac project.
>
> I haven't run into problems since I've cronned apache to restart every 
> day, but someday we'll exceed the limit in one day.
>
> What seems to still be unknown is at what point does apache ever close 
> those connections to postgres.
>
> I have all my DBs set up with separate users and passwords, I wonder if 
> all the different DBs had the same user/pass if one connection could 
> serve multiple databases.

Do you happen to have a canned way to replicate the connection issues? 
I've tried to duplicate them with ab (from apache) but can't get my 
number of connections to go beyond about 25.

I am using trunk and the pgschema patch.  I'd love to be able to 
duplicate the issue to see if I can track it down (not that I'll have 
more success, but here's to hoping).

-John
_______________________________________________
Trac mailing list
Trac (at) lists.edgewall.com
http://lists.edgewall.com/mailman/listinfo/trac