that 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
-APPDATA/postgresql/pgpass.txt>.
+%APPDATA%\postgresql\pgpass.txt> (where %APPDATA%>
+refers to the Application Data subdirectory in the user's profile).
A matching private key file ~/.postgresql/postgresql.key>
must also be present, and must not be world-readable.
(On Microsoft Windows these files are named
- APPDATA/postgresql/postgresql.crt and
- APPDATA/postgresql/postgresql.key.)
+ %APPDATA%\postgresql\postgresql.crt and
+ %APPDATA%\postgresql\postgresql.key.)
libpq will use the certificate list stored
therein to verify the server's certificate.
(On Microsoft Windows the file is named
- APPDATA/postgresql/root.crt.)
+ %APPDATA%\postgresql\root.crt.)
The SSL connection will
fail if the server does not present a certificate; therefore, to
use this feature the server must also have a root.crt> file.
psqlrc file and the user's
~/.psqlrc file.
(On Windows, the user's startup file is named
- APPDATA/postgresql/psqlrc.txt.)
+ %APPDATA%\postgresql\psqlrc.txt.)
See PREFIX>/share/psqlrc.sample>
for information on setting up the system-wide file. It could be used
to set up the client or the server to taste (using the \set
The command-line history is stored in the file
~/.psql_history, or
- APPDATA/postgresql/psql_history on Windows.
+ %APPDATA%\postgresql\psql_history on Windows.