From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter <pmc(at)citylink(dot)dinoex(dot)sub(dot)org> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Stephen Frost <sfrost(at)snowman(dot)net> |
Subject: | Re: 12.1 not useable: clientlib fails after a dozen queries (GSSAPI ?) |
Date: | 2020-01-11 20:37:43 |
Message-ID: | 1473.1578775063@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
I wrote:
> So last night I was assuming that this problem just requires more careful
> attention to what to return in the error exit paths. In the light of
> morning, though, I realize that the algorithms involved in
> be-secure-gssapi.c and fe-secure-gssapi.c are just fundamentally wrong:
Here's a revised patch that attempts to deal with those issues.
(Still doesn't touch the static-buffer issue, though.)
The 0002 patch isn't meant for commit, but testing with that gives me
a whole lot more confidence that the gssapi code deals with EWOULDBLOCK
correctly.
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
0001-fix-assorted-gssapi-bugs-2.patch | text/x-diff | 48.2 KB |
0002-debug-support.patch | text/x-diff | 1004 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-01-11 21:42:31 | Re: 12.1 not useable: clientlib fails after a dozen queries (GSSAPI ?) |
Previous Message | Tom Lane | 2020-01-11 15:28:15 | Re: 12.1 not useable: clientlib fails after a dozen queries (GSSAPI ?) |
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2020-01-11 21:10:56 | Re: Avoid full GIN index scan when possible |
Previous Message | Pavel Stehule | 2020-01-11 20:27:19 | Re: [Proposal] Global temporary tables |