Daniel Gustafsson <dan...@yesql.se> writes:
> I took another look at this tonight and committed it with some mostly cosmetic
> changes. Since then, tamandua failed the SSL test on this commit but I am
> unable to reproduce any error both on older OpenSSL and matching the 3.1
> version on tamandua, so not sure if its related.
That failure looks like just a random buildfarm burp:
2024-03-17 23:11:30.989 UTC [106988][postmaster][:0] LOG: starting PostgreSQL
17devel on x86_64-linux, compiled by gcc-12.3.0, 64-bit
2024-03-17 23:11:30.989 UTC [106988][postmaster][:0] LOG: could not bind IPv4
address "127.0.0.1": Address already in use
2024-03-17 23:11:30.989 UTC [106988][postmaster][:0] HINT: Is another
postmaster already running on port 54588? If not, wait a few seconds and retry.
2024-03-17 23:11:30.990 UTC [106988][postmaster][:0] WARNING: could not create
listen socket for "127.0.0.1"
2024-03-17 23:11:30.990 UTC [106988][postmaster][:0] FATAL: could not create
any TCP/IP sockets
2024-03-17 23:11:30.993 UTC [106988][postmaster][:0] LOG: database system is
shut down
regards, tom lane
