Closed will closed 1 year ago
Documentation says that the socket is .s.PGSQL.nnnn
where nnnn
is the server port, so it's possible to start a Postgres server on the non default port, and that would affect the UNIX socket file? Maybe the PG shard should try to use PGPORT
when specified?
It's an oddball edge case, but :shrug:
Yeah that looks like what psql
using libpq does, so it's not unreasonable. Right now people can specify the path manually, but it could be nice to still get the automatic search to work too
This change makes the driver find the actual socket file and is consistent with how libpq appends .s.PGSQL.5432 to the value of the env var when it's a path:
When the value is a domain the behavior doesn't change