This has come up on the list once before, and I answered the same way on your other new thread, but I think the best answer was to use the TurboGears scheduler to hit the DB regularly.
http://docs.turbogears.org/1.0/Scheduler --Mark On 2/3/07, iain duncan <[EMAIL PROTECTED]> wrote: > > On Sun, 2007-04-02 at 09:28 +1100, Glenn Davy wrote: > > On Sat, 2007-02-03 at 13:33 -0800, iain duncan wrote: > > > Can anyone tell me whether the mysql going to sleep issue also happens > > > with postgresql? Or if there are any similar issues for pg? > > > > > to be fair, i dont know what 'the sleep' issue is, but ive mainly used > > postgres over years for a variety of projects (all non TG :-( ) - never > > had any issues of it becoming non-responsive in anyway(or of any other > > sort of issue either really) > > The sleep issue is that when tg runs with cherrypy, it's in a > long-running process that keeps a mysql connection alive. But if mysql > doesn't receive a hit on that connection in a long time, it goes to > sleep and then the first hit fails. Which is Really Annoying. So the > workaround is to have something make a hit every hour. Which is Really > Ugly. ; ) > > Apparently this was brought to the attention of the mysql folks but I > don't know the status on that these days ... > > Iain > > > > > -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
