on Mon Feb 27 2006, John Hampton <pacopablo-h1wYaUIF4+1ZroRs9YW3xA-AT-public.gmane.org> 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. I've been seeing this exact symptom using Postgres, multiple schemas in one database (http://trac.edgewall.org/wiki/TracMultipleProjects/ComprehensiveSolution in fact), and lighttpd on Trac-0.11 for about 6 months. It takes down all the sites I run about every 48 hours. I still have no idea how to fix it. :( -- Dave Abrahams BoostPro Computing http://www.boostpro.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
