| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #6687: initdb -A ident can almost never be correct |
| Date: | 2012-06-11 22:27:44 |
| Message-ID: | 20979.1339453664@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
David Fetter <david(at)fetter(dot)org> writes:
> Interface wouldn't change. Instead, it would check for your
> once-in-a-blue-moon scenario of identd answering on the network and
> error out if it didn't fine same.
This is nonsense. As Magnus said, localhost is the one case where
identd *can* be trusted. There is no reason that we should discriminate
against that case.
It also does not seem to me like a good plan to insist that identd be
running at the same instant initdb runs; it's not hard to think of
installation scenarios where that won't be true.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-06-12 02:23:00 | Re: 9.2 beta2 - pg_ctl crashes on Win32 when neither PGDATA nor -D specified |
| Previous Message | Kris Jurka | 2012-06-11 21:28:07 | Re: JDBC Driver can't read UUID from database |