postgresql - Heroku: update database plan, then delete the first one -


i updated db plan on heroku quite time ago, following clear tutorial: https://devcenter.heroku.com/articles/upgrade-heroku-postgres-with-pgbackups

so have 2 db running:

$ heroku pg:info === heroku_postgresql_navy_url (database_url) plan:        crane status:      available data size:   26.1 mb tables:      52 pg version:  9.2.6 connections: 8 fork/follow: available rollback:    unsupported created:     2013-11-04 09:42 utc region:      eu-west-1 maintenance: not required  === heroku_postgresql_orange_url plan:        dev status:      available connections: 0 pg version:  9.2.7 created:     2013-08-13 20:05 utc data size:   11.8 mb tables:      49 rows:        7725/10000 (in compliance, close row limit) - refreshing fork/follow: unsupported rollback:    unsupported region:      europe 

i keep receiving mails saying i'm close rate limit on heroku_postgresql_orange_url. i'd rather delete it, i'd make sure i'm not going loose data. heroku not clear it:

the original database continue run (and incur charges) after upgrade. if desired, remove after upgrade successful.

but can 100% sure data in heroku_postgresql_orange_url duplicated in heroku_postgresql_navy_url? because if heroku_postgresql_orange_url follower of heroku_postgresql_navy_url, data should big first one.

so need confirmation.

thanks

it sounds me upgrade dumped , reloaded db. new db copy of old one. if that's case, contain data old 1 at time copied - if kept on adding new data old database, data wouldn't appear in new one.

i recommend before dropping db you:

  • disable access except pg_dump
  • dump pg_dump (or use heroku's tools that)
  • ... , delete it.

that way, if discover you've made mistake, have dump restore.


Comments

Popular posts from this blog

c# - How to get the current UAC mode -

postgresql - Lazarus + Postgres: incomplete startup packet -

javascript - Ajax jqXHR.status==0 fix error -