From 46ca159bf5a65f80ecbae07e762f0cb637a562aa Mon Sep 17 00:00:00 2001 From: James Coleman Date: Tue, 28 Sep 2021 10:13:49 -0400 Subject: [PATCH v1] Document spaces in .pgpass need to be escaped. A coworker has a space in a Postgres password and noticed .pgpass didn't work; escaping it fixed the issue. That requirement wasn't documented (despite other escaping requirements being documented), so add that comment now. --- doc/src/sgml/libpq.sgml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index b449c83..ecce0bd 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -8091,8 +8091,9 @@ myEventProc(PGEventId evtId, void *evtInfo, void *passThrough) *, which matches anything. The password field from the first line that matches the current connection parameters will be used. (Therefore, put more-specific entries first when you are using - wildcards.) If an entry needs to contain : or - \, escape this character with \. + wildcards.) If an entry needs to contain :, + , + or \, escape this character with \. The host name field is matched to the host connection parameter if that is specified, otherwise to the hostaddr parameter if that is specified; if neither -- 2.10.1