I'll rename it to PG_MAX_AUTH_TOKEN_LENGTH, unless someone has a better
suggestion.
If we are not changing this for all authentication schemes, then the name
should probably reflect that this is for GSS and SSPI only (not even KRB5).
--Ian
--
Sent via pgsql-bugs mailing list
The original naming complaint reflected a concern that
the symbol looked like it was supplied by the system headers, rather
than being of Postgres origin. Heikki's suggestion deals with that,
and I think it's fine as-is.
OK, fine with me.
--Ian
--
Sent via pgsql-bugs mailing list
Tom Lane:
I'd be inclined to just s/2000/32767/ and not bother with a symbol,
Heikki Linnakangas:
The corresponding limit in pg_SSPI_recvauth() probably needs to be
raised too..
Magnus Hagander:
Actually, I found a note that said it's recommended to never increase
it [above] 65535 - so
Hello pgsql-bugs,
While trying to connect our PostgreSQL database to our Kerberos realm, we
encountered the obscure message Invalid message length. Tracking this down,
we discovered that it was emitted by src/backend/libpq/pqcomm.c in response to
a rather large Kerberos message. The root cause
