Hi Diego,
I agree that this is a client-side issue and that libpq is a client
library. But that does not mean libpq should model the whole route to
the server.
A route can contain several SSH hops, proxies, and poolers:
libpq -> localhost:39907 -> SSH jump1 -> SSH jump2
-> PgBouncer:6432 -> PostgreSQL:5432
It is not clear why libpq should expose exactly two endpoints. Which
port is the "server port" here: 39907, 6432, or 5432? Only 39907 is
visible to libpq.
I think libpq should keep one connection endpoint, as it does today.
port and PQport() should continue to mean the port to which libpq
actually connects.
SSH forwarding should be configured by SSH itself, for example with
ProxyJump and LocalForward in ~/.ssh/config. If an application creates
a tunnel, it should manage that mapping itself. Pooler routing should
likewise remain in the pooler configuration.
For these reasons, I do not think portaddr belongs in libpq.
Best regards,
Denis Smirnov
