| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: duplicate connection failure messages |
| Date: | 2010-11-19 15:58:03 |
| Message-ID: | 318.1290182283@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Wanner | 2010-11-19 16:14:55 | Re: Latches with weak memory ordering (Re: max_wal_senders must die) |
| Previous Message | Tom Lane | 2010-11-19 15:51:00 | Re: Latches with weak memory ordering (Re: max_wal_senders must die) |