From: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
---|---|
To: | 'Andreas Karlsson' <andreas(at)proxel(dot)se>, 'Michael Paquier' <michael(dot)paquier(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, "mithun(dot)cy(at)enterprisedb(dot)com" <mithun(dot)cy(at)enterprisedb(dot)com> |
Subject: | Re: Broken SSL tests in master |
Date: | 2016-11-25 06:19:49 |
Message-ID: | 0A3221C70F24FB45833433255569204D1F65B2FD@G01JPEXMBYT05 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
From: pgsql-hackers-owner(at)postgresql(dot)org
> sense to add support for multiple hostaddrs. For consitency's sake if
> nothing else.
Yes, consistency and performance. The purpose of hostaddr is to speed up connection by eliminating DNS lookup, isn't it? Then, some users should want to specify multiple IP addresses for hostaddr and omit host.
> By the way is comma separated hosts documented somewhere? It is not included
> in
> https://www.postgresql.org/docs/9.6/static/libpq-connect.html#LIBPQ-PA
> RAMKEYWORDS.
Specifying multiple hosts is a new feature to be introduced in v10, so that's here:
https://www.postgresql.org/docs/devel/static/libpq-connect.html
Regards
Takayuki Tsunakawa
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Karlsson | 2016-11-25 06:33:36 | Re: Broken SSL tests in master |
Previous Message | Tom Lane | 2016-11-25 06:16:41 | Re: Random PGDLLIMPORTing |