When port databases/postgresql1[234]-client is configured with OPTION GSSAPI set to true and compiled, on platforms 13.0-RELENG, 13-STABLE and 14-CURRENT (tested myself, dis not test on any 12), no "remote" connection (via TCP) can be made, the psql client just times out.

I've tested this misbehaviour so far with bot server and client on the same host and with our department installation which is remote server/client installation with PostgreSQL 12, 13 14 on the above mentioned FreeBSD platforms.

When trying to connect to the local db server via "psql -U postgres -d postgres -h localhost" (alternatively replaced "-h localhost" by "-h 127.0.0.1" or "-h ::1"), connection is not possible, the client simply times out. The same is from a remote host where I have to provide the target host via -h option either as its DNS name, its IPv4 or IPv6. Any connection via the local socket (ommiting -h on the local host) works.

It took me a time to figure out that enabling GSSAPI on the client and not having any valif GSSAPI configuration provided, results in some mysterious segmentation faults on server side when checking the postgresql logs.