diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2019-06-14 18:02:26 -0400 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2019-06-14 18:02:26 -0400 |
| commit | 313f56ce2d1b9dfd3483e4f39611baa27852835a (patch) | |
| tree | b2c9aa2846217496234412dbb3927d783ade79f6 /contrib/jsonb_plpython/jsonb_plpython.c | |
| parent | 3da73d6839dc47f1f47ca57974bf28e5abd9b572 (diff) | |
| download | postgresql-313f56ce2d1b9dfd3483e4f39611baa27852835a.tar.gz postgresql-313f56ce2d1b9dfd3483e4f39611baa27852835a.zip | |
Tweak libpq's PQhost, PQhostaddr, and psql's \connect
Fixes some problems introduced by 6e5f8d489acc:
* When reusing conninfo data from the previous connection in \connect,
the host address should only be reused if it was specified as
hostaddr; if it wasn't, then 'host' is resolved afresh. We were
reusing the same IP address, which ignores a possible DNS change
as well as any other addresses that the name resolves to than the
one that was used in the original connection.
* PQhost, PQhostaddr: Don't present user-specified hostaddr when we have
an inet_net_ntop-produced equivalent address. The latter has been
put in canonical format, which is cleaner (so it produces "127.0.0.1"
when given "host=2130706433", for example).
* Document the hostaddr-reusing aspect of \connect.
* Fix some code comments
Author: Fabien Coelho
Reported-by: Noah Misch
Discussion: https://postgr.es/m/20190527203713.GA58392@gust.leadboat.com
Diffstat (limited to 'contrib/jsonb_plpython/jsonb_plpython.c')
0 files changed, 0 insertions, 0 deletions