Re: [9.1] pg_stat_get_backend_server_addr - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [9.1] pg_stat_get_backend_server_addr
Date
Msg-id 201005281421.o4SELNq13210@momjian.us
Whole thread Raw
In response to Re: [9.1] pg_stat_get_backend_server_addr  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [9.1] pg_stat_get_backend_server_addr
List pgsql-hackers
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?

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [9.1] pg_stat_get_backend_server_addr
Next
From: Andrew Dunstan
Date:
Subject: Re: functional call named notation clashes with SQL feature