On Sun, Nov 26, 2023 at 6:51 AM Peter J. Holzer wrote:
[snip]
> > But is not explanatory. I want to see host names in the log file when
> > possible, not just IP addresses.
>
> So now that you have IP addresses again, are there any for which a
> reverse lookup doesn't work?
>
I've gone through
On 2023-11-24 16:39:57 -0500, Ron Johnson wrote:
> On Fri, Nov 24, 2023 at 4:26 PM David G. Johnston
> wrote:
>
> On Friday, November 24, 2023, Ron Johnson wrote:
>
>
> The second "way" sounds interesting, but what is it filled with?
With "???"
(which isn't very helpful. I would
On Fri, Nov 24, 2023 at 4:26 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Friday, November 24, 2023, Ron Johnson 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
> a
On Friday, November 24, 2023, Ron Johnson 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
On Fri, Nov 24, 2023 at 3:46 PM Adrian Klaver
wrote:
> On 11/24/23 12:30, Ron Johnson wrote:
> > PG 9.6.24 (Yes, I know it's EOL.)
> >
> > I'm seeing lots of these in the postgresql log file:
> > 2023-11-24 15:09:02.224 EST [unknown] [unknown]
> > 18163 [unknown]
On 11/24/23 12:30, Ron Johnson wrote:
PG 9.6.24 (Yes, I know it's EOL.)
I'm seeing lots of these in the postgresql log file:
2023-11-24 15:09:02.224 EST [unknown] [unknown]
18163 [unknown] 01000 WARNING: 01000:
pg_getnameinfo_all() failed: Temporary f
