Re: duplicate connection failure messages
| От | Bruce Momjian |
|---|---|
| Тема | Re: duplicate connection failure messages |
| Дата | |
| Msg-id | 201011190317.oAJ3HxP12938@momjian.us обсуждение исходный текст |
| Ответ на | Re: duplicate connection failure messages (Alvaro Herrera <alvherre@commandprompt.com>) |
| Ответы |
Re: duplicate connection failure messages
|
| Список | pgsql-hackers |
Alvaro Herrera wrote: > Excerpts from Bruce Momjian's message of mié nov 17 13:04:46 -0300 2010: > > > OK, I doubt we want to add complexity to improve this, so I see our > > options as: > > > > o ignore the problem > > o display IPv4/IPv6 labels > > o display only an IPv6 label > > o something else > > 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. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
В списке pgsql-hackers по дате отправления: