| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_getnameinfo_all() failed: Temporary failure in name resolution |
| Date: | 2023-11-24 21:39:57 |
| Message-ID: | CANzqJaBP7mD0Z35A7T2UO+MiAH4wWXWrb1bpU0qrVj1Z3gvzRQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Nov 24, 2023 at 4:26 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Friday, November 24, 2023, Ron Johnson <ronljohnsonjr(at)gmail(dot)com> wrote:
>>
>>
>> The second "way" sounds interesting, but what is it filled with?
>>
>
> What does it matter? It’s an internal detail that apparently gets exposed
> as [unknown] appearing in your log file where the client ip address would
> normally be.
>
Because I'd hope that the log file would tell me the errant host name.
>
>> I added "log_hostname = on" to postgresql.conf earlier in the day. When
>> I commented that out, the errors stopped happening.
>>
>
> This makes sense.
>
But is not explanatory. I want to see host names in the log file when
possible, not just IP addresses.
In pg_hba.conf. all application servers are either IP addresses, or names
that are explicitly defined in /etc/hosts.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Les | 2023-11-24 22:01:46 | Re: replication primary writting infinite number of WAL files |
| Previous Message | Adrian Klaver | 2023-11-24 21:37:56 | Re: replication primary writting infinite number of WAL files |