-
Notifications
You must be signed in to change notification settings - Fork 119
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 already exists" when restoring #33
Comments
Apparently Postgresql needs database-names escaped when they contain "-". And, apparently sqlalchemy does not do this automatically. If I add database = '%s%s%s' % ('"', database, '"') to def remove_database() in operations.py, things are working for me again. Do you know of any way to maybe using configuration tell Sqlalchemy to escape databasenames? |
Hey, I'm also seeing this issue with subsequent restore calls.
I'm sure when testing this earlier in the week i was able to call restore multiple times without any issue :/ Update: re-creating the snapshot and removing the old ones seem to have resolved the issue. Perhaps it's possible that the stellar_data table got in a weird state or something ? Will leave this here in case you want to pick this up. Update 2: Issue has resurfaced already :/ I'll see if i can find a way to consistently re-produce this error. |
I'm seeing the same problem on PostgreSQl 9.6.11 running inside a Docker container. In my case, this seems to be caused by #62. |
When trying to restore the database, I get the following error:
What am I missing? When I remove the database using pgAdmin before restoring, all is fine.
The text was updated successfully, but these errors were encountered: