| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jobin Augustine <jobinau(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Christoph Berg <myon(at)debian(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Incomplete startup packet errors |
| Date: | 2019-11-25 15:02:42 |
| Message-ID: | 23082.1574694162@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jobin Augustine <jobinau(at)gmail(dot)com> writes:
> 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
>>
>>
Well, the agreed-to behavior change was to not log anything if the
connection is closed without any data having been sent. If the
client *does* send something, and it doesn't look like a valid
connection request, I think we absolutely should log that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Juan José Santamaría Flecha | 2019-11-25 15:06:46 | Re: logical decoding : exceeded maxAllocatedDescs for .spill files |
| Previous Message | Jehan-Guillaume de Rorthais | 2019-11-25 14:55:19 | Re: segmentation fault when cassert enabled |