From: | Jobin Augustine <jobinau(at)gmail(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Christoph Berg <myon(at)debian(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [HACKERS] Incomplete startup packet errors |
Date: | 2019-11-25 08:55:38 |
Message-ID: | CANaTPsqxJqs31yb7ZKudOQYkh1PqM4EBSG1XXc_Kpb-P1AYUQQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Mar 7, 2019 at 1:26 AM Andrew Dunstan <
andrew(dot)dunstan(at)2ndquadrant(dot)com> wrote:
>
> On 3/6/19 12:12 PM, Robert Haas wrote:
> > On Tue, Mar 5, 2019 at 5:35 PM Andrew Dunstan
> > <andrew(dot)dunstan(at)2ndquadrant(dot)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
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2019-11-25 08:55:50 | Re: Rework manipulation and structure of attribute mappings |
Previous Message | Michael Paquier | 2019-11-25 08:33:35 | Re: accounting for memory used for BufFile during hash joins |