Eugene Lazutkin wrote: > kmh wrote: > > Edgars Jekabsons wrote: > >> OK, posted a patch agaist trunk (revision 2307) > >> http://code.djangoproject.com/attachment/ticket/463/mysql_rev2307.diff > >> > >> -- > >> Edgars > > > > Hey thanks Edgars, > > > > I'll run it for a while and post encouragement to the ticket if I have > > no problems. > > > > Kieran > > Let me know how it goes. If there is a problem, I'll make my patch. I > use it for a long time now without problems. > > Thanks, > > Eugene
So I tried running this patch on a very low-volume production server and MySQL (4.1/ Ubuntu Breezy) started chucking some "Too many connections" errors. I'm no expert on RDBMS. I did some googling and discovered the MySQL "max_connections" setting. Mine is at the default of 100. I would have thought that would be well-adequate in this particular case, though the user-agent in the error message was a Yahoo-bot so it is possible that there were many simultaneous requests at the time (my access log was off so I can't say exactly - I'll turned it on if I try again). I don't know how to tell if this is a problem with the patch not cleaning up after itself or my database setup being piss-poor. Any tips? Various niggling problems with the MySQL/Django combination (together with the knowledge that it doesn't get quite the same loving from the core devs) are tempting me to switch to Postgresql, but the migration process seems like a recipe for pain and suffering. Anyone been through it? I have foggy notions about something involving Jacob and an idea for a data migration tool...am I making this up? Cheers, Kieran --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
