Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
> I propose the attached patch to shake up the wording in the connection
> type section of pg_hba.conf.sample a bit. After the hostgssenc part was
> added on, the whole thing became a bit wordy, and it's also a bit
> inaccurate for example in that the current wording for "host" appears to
> say that it does not apply to GSS-encrypted connections.
+1 for revising it in this general way. I notice you omitted "TCP/IP"
from the last line though:
+# - "hostnogssenc" is a not GSSAPI-encrypted socket
which doesn't seem consistent.
Another thought is to switch the phrase order:
+# - "local" is a Unix-domain socket
+# - "host" is a TCP/IP socket (encrypted or not)
+# - "hostssl" is a TCP/IP socket that is SSL-encrypted
+# - "hostnossl" is a TCP/IP socket that is not SSL-encrypted
+# - "hostgssenc" is a TCP/IP socket that is GSSAPI-encrypted
+# - "hostnogssenc" is a TCP/IP socket that is not GSSAPI-encrypted
I'm not wedded to that idea, but it seems to help reduce random
variations between the wordings of these lines.
regards, tom lane