Horton

Re: [HACKERS] Incomplete startup packet errors

jobinau@gmail.com

View thread View on postgr.es
From: Jobin Augustine <jobinau@gmail.com>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Christoph Berg <myon@debian.org>, Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-11-25T08:55:38Z
Lists: pgsql-hackers 
On Thu, Mar 7, 2019 at 1:26 AM Andrew Dunstan <
andrew.dunstan@2ndquadrant.com> wrote:

>
> On 3/6/19 12:12 PM, Robert Haas wrote:
> > On Tue, Mar 5, 2019 at 5:35 PM Andrew Dunstan
> > <andrew.dunstan@2ndquadrant.com> wrote:
> >> OK, I think we have agreement on Tom's patch. Do we want to backpatch
> OK, no back-patching it is.
>
However, Checking whether the port is open is resulting in error log like:
2019-11-25 14:03:44.414 IST [14475] LOG:  invalid length of startup packet
Yes, This is different from "Incomplete startup packet" discussed here.

Steps to reproduce:
$ telnet localhost 5432


>
>

Commits

  1. Don't log incomplete startup packet if it's empty