On Mon, Aug 18, 2014 at 10:46 AM, Zeb Haradon <zebhara...@gmail.com> wrote:
> Sorry, I misspoke. I meant that once the problem occurs you have to actually > reinstall postgres to get it to work again. If the problem affects every db on the server, I can't imagine how it could be anything *but* a postgres bug. But since postgres apparently doesn't have any bug tracking system, who knows? :-) If it were me, I'd jack the postgres logging level to max/debug/whatever provides the most data and cross fingers... Good luck, -- Hassan Schroeder ------------------------ hassan.schroe...@gmail.com http://about.me/hassanschroeder twitter: @hassan -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CACmC4yA4wX81PTobHaMsZFrd9HgRtAnK_GsCT%3DWVb_G0nY%2Bscw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
