Incomplete startup packet errors

Поиск
Список
Период
Сортировка
От Magnus Hagander
Тема Incomplete startup packet errors
Дата
Msg-id CABUevEzKFAaVWAM=-UPPYp56OG_pkNPibECyROhFuMCjwOVJVw@mail.gmail.com
обсуждение исходный текст
Ответы Re: Incomplete startup packet errors  (Abhijit Menon-Sen <ams@2ndQuadrant.com>)
Re: Incomplete startup packet errors  (Dave Page <dpage@pgadmin.org>)
Re: Incomplete startup packet errors  (Peter Geoghegan <pg@heroku.com>)
Список 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?

--

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: [COMMITTERS] pgsql: Add regression tests for multiple synchronous standbys.
Следующее
От: Abhijit Menon-Sen
Дата:
Сообщение: Re: Incomplete startup packet errors