Re: duplicate connection failure messages

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: duplicate connection failure messages
Дата
Msg-id 201011191943.oAJJhXc17187@momjian.us
обсуждение исходный текст
Ответ на Re: duplicate connection failure messages  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: duplicate connection failure messages  (Alvaro Herrera <alvherre@commandprompt.com>)
Список pgsql-hackers
Tom Lane wrote:
> 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

Yeah, that is nice, but we are calling this from libpq, not the backend.
Let me work up a patch.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: Latches with weak memory ordering (Re: max_wal_senders must die)
Следующее
От: Dimitri Fontaine
Дата:
Сообщение: Re: directory archive format for pg_dump