Re: duplicate connection failure messages - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: duplicate connection failure messages
Date
Msg-id 201011121402.oACE2e227080@momjian.us
Whole thread Raw
In response to Re: duplicate connection failure messages  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: duplicate connection failure messages
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > I have developed the attached patch to report whether IPv4 or IPv6 are
> > being used.
> 
> What's the use of that exactly?  It doesn't really respond to Peter's
> concern, I think.

Peter liked:

> And I agree it's not very friendly in this specific case - I
> wonder if we should log it as "localhost (127.0.0.1) and "localhost
> (::1)" (and similar for any other case that returns more than one
> address).

What this will show is:
localhost (IPv4)localhost (IPv6)

Is that good?  I can't figure out how to do ::1 because when you supply
a host _name_, there is no reverse mapping done.  Looking at the code,
we test for a host name, then a host ip, and don't assume they are both
set.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: We need index-only scans
Next
From: Bruce Momjian
Date:
Subject: Re: Simplifying replication