11<!--
2- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.175 2005/01/0618:29:07 tgl Exp $
2+ $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.176 2005/01/0621:20:43 tgl Exp $
33-->
44
55 <chapter id="libpq">
@@ -3882,7 +3882,8 @@ The file <filename>.pgpass</filename> in a user's home directory is a file
38823882that can contain passwords to be used if the connection requires a
38833883password (and no password has been specified otherwise).
38843884On 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).
38863887</para>
38873888
38883889<para>
@@ -3932,8 +3933,8 @@ however.)
39323933 A matching private key file <filename>~/.postgresql/postgresql.key</>
39333934 must also be present, and must not be world-readable.
39343935 (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>.)
39373938 </para>
39383939
39393940 <para>
@@ -3942,7 +3943,7 @@ however.)
39423943 <application>libpq</application> will use the certificate list stored
39433944 therein to verify the server's certificate.
39443945 (On Microsoft Windows the file is named
3945- <filename>APPDATA/ postgresql/ root.crt</filename>.)
3946+ <filename>% APPDATA%\ postgresql\ root.crt</filename>.)
39463947 The SSL connection will
39473948 fail if the server does not present a certificate; therefore, to
39483949 use this feature the server must also have a <filename>root.crt</> file.