| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Incomplete startup packet errors |
| Date: | 2016-04-13 08:21:49 |
| Message-ID: | CA+OCxoydn7sFxFhf4XaJk+abmXyDJ1MoX=7m3vynBGnPRu3GDw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 13, 2016 at 9:02 AM, Magnus Hagander <magnus(at)hagander(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-04-13 08:24:17 | Re: Incomplete startup packet errors |
| Previous Message | Kyotaro HORIGUCHI | 2016-04-13 08:14:22 | Re: Support for N synchronous standby servers - take 2 |