| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| 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 15:22:31 |
| Message-ID: | 1290180016-sup-2630@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Bruce Momjian's message of vie nov 19 00:17:59 -0300 2010:
> 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.
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
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-11-19 15:25:13 | Re: libpq changes for synchronous replication |
| Previous Message | Markus Wanner | 2010-11-19 15:12:26 | Re: Latches with weak memory ordering (Re: max_wal_senders must die) |