Hi Tom,
> On 27. Apr, 2020, at 15:13, Tom Lane wrote:
> [ shrug... ] When connecting via a Unix socket, psql does not have a
> relevant "hostname" to report, so it reports what it's got. You are
> ascribing a meaning to HOST that it does not have, never has had, and
> never can have in this cas
=?utf-8?Q?Paul_F=C3=B6rster?= writes:
>> On 27. Apr, 2020, at 14:20, Tom Lane wrote:
>> AFAICS, psql is behaving as documented. Why are you trying to override
>> HOST like that, instead of just using some other variable?
> I could but
> a) HOST is HOST and should not point to a socket director
Hi Tom,
> On 27. Apr, 2020, at 14:20, Tom Lane wrote:
> AFAICS, psql is behaving as documented. Why are you trying to override
> HOST like that, instead of just using some other variable?
I could but
a) HOST is HOST and should not point to a socket directory. A socket directory
is not a HOST.
=?utf-8?Q?Paul_F=C3=B6rster?= writes:
> the use of :HOST in psql containing the socket directory for local
> connections is pretty useless for us, so we set it to the hostname in a
> global psqlrc file:
> \set HOST `hostname -s`
> This works great when invoking psql on the command line. But if I
