| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jobin Augustine <jobinau(at)gmail(dot)com>, 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-12-04 04:08:12 |
| Message-ID: | 20191204040811.GC6962@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greetings,
* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> 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.
Agreed.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2019-12-04 04:47:35 | Re: [HACKERS] WAL logging problem in 9.4.3? |
| Previous Message | Dilip Kumar | 2019-12-04 03:57:12 | Re: [HACKERS] Block level parallel vacuum |