From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | rich(dot)crampton(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #16897: gssenc request slow connection |
Date: | 2021-02-25 17:43:51 |
Message-ID: | 20210225174351.GU20766@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Greetings,
* PG Bug reporting form (noreply(at)postgresql(dot)org) wrote:
> Email address: rich(dot)crampton(at)gmail(dot)com
> PostgreSQL version: 12.6
> Operating system: client Windows 10, postgresql server Ubuntu
> Description:
>
> When connecting over a local network from Windows 10 to PostgreSQL server
> (Linux version 12.6 default install) the gssencmode=prefer in libpq
> connection causes a big slowdown.
>
> With "gssencmode=prefer" connection takes 4 seconds.
> With "gssencmode=disable" connection as fast as normal.
>
> As the prefer option is the default option this causes problems in dependent
> libraries such as psycopg2 for Python. First raised the bug here
> https://github.com/psycopg/psycopg2/issues/1242 but I think this must be a
> libpq/Postgresql bug since psycopg2 is just passing along the request.
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..
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | David Steele | 2021-02-25 17:53:44 | Re: BUG #16894: PANIC: WAL contains references to invalid pages |
Previous Message | Tom Lane | 2021-02-25 15:19:43 | Re: BUG #16801: Invalid memory access on WITH RECURSIVE with nested WITHs |