From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
Cc: rich.crampton@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16897: gssenc request slow connection
Date: Thu, 25 Feb 2021 14:29:17 -0500
Message-ID: <73903.1614281357@sss.pgh.pa.us> (raw)
In-Reply-To: <20210225174351.GU20766@tamriel.snowman.net>
References: <16897-2632c6541c9f8491@postgresql.org>
<20210225174351.GU20766@tamriel.snowman.net>
Stephen Frost <sfrost@snowman.net> writes:
> What's the version of the libpq library on the client side..? In
> general, while there's an extra packet back and forth because Kerberos /
> GSSAPI is set up on the client / Windows side, once the server says it
> doesn't support GSSENC, libpq should try a non-GSSENC connection right
> away..
I'm wondering if the server DOES say it supports GSSENC, and the delay
is involved in the two sides not realizing they aren't talking to the
same Kerberos/AD servers, or something like that.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, sfrost@snowman.net, rich.crampton@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16897: gssenc request slow connection
In-Reply-To: <73903.1614281357@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox