Adding a helpful error message for "Could not connect" #1047
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #983
I just got bit by this again. If your default user is
postgres
, you generally already have a database calledpostgres
; however, in the case of Avram specs, we use the userlucky
. This means you have to have a local db calllucky
in order to runlucky db.create
. This is because when we removed thepg_client
dependency we no longer have access tocreatedb
. Instead, we have to connect to the DB server and run some SQL... but postgres doesn't let you connect to the server without being attached to some database.. 🐔 🥚 🤷♂️This PR just adds an error message that tells you
That should at least point to a common fix for this problem.