From: | Paul Förster <paul(dot)foerster(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: HOST variable in psql |
Date: | 2020-04-27 12:44:44 |
Message-ID: | 0767EAE6-86F3-45D8-87B5-4A9275E3E924@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Tom,
> On 27. Apr, 2020, at 14:20, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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. This makes no sense, especially since I see no use for using a socket directory in any psql script. There are tons of use cases for the hostname, though.
b) it would require changing some scripts.
c) the docs are IMHO not 100% clear on this. I think the psqlrc should be executed on EVERY new connect, hence including \c, and this is how I interpret the docs too. But it doesn't...
also (slightly related) d) PostgreSQL unfortunately does not provide any functionality to determine the server hostname it runs on. There is an extension but I still don't see why PostgreSQL does not include this natively.
Cheers,
Paul
From | Date | Subject | |
---|---|---|---|
Next Message | Matthias Apitz | 2020-04-27 13:06:18 | Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;' |
Previous Message | Tom Lane | 2020-04-27 12:40:04 | Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;' |