Re: [HACKERS] Incomplete startup packet errors - Mailing list pgsql-hackers

From Jobin Augustine
Subject Re: [HACKERS] Incomplete startup packet errors
Date
Msg-id CANaTPsqxJqs31yb7ZKudOQYkh1PqM4EBSG1XXc_Kpb-P1AYUQQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Incomplete startup packet errors  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: [HACKERS] Incomplete startup packet errors  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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 



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: accounting for memory used for BufFile during hash joins
Next
From: Amit Langote
Date:
Subject: Re: Rework manipulation and structure of attribute mappings