Re: Incomplete startup packet errors
| От | Tom Lane |
|---|---|
| Тема | Re: Incomplete startup packet errors |
| Дата | |
| Msg-id | 20758.1460555803@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Incomplete startup packet errors (Magnus Hagander <magnus@hagander.net>) |
| Ответы |
Re: Incomplete startup packet errors
|
| Список | pgsql-hackers |
Magnus Hagander <magnus@hagander.net> writes:
> On Wed, Apr 13, 2016 at 10:24 AM, Peter Geoghegan <pg@heroku.com> wrote:
>> On Wed, Apr 13, 2016 at 1: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've also seen it caused by port scanning.
> Yes, definitely. Question there might be if that's actually a case when we
> *want* that logging?
I should think someone might. But I doubt we want to introduce another
GUC for this. Would it be okay to downgrade the message to DEBUG1 if
zero bytes were received?
regards, tom lane
В списке pgsql-hackers по дате отправления: