Re: duplicate connection failure messages - Mailing list pgsql-hackers

From Tom Lane
Subject Re: duplicate connection failure messages
Date
Msg-id 318.1290182283@sss.pgh.pa.us
Whole thread Raw
In response to Re: duplicate connection failure messages  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: duplicate connection failure messages
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Excerpts from Bruce Momjian's message of vie nov 19 00:17:59 -0300 2010:
>> Alvaro Herrera wrote:
>>> I think we should use inet_ntop where available to print the address.
>> 
>> Good idea because inet_ntop() is thread-safe.  Does that work on IPv6? 
>> You indicated that inet_ntoa() does not.

> According to opengroup.org, IPv6 should work if the underlying libraries
> support it, whereas inet_ntoa explicitely does not.
> http://www.opengroup.org/onlinepubs/009695399/functions/inet_ntop.html
> http://www.opengroup.org/onlinepubs/009695399/functions/inet_addr.html

I get the impression that you guys have forgotten the existence of
src/backend/utils/adt/inet_net_ntop.c
        regards, tom lane


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: final patch - plpgsql: for-in-array
Next
From: Markus Wanner
Date:
Subject: Re: Latches with weak memory ordering (Re: max_wal_senders must die)