Re: duplicate connection failure messages

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-17 16:04:46
Message-ID: 201011171604.oAHG4kE23254@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 sb nov 13 22:36:31 -0300 2010:
>
> > OK, I found out how to get the IP address with the attached patch. The
> > problem is that only pghost is set, never pghostaddr. I am not even
> > sure how that would get set for this code because my tests show it is
> > not:
>
> This doesn't work for IPv6 addresses, though.
>
> pghostaddr is specified by the user on the command line as an
> optimization to avoid DNS lookups IIRC, which is why you don't see the
> code setting it.

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

Comments?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2010-11-17 16:05:08 Re: Indent authentication overloading
Previous Message Greg Stark 2010-11-17 16:00:46 Re: unlogged tables