2013/8/8 <[email protected]> > The exception is excited after connection with a database was lost and > again regenerated(I start the application, execute a command postgresql > restart, refresh the page of application and receive this exception)
Have you turned on persistent connections? If so, you're seeing the expected behavior. With persistent connections, if memory serves, the first user hitting a page after a database restart will encounter an error. There are rather fundamental reasons why this is hard to fix. (Hard doesn't mean impossible.) -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
