1
1
<!--
2
- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.175 2005/01/06 18:29:07 tgl Exp $
2
+ $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.176 2005/01/06 21:20:43 tgl Exp $
3
3
-->
4
4
5
5
<chapter id="libpq">
@@ -3882,7 +3882,8 @@ The file <filename>.pgpass</filename> in a user's home directory is a file
3882
3882
that can contain passwords to be used if the connection requires a
3883
3883
password (and no password has been specified otherwise).
3884
3884
On Microsoft Windows the file is named
3885
- <filename>APPDATA/postgresql/pgpass.txt</>.
3885
+ <filename>%APPDATA%\postgresql\pgpass.txt</> (where <filename>%APPDATA%</>
3886
+ refers to the Application Data subdirectory in the user's profile).
3886
3887
</para>
3887
3888
3888
3889
<para>
@@ -3932,8 +3933,8 @@ however.)
3932
3933
A matching private key file <filename>~/.postgresql/postgresql.key</>
3933
3934
must also be present, and must not be world-readable.
3934
3935
(On Microsoft Windows these files are named
3935
- <filename>APPDATA/ postgresql/ postgresql.crt</filename> and
3936
- <filename>APPDATA/ postgresql/ postgresql.key</filename>.)
3936
+ <filename>% APPDATA%\ postgresql\ postgresql.crt</filename> and
3937
+ <filename>% APPDATA%\ postgresql\ postgresql.key</filename>.)
3937
3938
</para>
3938
3939
3939
3940
<para>
@@ -3942,7 +3943,7 @@ however.)
3942
3943
<application>libpq</application> will use the certificate list stored
3943
3944
therein to verify the server's certificate.
3944
3945
(On Microsoft Windows the file is named
3945
- <filename>APPDATA/ postgresql/ root.crt</filename>.)
3946
+ <filename>% APPDATA%\ postgresql\ root.crt</filename>.)
3946
3947
The SSL connection will
3947
3948
fail if the server does not present a certificate; therefore, to
3948
3949
use this feature the server must also have a <filename>root.crt</> file.
0 commit comments