| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 03:17:59 |
| Message-ID: | 201011190317.oAJ3HxP12938@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2010-11-19 03:21:12 | Re: duplicate connection failure messages |
| Previous Message | Greg Smith | 2010-11-19 02:43:03 | Changes to Linux OOM killer in 2.6.36 |