openssl @3.2.0: incompatible with psql

[jrabinow]

$ psql service=localdb
psql (16.1)
Type "help" for help.

localhost/localdb=>
\q

$ psql service=remotedb
psql: error: connection to server at "remotedb.rds.amazonaws.com" (10.0.0.1), port 5432 failed: FATAL:  no PostgreSQL user name specified in startup packet
connection to server at "remotedb.rds.amazonaws.com" (10.0.0.1), port 5432 failed: FATAL:  no PostgreSQL user name specified in startup packet
psql(18855,0x1e2cfdec0) malloc: *** error for object 0xa3: pointer being freed was not allocated
psql(18855,0x1e2cfdec0) malloc: *** set a breakpoint in malloc_error_break to debug
Abort trap: 6
[Exit 134 (ABRT)]

I chanced upon ​this stack overflow response and gave reverting [959845548b0dcf19985aeba7bfa1366bc2f4d55e/macports-ports] a shot. Results show that neither psql13 nor psql16 can run with openssl3@3.2.0, while both run fine with openssl3@3.1.4

This might be reported upstream, I'm not sure whether with the openssl or the postgresql folks, but I wanted to open a bug here against openssl3 port since this port update triggered the breakage.

[ryandesign (Ryan Carsten Schmidt)]

Duplicate of #68777.