diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2019-09-11 10:15:23 -0300 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2019-09-11 10:15:59 -0300 |
| commit | 75f46eaee20c38b2a04f569e8a5fed4f63091bd3 (patch) | |
| tree | b6a84951d131ebd40e2397f268f7ddc8ad8f0baf | |
| parent | 8a0deae8d9b6861265cf4ebf25a9e4385f4c7672 (diff) | |
| download | postgresql-75f46eaee20c38b2a04f569e8a5fed4f63091bd3.tar.gz postgresql-75f46eaee20c38b2a04f569e8a5fed4f63091bd3.zip | |
libpq docs: be clearer about conninfo's 'hostaddr'
The previous wording was a bit too terse, too vague on the subject of
'host' and 'hostaddr' in connection specifications, which has caused
people to waste time trying to conform to rules because of
misunderstanding the whole thing; this small change should make things
clearer.
Author: Robert Haas, stemming from Fabien Coelho's complaints
Discussion: https://postgr.es/m/alpine.DEB.2.21.1808201323020.13832@lancre
| -rw-r--r-- | doc/src/sgml/libpq.sgml | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index 56014855557..0a187e256a4 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -993,10 +993,14 @@ postgresql://%2Fvar%2Flib%2Fpostgresql/dbname your machine supports IPv6, you can also use those addresses. TCP/IP communication is always used when a nonempty string is specified for this parameter. + If this parameter is not specified, the value of <literal>host</literal> + will be looked up to find the corresponding IP address — or, if + <literal>host</literal> specifies an IP address, that value will be + used directly. </para> <para> - Using <literal>hostaddr</literal> instead of <literal>host</literal> allows the + Using <literal>hostaddr</literal> allows the application to avoid a host name look-up, which might be important in applications with time constraints. However, a host name is required for GSSAPI or SSPI authentication |