Re: General Inquiry

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: FrancoisClo(at)Nedbank(dot)co(dot)za
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: General Inquiry
Date: 2022-07-06 00:49:57
Message-ID: 20220706.094957.2155099674543545895.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

At Tue, 5 Jul 2022 08:49:40 +0000, "Cloete, F. (Francois)" <FrancoisClo(at)Nedbank(dot)co(dot)za> wrote in
> Good morning,
> Can you please confirm if I need to contact the postgresql community fro some assistance can I use this e-mail address or another e-mail ?

pgsql-general is the right place for that. Welcome.

> We keep on seeing the below entries in our postgresql.log file getting written what seems to be every millisecond.

> UTF [32640]: [1-1] user=[unknown],db=[unknown],app=[unknown],client=[local] L

Unfortunately the screen capture is missing the most significant
part. But I guess that they are "LOG: connection received".

If this is correct, log_connection is set to on on your server, which
makes server record every incoming connection like this. The frequent
log lines mean that someone on the local host is frequently (trying)
making connections to the server.

If they are unexpected incoming connections, one possibility is that
something like health-check or keep alive thing is having a wrong
interval setting.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2022-07-06 01:16:33 Re: Seems to be impossible to set a NULL search_path
Previous Message Adrian Klaver 2022-07-05 23:33:43 Re: Seems to be impossible to set a NULL search_path