Re: Flood Warning message : user=[unknown],db=[unknown],host= WARNING: pg_getnameinfo_all() failed: Temporary failure in name resolution

From: bricklen <bricklen(at)gmail(dot)com>
To: Steve Crawford <scrawford(at)pinpointresearch(dot)com>
Cc: Perumal Raj <perucinci(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Flood Warning message : user=[unknown],db=[unknown],host= WARNING: pg_getnameinfo_all() failed: Temporary failure in name resolution
Date: 2019-06-05 23:19:46
Message-ID: CAGrpgQ-PtOUwvvGO6dL1jTVw2ATJ+AQrnZ9AfAjYBHSQRmUzug@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Jun 5, 2019 at 11:08 AM Steve Crawford <
scrawford(at)pinpointresearch(dot)com> wrote:

> On Wed, Jun 5, 2019 at 10:13 AM Perumal Raj <perucinci(at)gmail(dot)com> wrote:
>
>>
>> [64459]: [1-1] user=[unknown],db=[unknown],host= WARNING:
>> pg_getnameinfo_all() failed: Temporary failure in name resolution...
>>
>
> First thing I'd check is that DNS is functioning correctly (including
> local resolution settings or caching name resolvers).
>

In addition to what Steve mentioned, I've a vague recollection from running
into this several years ago that this is triggered by having "log_hostname"
enabled in your postgresql.conf.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jan Bilek 2019-06-05 23:23:23 RE: Requirement PA-DSS 1.1.4
Previous Message Ron 2019-06-05 19:53:51 Re: configure multiple repository path in pgbackrest