From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
Cc: | alvherre(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: could not create IPv6 socket (AI_ADDRCONFIG) |
Date: | 2014-02-05 03:27:29 |
Message-ID: | 4889.1391570849@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> writes:
> getaddrinfo returned two same entries having the same address
> AF_INET "127.0.0.1:14357". One of them is for "::1" in
> hosts. This is worse than current behavior X-(
Yeah, the fundamental issue is that getaddrinfo tends to return bogus
info.
>>> How about just adding a HINT?
>> Hmm ... maybe, but how would you phrase the hint exactly?
> Putting the 'exactly' aside, is it something means 'You will get
> this message when the feature to handle the address family is
> disabled', only for EAFNOSUPPORT ?
> Though I don't know whether such a hint is helpful for those who
> tend to mind that kind of message.
I still think the best thing might be to reduce the individual messages
to DEBUG-something, and only produce a LOG entry if we are unable to
bind to *any* of the addresses returned by getaddrinfo.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2014-02-05 03:48:38 | Re: narwhal and PGDLLIMPORT |
Previous Message | Kyotaro HORIGUCHI | 2014-02-05 03:11:39 | Re: could not create IPv6 socket (AI_ADDRCONFIG) |