Done for libpq, postgres-fdw, and psql.
Reported-by: [email protected]
Discussion: https://postgr.es/m/CAKFQuwZ-T-zsVM7gApS9-XU9vGxC7Oa-UyRQPVcJFagNU=AjOw@mail.gmail.com
Backpatch-through: master
The file .pgpass in a user's home directory can
contain passwords to
be used if the connection requires a password (and no password has been
- specified otherwise). On Microsoft Windows the file is named
+ specified otherwise). On Unix systems, the directory can be specified by
+ the HOME environment variable, or if undefined, the home
+ directory of the effective user. On Microsoft Windows the file is named
%APPDATA%\postgresql\pgpass.conf (where
%APPDATA% refers to the Application Data subdirectory in
the user's profile).
user can potentially use any client certificates,
.pgpass,
.pg_service.conf etc. in the unix home directory of the
- system user the postgres server runs as. They can also use any trust
+ system user the postgres server runs as. (For details on how home
+ directories are found, see .) They can
+ also use any trust
relationship granted by authentication modes like peer
or ident authentication.
Changes the current working directory to
directory. Without argument, changes
- to the current user's home directory.
+ to the current user's home directory. For details on how home
+ directories are found, see .