|
1 | 1 | <!--
|
2 |
| -$Header: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v 1.103 2002/12/13 05:49:10 momjian Exp $ |
| 2 | +$Header: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v 1.104 2003/01/06 22:48:16 momjian Exp $ |
3 | 3 | -->
|
4 | 4 |
|
5 | 5 | <chapter id="libpq">
|
@@ -110,14 +110,15 @@ PGconn *PQconnectdb(const char *conninfo)
|
110 | 110 | <listitem>
|
111 | 111 | <para>
|
112 | 112 | IP address of host to connect to. This should be in standard
|
113 |
| - numbers-and-dots form, as used by the BSD functions <function>inet_aton</> et al. If |
114 |
| - a nonzero-length string is specified, TCP/IP communication is used. |
| 113 | + IPv4 address format, e.g. <literal>172.28.40.9</>. If your machine |
| 114 | + supports IPv6, you can also use those addresses. If a nonzero-length |
| 115 | + string is specified, TCP/IP communication is used. |
115 | 116 | </para>
|
116 | 117 | <para>
|
117 | 118 | Using <literal>hostaddr</> instead of host allows the application to avoid a host
|
118 | 119 | name look-up, which may be important in applications with time
|
119 | 120 | constraints. However, Kerberos authentication requires the host
|
120 |
| - name. The following therefore applies. If host is specified without |
| 121 | + name. The following therefore applies: If host is specified without |
121 | 122 | <literal>hostaddr</>, a host name lookup is forced. If <literal>hostaddr</> is specified without
|
122 | 123 | host, the value for <literal>hostaddr</> gives the remote address; if Kerberos is
|
123 | 124 | used, this causes a reverse name query. If both host and <literal>hostaddr</> are
|
|