On Thursday 04 May 2006 12:26, Richie Hindle wrote: > [Greg] > > > I think you're right, Richie. I applied the patch just in case I used > > threads at some point, like maybe if I used Django's database layer in > > some context other than a web server. > > OK, thanks. That's a relief! I thought I'd misunderstood the prefork MPM > completely...
Hey Richie, We just had to apply the patch found here: <http://code.djangoproject.com/ticket/1445> Apparently the problem is fixed in the trunk-previously-known-as-magic-removal. The problem arose with us when I svn switch'ed to the 'Sargasso' branch, aka 'pre-magic-removal', which was essentially an svn update to version 2808. I haven't checked, but I suspect the ticket 1445 problem was introduced when I made that switch. PostgreSQL's max_connections were reached and then the app started throwing errors. The site had been running fine for over a month up to this point. I applied the patch and restarted apache. So far, after about an hour of moderate use, there are no more leaked connections. I hope that helps. Eric. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
