| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Atul Kumar <akumar14871(at)gmail(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: issue with reading hostname |
| Date: | 2024-04-22 21:59:17 |
| Message-ID: | CAKFQuwagbtfSjzeu6SgZX7AbsiisuUXhKKiQJ2aBRpaGMjAN0A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Apr 22, 2024 at 2:54 PM Atul Kumar <akumar14871(at)gmail(dot)com> wrote:
> I mean, Once I change the hostname then how will the socket read the new
> hostname ? Does it require a postgres service restart ?
>
>>
>>
-h doesn't strictly mean hostname (the wording choice here does seem
problematic), rather it is simply a direct specification of how and
where the psql client looks for and connects to the server. When the
specification is a filename it is that file that is used and hostname and
any other networking-related stuff is immaterial. Though the server does
choose to borrow the port number 5432 from networking to construct the
unique name out of convenience.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2024-04-22 21:59:39 | Re: issue with reading hostname |
| Previous Message | Adrian Klaver | 2024-04-22 21:56:44 | Re: CLUSTER vs. VACUUM FULL |