BUG #15292: Multiple Messages "2018-07-24 10:46:12.566 CEST [32029]LOG: invalid length of startup" in logfile - Mailing list pgsql-bugs

From PG Bug reporting form
Subject BUG #15292: Multiple Messages "2018-07-24 10:46:12.566 CEST [32029]LOG: invalid length of startup" in logfile
Date
Msg-id 153242398409.1403.3646573029055189847@wrigleys.postgresql.org
Whole thread Raw
Responses Re: BUG #15292: Multiple Messages "2018-07-24 10:46:12.566 CEST [32029] LOG: invalid length of startup" in logfile  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      15292
Logged by:          stefan muster
Email address:      stefan.muster@isc-ejpd.admin.ch
PostgreSQL version: 11beta2
Operating system:   SUSE Linux Enterprise Server 12 (x86_64)
Description:

Modification in pg_hba.conf:

Add line "host    all             all             172.24.84.43/0
md5" in Section # IPv4 local connections:

And Modification in postgresql.conf:

listen_addresses = '*'

After Restart postgres Cluster, I receive all Minutes Messages like
""2018-07-24 10:46:12.566 CEST [32029] LOG:  invalid length of startup" in
Logfile. But the remote Connection from Host 172.24.84.43 is working as
expected.

If listen_addresses = '*'  change to listen_addresses = 'localhost' and
restart the Postgres Cluster, I  do not receive any further error messages
in logfile. But as expected, the remote connections are not working in this
case.

I've also postgresql version 10 on the same host and can not detect any
issuses when we change listen_adresses = '*'

Thanks a lot for your Investigation and feedback.

With best regards
Stefan


pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #15291: Lateral join has different/suprising semantics (withimpure function)
Next
From: PG Bug reporting form
Date:
Subject: BUG #15293: Stored Procedure Triggered by Logical Replication isUnable to use Notification Events