Re: Direct SSL connection and ALPN loose ends

I reviewed the documentation for "direct ALPN connections' ', and it looks like it could be improved.

Here's the link: https://www.postgresql.org/docs/17/protocol-flow.html#PROTOCOL-FLOW-SSL

The currently suggested values for "sslnegotiations" are "direct" and "postgres".

The project name is PostgreSQL and the ALPN name is postgresql. Is there a reason why property value uses "postgres"?

Can the value be renamed to postgresql for consistency?

"SSL". Technically, the proper term is TLS, and even the document refers to "IANA TLS ALPN Protocol IDs" (TLS, not SSL).

I would not die on that hill, however, going for tlsnegotiation would look better than sslnegotiation.