| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [9.1] pg_stat_get_backend_server_addr |
| Date: | 2010-05-28 13:41:24 |
| Message-ID: | 201005281341.o4SDfOo04222@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > There are functions pg_stat_get_backend_client_addr and
> > pg_stat_get_backend_client_port, which are exposed through the
> > pg_stat_activity view, but there is no straightforward way to get the
> > server-side address and port of a connection. This is obviously much
> > less commonly needed than the client information,
>
> ... indeed. Is it worth burdening the pg_stats mechanism with this?
> The use case seems vanishingly thin.
I am confused how this is different from inet_server_addr() and
inet_server_port().
Also, these functions return nothing for unix domain connections.
Should they, particularly for the port number which we do use to map to
a socket name?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-05-28 13:47:20 | Re: Working with PostgreSQL enums in C code |
| Previous Message | Tom Lane | 2010-05-28 13:26:56 | Re: functional call named notation clashes with SQL feature |