Re: LOG: incomplete startup packet - Mailing list pgsql-general

From Pavel Stehule
Subject Re: LOG: incomplete startup packet
Date
Msg-id CAFj8pRDtwsxj63=LaWSwA8u7NrU9k9+dJtz2gB_0f4SxCM1sQA@mail.gmail.com
Whole thread Raw
In response to Re: LOG: incomplete startup packet  (Pavel Demidov <zeller56@gmail.com>)
List pgsql-general


út 13. 11. 2018 v 16:42 odesílatel Pavel Demidov <zeller56@gmail.com> napsal:
Hello,
Thank your answer. If there are a lot of messages 'LOG: incomplete startup packet' into postgres log will it cause the log overflow?
Does it possible to filter it or ban to write.

It is garbage. Usually it means nothing, but better to work live without this garbage.

Pavel



Regards,
Paul

On Thu, Nov 8, 2018 at 1:06 PM Pavel Stehule <pavel.stehule@gmail.com> wrote:
Hi

čt 8. 11. 2018 v 10:19 odesílatel Pavel Demidov <zeller56@gmail.com> napsal:
Hello,

Time to time found in postgres.log the following message

01:35:22.608  LOG: incomplete startup packet
01:35:27.147  LOG: incomplete startup packet
01:35:52.593  LOG: incomplete startup packet
01:35:57.146  LOG: incomplete startup packet

01:36:22.596  LOG: incomplete startup packet
01:36:27.146  LOG: incomplete startup packet
01:36:52.593  LOG: incomplete startup packet
01:36:57.145  LOG: incomplete startup packet

Are any way exists how to identify the source. What need to collect and what need to see.

Best Regards
Paul

some monitoring tools does it

Regards

Pavel

pgsql-general by date:

Previous
From: Pavel Demidov
Date:
Subject: Re: LOG: incomplete startup packet
Next
From: Ravi Krishna
Date:
Subject: Re: Plpgsql search_path issue going from 9.3 to 9.6