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

Problems after dropping edgedb database #1729

Closed
CodesInChaos opened this issue Aug 29, 2020 · 0 comments · Fixed by #1737
Closed

Problems after dropping edgedb database #1729

CodesInChaos opened this issue Aug 29, 2020 · 0 comments · Fixed by #1737

Comments

@CodesInChaos
Copy link
Contributor

After drop database edgedb, I can't recreate it because it supposedly already exists. However I can't connect to it either. And after stopping the server, I can't start it again.

elprans added a commit that referenced this issue Sep 1, 2020
The `edgedb` database is a database that we create by default, but it
should not be special: it can be dropped, and, accordingly, the server
should not rely on it being present.  Instead, use the `edgedb0`
template database for system purposes.  To do this, hoist the connection
block from PostgreSQL level to EdgeDB level.

Fixes: #1729
elprans added a commit that referenced this issue Sep 1, 2020
…al (#1737)

The `edgedb` database is a database that we create by default, but it
should not be special: it can be dropped, and, accordingly, the server
should not rely on it being present.  Instead, use the `edgedb0`
template database for system purposes.  To do this, hoist the connection
block from PostgreSQL level to EdgeDB level.

Fixes: #1729
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants