PostgreSQL passfile connection param #4001
Open
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.
Implements handling of the PostgreSQL URL
passfile
connection parameter. With this PR the pgpass file given in the following URL is picked up and used:Is this a breaking change?
No. This is a new feature that adds the public
PgConnectOptions::passfile_paths
method and implements handling of thepassfile
URL parameter. Even applications that pass a (currently ignored)passfile
argument will not notice any difference in behavior as a failed pgpass lookup does not error. There is the edge case of relying on the information in the default pgpass file while pointing to a different existing passfile that is currently ignored; this would break an existing application, but is a scenario I find negligible.