Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> On 2019-04-12 17:57, Tom Lane wrote:
>> Those are actually pretty common, for example if you use Red Hat's
>> packaging you will have both /var/run/postgresql and /tmp as socket
>> directories (since they consider use of /tmp deprecated, but getting
>> rid of all clients' use of it turns out to be really hard). However,
>> it's definitely fair to question whether anyone *cares* which of
>> the server's socket directories a given connection used. Aren't
>> they going to be pretty much all equivalent?
> So what is being asked here is really information about which end point
> on the server is being connected to. That is also information for the
> TCP/IP case that we don't currently provide.
Good point.
> It's probably of marginal use, as you also say.
Yeah. Per downthread discussion, what Tatsuo-san really wants to know
is not that at all, but which client (slave server) is connecting.
It's not very clear how to identify the client, but knowing which socket
it came through doesn't seem to help for that.
regards, tom lane