| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Krb5 & multiple DB connections |
| Date: | 2006-02-09 03:14:44 |
| Message-ID: | 23954.1139454884@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
>> I have little idea of how expensive the operations called by
>> pg_krb5_init really are. If they are expensive then it'd probably
>> make sense to keep the current static variables but treat 'em as a
>> one-element cache, ie, recompute if a new user name is being demanded.
>> If not, we ought to be able to simplify some things.
> We'd have to recompute based on the KRB5CCNAME environment variable
> changing, which is certainly an option. It's not necessairly the case
> that the username is changing, possibly just the cache.
Hm, apparently I completely misunderstand the problem here. What I
thought the bug was was that the cache wasn't recomputed given an
attempt to connect as a different Postgres username than the first
time. If that's not the issue, then what is?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-02-09 03:45:26 | Re: Upcoming re-releases |
| Previous Message | Stephen Frost | 2006-02-09 03:03:34 | Re: [HACKERS] Krb5 & multiple DB connections |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-02-09 03:41:44 | Re: [PATCHES] date overflows |
| Previous Message | Stephen Frost | 2006-02-09 03:03:34 | Re: [HACKERS] Krb5 & multiple DB connections |