Some follow-up to my own post in case someone else has the same issue. I looked into putting the schema scans into the to_prepare callback but it looks like that is run at start-up (for production). Also on further reflection moving the schema scans out of the startup (or altogether) only reduces the issue a bit. The fundamental issue of database timeouts still causes errors during the request cycle. If this continues I will just have to conclude Heroku is not a reliable hosting environment if you are not able to justify the $200+/month for a dedicated database (using Amazon RDS might be a little cheaper but still expensive for an app that doesn't need a dedicated database).
I am *hoping* this is just a temp issue with Heroku that will get resolved soon. So in the meantime I created a restart app for my client so they can restart the application themselves if it gets a database hangup. It feels like I am back developing on Windows with having a restart script but it will have to do for now. In case someone else might need something similar here is the code for the restart app: http://gist.github.com/371030 Hopefully reliability won't force me to move from Heroku as I really love the workflow they provide. -- You received this message because you are subscribed to the Google Groups "Heroku" 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/heroku?hl=en.
