| From: | Pavel Demidov <zeller56(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: LOG: incomplete startup packet |
| Date: | 2018-11-13 15:41:49 |
| Message-ID: | CAJ3u2CnBWpEQdj4m9aSaT37o-9ymrf-sjmA5YN63a-7fxbtMGQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
Regards,
Paul
On Thu, Nov 8, 2018 at 1:06 PM Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
wrote:
> Hi
>
> čt 8. 11. 2018 v 10:19 odesílatel Pavel Demidov <zeller56(at)gmail(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2018-11-13 15:49:37 | Re: LOG: incomplete startup packet |
| Previous Message | George Woodring | 2018-11-13 15:39:40 | Re: Plpgsql search_path issue going from 9.3 to 9.6 |