From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | pramod kg <pramod11287(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Kellerer <shammat(at)gmx(dot)net>, pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: PostgreSQL local connection is taking 4 seconds |
Date: | 2024-01-03 17:59:49 |
Message-ID: | CAMkU=1zgzHj+YHiOt=xPi6Mfoq52op=5MAq=5KR5hDz8fQVO5Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Wed, Jan 3, 2024 at 2:05 AM pramod kg <pramod11287(at)gmail(dot)com> wrote:
> We have made some progress. GSSAPI authentication method is taking time
> though we have not enabled the GSSAPI authentication method in postgres
> (but the connection request is spending some time there).
>
When a libpq client sees that krb5 credentials exist, it tries to use them
preemptively, without knowing if the server supports them or not. Once
given an error, it then tries again without GSS. The server log file
should show evidence of these failed connections, and the failure reason
given might offer some clues.
But this first try should normally be fast. Is the time taken on the client
side, or on the server side? Using strace on a simple psql invocation
would be the best way to answer this (on Linux). If the server doesn't
support GSS at all, it is hard to see why it should fail slowly on the
server side so that would probably be a bug.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2024-01-03 18:36:48 | Re: Vacuum |
Previous Message | Tom Lane | 2024-01-03 15:56:00 | Re: PostgreSQL local connection is taking 4 seconds |