Skip to content

Conversation

V02460
Copy link
Contributor

@V02460 V02460 commented Aug 25, 2025

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:

postgres://user@dbhost/mydb?passfile=/non/default/pgpass

Is this a breaking change?

No. This is a new feature that adds the public PgConnectOptions::passfile_paths method and implements handling of the passfile 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.

@V02460 V02460 force-pushed the pgpass-connection-param branch from 8c124d5 to ffa2be6 Compare August 25, 2025 20:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant