| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Creager <Robert_Creager(at)LogicalChaos(dot)org>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: 7.4Beta1 "failed to create socket: Address family not |
| Date: | 2003-08-12 14:07:18 |
| Message-ID: | 200308121407.h7CE7In13810@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Tom Lane wrote:
> >> The real problem is perhaps that the message gives no hint that it's
> >> talking about being unable to establish an IPv6 socket. With that hint,
> >> perhaps people would realize that it's not a problem.
>
> > Not sure who took it out, but it gone. The original message was:
> > elog(LOG, "IPv6 support disabled --- perhaps the kernel does not support IPv6");
>
> That seems both wordy and not necessarily accurate. What I had in mind
> was more like
>
> "could not create IPv6 socket: %m"
>
> But I still wonder whether we shouldn't suppress the message entirely,
> at least for EAFNOSUPPORT errors.
If we suppress it entirely, there is no user-visible report that IPv6
isn't enabled on this computer, though if your kernel doesn't support
it, you would think they would know that, but I suspect many people
don't know it has to be enabled in the kernel --- hence the wording of
the original message.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-08-12 14:12:44 | Re: 7.4Beta1 "failed to create socket: Address family not |
| Previous Message | Vilson farias | 2003-08-12 14:02:22 | Timestamp with zero precision |