Postgres Pro
Downloads
Home   >   mailing lists

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

From Magnus Hagander
Subject Re: Incomplete startup packet errors
Date
Msg-id CABUevEw0ii+tnQs1ynoPuOJybb7JbW2ZO8BCDGm=YC3+Kg4VqA@mail.gmail.com
Whole thread Raw
In response to Re: Incomplete startup packet errors  (Peter Geoghegan <pg@heroku.com>)
Responses Re: Incomplete startup packet errors  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Incomplete startup packet errors  (Tatsuo Ishii <ishii@postgresql.org>)
List pgsql-hackers
Tree view
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? 


--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Incomplete startup packet errors
Next
From: Simon Riggs
Date:
Subject: Re: Pglogical questions and problems