-
Notifications
You must be signed in to change notification settings - Fork 308
upgrade to Postgres 9.3 #1158
Comments
It's not released yet (though it's available on Heroku Postgres). We're currently on 9.1. |
This is released now: |
Are we comfortable upgrading to 9.3? Or do we want to wait for 9.3.1 or 9.3.2? |
9.3.1 is out as of yesterday: http://www.postgresql.org/about/news/1487/. |
@zwn Wanna take this one? |
Postgres 9.3 is still available only as public beta https://postgres.heroku.com/blog/past/2013/9/9/postgres_93_now_available/. Let's wait of official release because upgrading from beta to release would have to be done through backup and not fork/follow. |
I have marked this issue as blocked while we wait for non beta heroku postgres release. |
Agreed. Also, I guess we're really waiting for 9.4 now, per #1549 (comment)? /me edits ticket title |
I think it is worth upgrading to 9.3 since it will give us pg_stat_statements which in turn enables things like https://github.com/will/datascope. Ref. #1571 |
Fair enough. I've changed the ticket back to 9.3. |
Upgrading to 9.3 will also give us native json datatype. The hstore we are using right now supports only text key and values so this is not a problem in psycopg2 - I am responding to gittip/elsewhere/init.py#L129. |
And index only scans. |
@whit537 I wanted to do this tonight but I am not allowed to:
That would be the first step from https://devcenter.heroku.com/articles/heroku-postgres-follower-databases#database-upgrades-and-migrations-with-changeovers. |
I get an error trying to run that command:
|
According to https://devcenter.heroku.com/articles/heroku-postgresql#version-support 9.3 should be the default. Could you try adding |
|
😱 We will have to take the site down, dump the database, restore to 9.3 and bring it back online. I'll read up on how to do this. |
We would have had a brief downtime w/ the follower strategy anyway. Not the end of the world. |
Received on support@gittip.com:
|
And then ...
|
We're now on 9.1.11. We were on 9.1.9 before. |
I have everything running locally on 9.3.2 and so far nothing seems broken. |
I have loaded the heroku 9.3.2 instance with data and run local gittip against it. All working. About to do 'the real thing'. The steps I am going to take are:
I am following https://devcenter.heroku.com/articles/upgrade-heroku-postgres-with-pgbackups and it should not take more then a couple of minutes. |
The backup id for the switchover is |
We are now on 9.3.2 |
@whit537 I think the original 9.1 database can now be removed so that it does not incur further charges. |
\0/ |
I've found one more article nicely covering all aspects of heroku backups: https://devcenter.heroku.com/articles/heroku-postgres-data-safety-and-continuous-protection |
Done. !m @zwn |
Suggested by @jacobian on Twitter: Gets us materialized views, which came up in code review for #1155.
The text was updated successfully, but these errors were encountered: