Re: pg_getnameinfo_all() failed: Temporary failure in name resolution

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "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:26:14
Message-ID: CAKFQuwYe6La_7eGuabErFs7zu688_pBZs8WpRvaRTKT8h2L34g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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.

>
> I added "log_hostname = on" to postgresql.conf earlier in the day. When I
> commented that out, the errors stopped happening.
>

This makes sense.

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2023-11-24 21:37:56 Re: replication primary writting infinite number of WAL files
Previous Message Ron Johnson 2023-11-24 21:14:22 Re: pg_getnameinfo_all() failed: Temporary failure in name resolution