Heroku postgres: How to fork pg database with rollback to recover lost data
up vote
1
down vote
favorite
I deleted 3 rows accidentally from our production database (Heroku postgres). I followed this guide from Heroku on creating a rolled-back fork: https://devcenter.heroku.com/articles/heroku-postgres-rollback
My production DB is called HEROKU_POSTGRESQL_IVORY and is on plan Standard-0.
I have tried multiple combinations of the command that they suggest:
$ heroku addons:create heroku-postgresql:standard-0 --rollback
HEROKU_POSTGRESQL_IVORY --TO '2018-11-22 13:13+00' --APP my_app
$ heroku addons:create heroku-postgresql:standard-0 --rollback
HEROKU_POSTGRESQL_IVORY --TO '2018-11-22 13:13+00:00' --APP my_app
$ heroku addons:create heroku-postgresql:standard-0 --rollback
HEROKU_POSTGRESQL_IVORY --BY '0 days 1 hours 0 minutes' --APP my_app
All three of which have created a DB that wasn't rolled back. When I run heroku pg:info -a my_app
, I can see the newly created DB, but the rollback version it gives is never from the desired time, and the rows that I deleted are not present:
Plan: Standard 0
Status: Available
Data Size: 52.4 MB
Tables: 34
PG Version: 10.6
Connections: 8/120
Connection Pooling: Available
Credentials: 2
Fork/Follow: Available
Rollback: earliest from 2018-11-22 14:17 UTC
Created: 2018-11-22 14:10 UTC
Region: eu
Data Encryption: In Use
Continuous Protection: On
Forked From: HEROKU_POSTGRESQL_IVORY
Maintenance: not required
Maintenance window: Wednesdays 21:00 to Thursdays 01:00 UTC
Add-on: postgresql-deep-1111
heroku heroku-postgres heroku-cli
add a comment |
up vote
1
down vote
favorite
I deleted 3 rows accidentally from our production database (Heroku postgres). I followed this guide from Heroku on creating a rolled-back fork: https://devcenter.heroku.com/articles/heroku-postgres-rollback
My production DB is called HEROKU_POSTGRESQL_IVORY and is on plan Standard-0.
I have tried multiple combinations of the command that they suggest:
$ heroku addons:create heroku-postgresql:standard-0 --rollback
HEROKU_POSTGRESQL_IVORY --TO '2018-11-22 13:13+00' --APP my_app
$ heroku addons:create heroku-postgresql:standard-0 --rollback
HEROKU_POSTGRESQL_IVORY --TO '2018-11-22 13:13+00:00' --APP my_app
$ heroku addons:create heroku-postgresql:standard-0 --rollback
HEROKU_POSTGRESQL_IVORY --BY '0 days 1 hours 0 minutes' --APP my_app
All three of which have created a DB that wasn't rolled back. When I run heroku pg:info -a my_app
, I can see the newly created DB, but the rollback version it gives is never from the desired time, and the rows that I deleted are not present:
Plan: Standard 0
Status: Available
Data Size: 52.4 MB
Tables: 34
PG Version: 10.6
Connections: 8/120
Connection Pooling: Available
Credentials: 2
Fork/Follow: Available
Rollback: earliest from 2018-11-22 14:17 UTC
Created: 2018-11-22 14:10 UTC
Region: eu
Data Encryption: In Use
Continuous Protection: On
Forked From: HEROKU_POSTGRESQL_IVORY
Maintenance: not required
Maintenance window: Wednesdays 21:00 to Thursdays 01:00 UTC
Add-on: postgresql-deep-1111
heroku heroku-postgres heroku-cli
Can you add the full output frompg:info
? Or at least the information forIVORY
? Also, did you upgradeIVORY
trying to get access to the rollback feature? Or was it always a standard-0?
– RangerRanger
Nov 22 at 15:48
@RangerRanger thanks for help, I'll be sure to post a more full question in the future. I actually just figured it out. It was using--TO
as opposed to--to
! I'm sure I didn't write the whole thing out myself, I copied it from somewhere, but that's my bad.
– JMurphyWeb
Nov 22 at 16:17
Glad to hear it!
– RangerRanger
Nov 22 at 16:19
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I deleted 3 rows accidentally from our production database (Heroku postgres). I followed this guide from Heroku on creating a rolled-back fork: https://devcenter.heroku.com/articles/heroku-postgres-rollback
My production DB is called HEROKU_POSTGRESQL_IVORY and is on plan Standard-0.
I have tried multiple combinations of the command that they suggest:
$ heroku addons:create heroku-postgresql:standard-0 --rollback
HEROKU_POSTGRESQL_IVORY --TO '2018-11-22 13:13+00' --APP my_app
$ heroku addons:create heroku-postgresql:standard-0 --rollback
HEROKU_POSTGRESQL_IVORY --TO '2018-11-22 13:13+00:00' --APP my_app
$ heroku addons:create heroku-postgresql:standard-0 --rollback
HEROKU_POSTGRESQL_IVORY --BY '0 days 1 hours 0 minutes' --APP my_app
All three of which have created a DB that wasn't rolled back. When I run heroku pg:info -a my_app
, I can see the newly created DB, but the rollback version it gives is never from the desired time, and the rows that I deleted are not present:
Plan: Standard 0
Status: Available
Data Size: 52.4 MB
Tables: 34
PG Version: 10.6
Connections: 8/120
Connection Pooling: Available
Credentials: 2
Fork/Follow: Available
Rollback: earliest from 2018-11-22 14:17 UTC
Created: 2018-11-22 14:10 UTC
Region: eu
Data Encryption: In Use
Continuous Protection: On
Forked From: HEROKU_POSTGRESQL_IVORY
Maintenance: not required
Maintenance window: Wednesdays 21:00 to Thursdays 01:00 UTC
Add-on: postgresql-deep-1111
heroku heroku-postgres heroku-cli
I deleted 3 rows accidentally from our production database (Heroku postgres). I followed this guide from Heroku on creating a rolled-back fork: https://devcenter.heroku.com/articles/heroku-postgres-rollback
My production DB is called HEROKU_POSTGRESQL_IVORY and is on plan Standard-0.
I have tried multiple combinations of the command that they suggest:
$ heroku addons:create heroku-postgresql:standard-0 --rollback
HEROKU_POSTGRESQL_IVORY --TO '2018-11-22 13:13+00' --APP my_app
$ heroku addons:create heroku-postgresql:standard-0 --rollback
HEROKU_POSTGRESQL_IVORY --TO '2018-11-22 13:13+00:00' --APP my_app
$ heroku addons:create heroku-postgresql:standard-0 --rollback
HEROKU_POSTGRESQL_IVORY --BY '0 days 1 hours 0 minutes' --APP my_app
All three of which have created a DB that wasn't rolled back. When I run heroku pg:info -a my_app
, I can see the newly created DB, but the rollback version it gives is never from the desired time, and the rows that I deleted are not present:
Plan: Standard 0
Status: Available
Data Size: 52.4 MB
Tables: 34
PG Version: 10.6
Connections: 8/120
Connection Pooling: Available
Credentials: 2
Fork/Follow: Available
Rollback: earliest from 2018-11-22 14:17 UTC
Created: 2018-11-22 14:10 UTC
Region: eu
Data Encryption: In Use
Continuous Protection: On
Forked From: HEROKU_POSTGRESQL_IVORY
Maintenance: not required
Maintenance window: Wednesdays 21:00 to Thursdays 01:00 UTC
Add-on: postgresql-deep-1111
heroku heroku-postgres heroku-cli
heroku heroku-postgres heroku-cli
edited Nov 22 at 15:44
asked Nov 22 at 15:18
JMurphyWeb
13410
13410
Can you add the full output frompg:info
? Or at least the information forIVORY
? Also, did you upgradeIVORY
trying to get access to the rollback feature? Or was it always a standard-0?
– RangerRanger
Nov 22 at 15:48
@RangerRanger thanks for help, I'll be sure to post a more full question in the future. I actually just figured it out. It was using--TO
as opposed to--to
! I'm sure I didn't write the whole thing out myself, I copied it from somewhere, but that's my bad.
– JMurphyWeb
Nov 22 at 16:17
Glad to hear it!
– RangerRanger
Nov 22 at 16:19
add a comment |
Can you add the full output frompg:info
? Or at least the information forIVORY
? Also, did you upgradeIVORY
trying to get access to the rollback feature? Or was it always a standard-0?
– RangerRanger
Nov 22 at 15:48
@RangerRanger thanks for help, I'll be sure to post a more full question in the future. I actually just figured it out. It was using--TO
as opposed to--to
! I'm sure I didn't write the whole thing out myself, I copied it from somewhere, but that's my bad.
– JMurphyWeb
Nov 22 at 16:17
Glad to hear it!
– RangerRanger
Nov 22 at 16:19
Can you add the full output from
pg:info
? Or at least the information for IVORY
? Also, did you upgrade IVORY
trying to get access to the rollback feature? Or was it always a standard-0?– RangerRanger
Nov 22 at 15:48
Can you add the full output from
pg:info
? Or at least the information for IVORY
? Also, did you upgrade IVORY
trying to get access to the rollback feature? Or was it always a standard-0?– RangerRanger
Nov 22 at 15:48
@RangerRanger thanks for help, I'll be sure to post a more full question in the future. I actually just figured it out. It was using
--TO
as opposed to --to
! I'm sure I didn't write the whole thing out myself, I copied it from somewhere, but that's my bad.– JMurphyWeb
Nov 22 at 16:17
@RangerRanger thanks for help, I'll be sure to post a more full question in the future. I actually just figured it out. It was using
--TO
as opposed to --to
! I'm sure I didn't write the whole thing out myself, I copied it from somewhere, but that's my bad.– JMurphyWeb
Nov 22 at 16:17
Glad to hear it!
– RangerRanger
Nov 22 at 16:19
Glad to hear it!
– RangerRanger
Nov 22 at 16:19
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
I realised soon after posting:
Make sure you use flags in lower case:
--to
as opposed to--TO
--by
as opposed to--BY
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
I realised soon after posting:
Make sure you use flags in lower case:
--to
as opposed to--TO
--by
as opposed to--BY
add a comment |
up vote
0
down vote
accepted
I realised soon after posting:
Make sure you use flags in lower case:
--to
as opposed to--TO
--by
as opposed to--BY
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
I realised soon after posting:
Make sure you use flags in lower case:
--to
as opposed to--TO
--by
as opposed to--BY
I realised soon after posting:
Make sure you use flags in lower case:
--to
as opposed to--TO
--by
as opposed to--BY
answered Nov 22 at 16:20
JMurphyWeb
13410
13410
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53433954%2fheroku-postgres-how-to-fork-pg-database-with-rollback-to-recover-lost-data%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Can you add the full output from
pg:info
? Or at least the information forIVORY
? Also, did you upgradeIVORY
trying to get access to the rollback feature? Or was it always a standard-0?– RangerRanger
Nov 22 at 15:48
@RangerRanger thanks for help, I'll be sure to post a more full question in the future. I actually just figured it out. It was using
--TO
as opposed to--to
! I'm sure I didn't write the whole thing out myself, I copied it from somewhere, but that's my bad.– JMurphyWeb
Nov 22 at 16:17
Glad to hear it!
– RangerRanger
Nov 22 at 16:19