Re: duplicate connection failure messages
От | Bruce Momjian |
---|---|
Тема | Re: duplicate connection failure messages |
Дата | |
Msg-id | 201011202043.oAKKhTs01861@momjian.us обсуждение исходный текст |
Ответ на | Re: duplicate connection failure messages (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: duplicate connection failure messages
|
Список | pgsql-hackers |
Tom Lane wrote: > Bruce Momjian <bruce@momjian.us> writes: > > I was wondering that. I am unclear if we need it though --- can we not > > assume inet_ntop() exists on all systems? We assumed inet_ntoa() did. > > The Single Unix Spec includes inet_ntoa but not inet_ntop. > > > Of course, the buildfarm will tell us. > > The buildfarm unfortunately contains only a subset of the platforms > we care about. I don't think this problem is large enough to justify > taking a portability risk by depending on non-SUS library functions. > > If you want to do this, please do it as suggested previously, ie depend > on the copy of the code we have internally. I assume you are suggesting to use our inet_net_ntop() even if the system has inet_ntop(). -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
В списке pgsql-hackers по дате отправления: