Re: Enhance pg_stat_wal_receiver view to display connected host
Haribabu Kommi <kommi.haribabu@gmail.com>
From: Haribabu Kommi <kommi.haribabu@gmail.com>
To: Michael Paquier <michael.paquier@gmail.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
Pg Hackers <pgsql-hackers@postgresql.org>, Robert Haas <robertmhaas@gmail.com>
Date: 2018-01-12T05:32:54Z
Lists: pgsql-hackers
Attachments
- PQhost-update-to-return-proper-host-details_v2.patch (application/octet-stream) patch v2
On Fri, Jan 12, 2018 at 4:06 PM, Michael Paquier <michael.paquier@gmail.com> wrote: > On Fri, Jan 12, 2018 at 03:55:04PM +1100, Haribabu Kommi wrote: > > Before posting the patch, first I did the same, upon further study > > I didn't find any scenario where the value is not present in > > conn->connhost[conn->whichhost].host and present in conn->pghost. > > > > If user provides "host" as connection option, the value is present > > in both the variables. Even if the connection is unix domain socket, > > there is a value in conn->connhost[conn->whichhost].host. > > > > In case if user provides only hostaddr and host connection option, > > then in that case, both the members are NULL. So even if we add > > that case, it will be dead code. > > Hm. Wouldn't it matter for cases where caller has not yet established a > connection to the server but still calls PQhost to get the host string? > Yes I agree that the above scenario leads to a wrong result with the earlier patch, Updated patch attached by including the conn->pghost. Thanks for the review. Regards, Hari Babu Fujitsu Australia
Commits
-
Enhance pg_stat_wal_receiver view to display host and port of sender server.
- 9a895462d940 11.0 landed
-
Allow multiple hostaddrs to go with multiple hostnames.
- 7b02ba62e9ff 10.0 cited
-
libpq: Fix inadvertent change in PQhost() behavior.
- 11003eb55658 10.0 cited
-
libpq: Allow connection strings and URIs to specify multiple hosts.
- 274bb2b3857c 10.0 cited