https://www.percona.com/blog/postgresql-12-improvement-benign-log-entries-incomplete-startup-packet/ Tue, 13 Feb 2024 18:37:56 +0000 hourly 1 https://wordpress.org/?v=6.5.2 https://www.percona.com/blog/postgresql-12-improvement-benign-log-entries-incomplete-startup-packet/#comment-10971519 Fri, 06 Dec 2019 11:30:19 +0000 https://www.percona.com/blog/?p=63692#comment-10971519 PostgreSQL won’t store such information inside database. but data will be available in log files. External tooling can parse the log files and store if required. Alternatively log file in CSV format can be used by file_fdw

]]> https://www.percona.com/blog/postgresql-12-improvement-benign-log-entries-incomplete-startup-packet/#comment-10971517 Fri, 06 Dec 2019 03:03:20 +0000 https://www.percona.com/blog/?p=63692#comment-10971517 If there are too many “bad” connections like this, does postgresql provide
some statistics like, the number of “bad” connections those with incomplete
packet, and those with hard reset?

]]>