Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Database restore does not work in VM. #194

Closed
tomkooij opened this issue Nov 1, 2017 · 2 comments
Closed

Database restore does not work in VM. #194

tomkooij opened this issue Nov 1, 2017 · 2 comments

Comments

@tomkooij
Copy link
Member

tomkooij commented Nov 1, 2017

I cannot successfully restore a postgresql database dump in my VM. I recall this happing months ago, but I attributed it to an old/stale install of my VM.

Today I destroyed my VM. git reset --hard to the current origin/master. Rebuild the VM and still the most recent database dump (Nov 1st) does not restore to a working server.

There always have been many (many!) warnings and errors, but now the station list is not restored, which means many of the other things also fail/are missing.

I use the command from README.md to restore (as user hisparc)

pg_restore --clean --if-exists --no-owner --no-acl --schema=public --dbname=publicdb /vagrant/publicdb_dump.sql

My copy of the database dump has the same MD5 hash as the dump on trave:

610e768a79ef7a926957f2de5e228223 *publicdb_dump.sql

This might be important: Will it work on pique if necessary?

@153957
Copy link
Member

153957 commented Nov 1, 2017

See #189 (mainly my comment at the end)

@tomkooij
Copy link
Member Author

tomkooij commented Nov 1, 2017

I missed that one. I'm closing this one in favor of that other issue.

@tomkooij tomkooij closed this as completed Nov 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants