[!] use native Postgres connection parameters and ENVVARs #695
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pashagolub
force-pushed
the
use-native-pg-env-vars
branch
from
c09402a to
fae934e
Compare
Drop all custom connection parameters and move to the native Postgres handling, e.g. PGHOST, PGPORT, etc. Allow user to specify a whole connection string with `--constr` or as unnamed parameter.
pashagolub
force-pushed
the
use-native-pg-env-vars
branch
from
fae934e to
2dc9d24
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Drop all custom connection parameters and move to the native Postgres handling, e.g. PGHOST, PGPORT, etc. Allow user to specify a whole connection string with
--constror as unnamed parameter.