Re: [9.1] pg_stat_get_backend_server_addr
| От | Peter Eisentraut |
|---|---|
| Тема | Re: [9.1] pg_stat_get_backend_server_addr |
| Дата | |
| Msg-id | 1275058918.6851.8.camel@fsopti579.F-Secure.com обсуждение исходный текст |
| Ответ на | Re: [9.1] pg_stat_get_backend_server_addr (Bruce Momjian <bruce@momjian.us>) |
| Ответы |
Re: [9.1] pg_stat_get_backend_server_addr
Re: [9.1] pg_stat_get_backend_server_addr |
| Список | pgsql-hackers |
On fre, 2010-05-28 at 10:21 -0400, Bruce Momjian wrote: > Tom Lane wrote: > > Bruce Momjian <bruce@momjian.us> writes: > > > Tom Lane wrote: > > >> ... 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(). > > > > I think the point is to let someone find out *from another session* > > which server port number a particular session is using. I fail to see > > a significant use case for that, though. > > Uh, aren't they all using the same server port number, e.g. 5432? Is > the issue different IP addresses for the same server? Yes, I would like to know who is connecting to what IP address. It's useful if you have HA setups and you need to check which way your connections are going.
В списке pgsql-hackers по дате отправления: