| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Occupied port warning |
| Date: | 2005-06-28 14:10:07 |
| Message-ID: | 200506281610.08353.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> Andrew Dunstan wrote:
> > see
> > http://archives.postgresql.org/pgsql-hackers/2004-03/msg00679.php
>
> Well, with once release of field experience behind me I'd like to
> revisit this idea. Who would actually be hurt by generating an error
> here like it used to do?
It seems that the only concern was broken resolvers (namely, "localhost"
not being resolvable). Then you can easily replace that with
127.0.0.1, or * if you like. That sounds like the place for an error
message with a hint, not silent failure. Comments?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2005-06-28 14:16:06 | initdb -W failure with role-capable catalogs |
| Previous Message | Peter Eisentraut | 2005-06-28 14:04:58 | Re: Occupied port warning |