On Wed, Aug 13, 2014 at 2:32 PM, Zeb Haradon <[email protected]> wrote: > Summary: rails app using postgres randomly gets into a state where hstore > array is returned as a string, and cannot be fixed without rebuilding the > database
Not that familiar with (or fond of) postgres, but curious -- > You can see that in the broken instance, it is returning the hstore data as > a string. Some pertinent info is that once it gets in this broken state, you > can drop and restore the database, or rename the database, and as long as > it's on the same postgres sever, it's still broken - you have to rebuild the > whole database for it to work. What is the difference exactly between "drop and restore" and "rebuild"? > And if you point the app (change > database.yml) to point to a different server, it works. What's in the postgres logs when this fails? Is there anything in the Rails logs at startup that differs between working/not working? Have you put any additional logging into the connection adapter? -- Hassan Schroeder ------------------------ [email protected] 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CACmC4yBSZSr%2BpZZ-e3oaAuqhL5w1ubJxJizmRrutn5fWNvm_rw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
