Re: duplicate connection failure messages

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-18 15:07:49
Message-ID: 1290092783-sup-68@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2010-11-18 15:24:34 Re: final patch - plpgsql: for-in-array
Previous Message Pavel Stehule 2010-11-18 13:43:22 Re: final patch - plpgsql: for-in-array