Saturday, August 6, 2011

PGError: ERROR: cached plan must not change result type... Solved

I got this error recently after deploying to Heroku:

ActiveRecord::StatementInvalid (PGError: ERROR:  cached plan must not change result type

It turns out the issue was just like that of this person: http://stackoverflow.com/questions/2783813/postgres-8-3-error-cached-plan-must-not-change-result-type.

Basically, I ran a migration / modified my database table, but didn't restart the heroku app. So, after running

heroku run rake db:migrate

I had to also run

heroku restart

and the problem was solved.

Why do we have to do this? According to this site on Heroku, "After running a migration you’ll want to restart your app with heroku restart to reload the schema and pickup any schema changes."
Labels:

8 comments:

  1. Brian KellyJanuary 5, 2012 at 6:09 PM

    Thanks! I just ran into this problem and this solved it for me.

    ReplyDelete
  2. UnknownJanuary 17, 2012 at 11:04 AM

    thanks. worked for me.

    ReplyDelete
  3. AnonymousJune 13, 2012 at 12:48 PM

    this saved me! thanks!

    ReplyDelete
  4. The ConnectionSeptember 20, 2012 at 4:29 PM

    yep, your link was the top search result (query = this error's text) and fixed my problem, thanks for posting

    ReplyDelete
  5. UnknownDecember 14, 2013 at 6:49 PM

    thanks just saved me from a heart attack!

    ReplyDelete
  6. UnknownFebruary 24, 2015 at 2:11 PM

    Thanks Man! :-) You saved my bacons!

    ReplyDelete
  7. AnonymousMay 21, 2015 at 6:44 PM

    thanks dude worked

    ReplyDelete
  8. AnonymousJuly 17, 2015 at 4:18 PM

    you have no idea how happy this just made me. thank you!

    ReplyDelete

Please be considerate in what you say.

Subscribe to: Post Comments (Atom)