Re: Incomplete startup packet errors

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Peter Geoghegan <pg(at)heroku(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Incomplete startup packet errors
Date: 2016-04-13 08:25:35
Message-ID: CABUevEw0ii+tnQs1ynoPuOJybb7JbW2ZO8BCDGm=YC3+Kg4VqA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 13, 2016 at 10:24 AM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:

> On Wed, Apr 13, 2016 at 1: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'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/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2016-04-13 08:38:39 Re: Pglogical questions and problems
Previous Message Peter Geoghegan 2016-04-13 08:24:17 Re: Incomplete startup packet errors