Hi all, Sorry to bump this, but I didn't find another thread, and I'm pretty sure re-trying the database connection is the sane thing to do.
Otherwise, Django will remain in failed state after reboot in some cases: psycopg2.OperationalError: FATAL: the database system is starting up It would be better if Django could tolerate this situation and retry, then the server would be reboot proof. At least, show a 500 page until the DB server has started, would be more reasonnable. Are you sure Django should not be a bit a bit more tolerant with databases starting up ? Or should we open a ticket ? Thanks in advance for your reply Have a great weekend -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC6Op18ET_ZZs_XBQou70sJL9vo2fsk2BL57q4j-U-j5H_d4oQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
