| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Incomplete startup packet errors |
| Date: | 2016-04-13 08:02:22 |
| Message-ID: | CABUevEzKFAaVWAM=-UPPYp56OG_pkNPibECyROhFuMCjwOVJVw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Abhijit Menon-Sen | 2016-04-13 08:04:06 | Re: Incomplete startup packet errors |
| Previous Message | Michael Paquier | 2016-04-13 07:54:04 | Re: [COMMITTERS] pgsql: Add regression tests for multiple synchronous standbys. |