| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Open item: kerberos warning message |
| Date: | 2009-01-08 15:49:20 |
| Message-ID: | 16264.1231429760@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> The reason this is happening is that we are initializing Kerberos even
> if we're not going to use it. The reason for doing *this*, is that if
> kerberos is compiled in, we use it to find out if we should try a
> different username than the one logged in to the local system - we look
> at the kerberos login.
> We don't do this for any other login, including kerberos over GSSAPI.
> AFAIK, we've heard no complaints.
> I see two ways to fix this, and have attached two patches:
> 1) Remove the support for getting this username. AFAIK, it's not even
> documented. [krberror_remove.patch]
+1 for this approach.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2009-01-08 15:49:35 | Re: WITH RECURSIVE ... CYCLE in vanilla SQL: issues with arrays of rows |
| Previous Message | David Fetter | 2009-01-08 15:46:19 | Re: about truncate |