On 2019-04-12 17:57, Tom Lane wrote:
>> For a socket connection, directory is important and that
>> information I can get from unix_socket_directories parameter (I've
>> never seen a setup with multiple socket directories).
> 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. It's probably of marginal
use, as you also say.
I don't get what this has to do with walsenders specifically. Do they
have each walsender connect to a different socket?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
