Heroku Postgres 2.0
postgres.heroku.com
Heroku Postgres 2.0
1–10 of 15 posts
Re: Heroku Postgres 2.0
#2I really want a better explanation of how 'rollback' works. You have to create a fork before you run your migration script so you can roll back to that fork?
Re: Heroku Postgres 2.0
#3Silently dropped the storage drastically in the lower plans. Knew the 1TB at $50 a month was too good to last forever. Now for that much storage you need to pay $2000
Re: Heroku Postgres 2.0
#4I really want a better explanation of how 'rollback' works. You have to create a fork before you run your migration script so you can roll back to that fork?
[deleted]
Re: Heroku Postgres 2.0
#5Silently dropped the storage drastically in the lower plans. Knew the 1TB at $50 a month was too good to last forever. Now for that much storage you need to pay $2000
[deleted]
Re: Heroku Postgres 2.0
#6I really want a better explanation of how 'rollback' works. You have to create a fork before you run your migration script so you can roll back to that fork?
Rollback is essentially like a fork to the past. It creates a new database, but only replays transactions up to a specific instant. It's based on the Postgres Point-in-Time Recovery feature: http://www.postgresql.org/docs/current/static/continuous-arc...
Re: Heroku Postgres 2.0
#7I really want a better explanation of how 'rollback' works. You have to create a fork before you run your migration script so you can roll back to that fork?
Rollback can be run at any point in time you do not have to create a fork ahead of time. We will be conducting some follow up posts explaining how the underlying mechanism works, for now you can read more on it at https://devcenter.heroku.com/articles/heroku-postgres-rollba...
Re: Heroku Postgres 2.0
#8Silently dropped the storage drastically in the lower plans. Knew the 1TB at $50 a month was too good to last forever. Now for that much storage you need to pay $2000
yeah these changes price adjustments are getting too be too much. And now when I enter the New Relic console I get "login failed"... When I try to look at history in Adept I get a Rails error. It feels like their priority is NEW and MORE instead of SOLID, RELIABLE. Going to try AWS for next app.
Luckily, my Heroku apps are all RDS anyway so no paranoid scrambling here...
Re: Heroku Postgres 2.0
#9Silently dropped the storage drastically in the lower plans. Knew the 1TB at $50 a month was too good to last forever. Now for that much storage you need to pay $2000
yeah these changes price adjustments are getting too be too much. And now when I enter the New Relic console I get "login failed"... When I try to look at history in Adept I get a Rails error. It feels like their priority is NEW and MORE instead of SOLID, RELIABLE. Going to try AWS for next app. Luckily, my Heroku apps are all RDS anyway so no paranoid scrambling here...
Could you raise a ticket for this stuff? Login problems with Add-ons isn't a common thing and we'd like to investigate.
Re: Heroku Postgres 2.0
#10Silently dropped the storage drastically in the lower plans. Knew the 1TB at $50 a month was too good to last forever. Now for that much storage you need to pay $2000
[deleted]