Re: Incomplete startup packet errors - Mailing list pgsql-hackers

From Dave Page
Subject Re: Incomplete startup packet errors
Date
Msg-id CA+OCxoydn7sFxFhf4XaJk+abmXyDJ1MoX=7m3vynBGnPRu3GDw@mail.gmail.com
Whole thread Raw
In response to Incomplete startup packet errors  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On Wed, Apr 13, 2016 at 9:02 AM, Magnus Hagander <magnus@hagander.net> wrote:
> It's fairly common to see a lot of "Incomplete startup packet" in the
> logfiles caused by monitoring or healthcheck connections.
>
> I wonder if it would make sense to only log that error if *at least one
> byte* has been received and then it becomes empty. Meaning that if the
> client just connects+disconnects without sending anything, we don't log
> anything. At least at the default log level (we could have a DEBUG level
> that logged "connection closed immediately").
>
> That would get rid of a lot of logspam.
>
> Would that make sense?

Absolutely. It would be very nice to get rid of such noise.

-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Support for N synchronous standby servers - take 2
Next
From: Peter Geoghegan
Date:
Subject: Re: Incomplete startup packet errors