Kyotaro HORIGUCHI 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 addin
Hello,
At Tue, 04 Feb 2014 02:07:08 -0500, Tom Lane wrote in
<3176.1391497...@sss.pgh.pa.us>
> One good reason not to trust this too much is that getaddrinfo() is
> fundamentally a userspace DNS access function, and as such it has
> no very good way to know if there's currently an IPv4 or IPv6
>
Alvaro Herrera writes:
> Tom Lane wrote:
>> Kyotaro HORIGUCHI writes:
>>> Hello, I have often seen inquiries about an log message from
>>> PostgreSQL server.
>>> LOG: could not create IPv6 socket: Address family not supported by protocol
>> That's merely a harmless log message.
> How about jus
Tom Lane wrote:
> Kyotaro HORIGUCHI writes:
> > Hello, I have often seen inquiries about an log message from
> > PostgreSQL server.
> >> LOG: could not create IPv6 socket: Address family not supported by
> >> protocol
>
> That's merely a harmless log message.
> If we're concerned about users
Kyotaro HORIGUCHI writes:
> Hello, I have often seen inquiries about an log message from
> PostgreSQL server.
>> LOG: could not create IPv6 socket: Address family not supported by protocol
That's merely a harmless log message.
> - hints.ai_flags = AI_PASSIVE;
> + hints.ai_flags = AI_PAS
Hello, I have often seen inquiries about an log message from
PostgreSQL server.
> LOG: could not create IPv6 socket: Address family not supported by protocol
This is emitted on ipv6-disabled environment which was available
for me by the following steps on CentOS 6.5,
- Add 'NETWORKING_IPV6=no'
