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

From Bruce Momjian
Subject Re: duplicate connection failure messages
Date
Msg-id 201011262000.oAQK02D10246@momjian.us
Whole thread Raw
In response to Re: duplicate connection failure messages  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: duplicate connection failure messages
List pgsql-hackers
Peter Eisentraut wrote:
> On fre, 2010-11-26 at 13:27 -0500, Bruce Momjian wrote:
> > Peter Eisentraut wrote:
> > > On fre, 2010-11-26 at 11:53 -0500, Bruce Momjian wrote:
> > > > OK, I updated the code to always use cur_addr in the code --- let me
> > > > know if that doesn't fix it.
> > > 
> > > Now it's even more wrong:
> > > 
> > > psql: could not connect to server: Connection refused
> > >         Is the server running on host "localhost" (???) and accepting
> > >         TCP/IP connections on port 55555?
> > > could not connect to server: Connection refused
> > >         Is the server running on host "localhost" (232.106.56.8) and accepting
> > >         TCP/IP connections on port 55555?
> > 
> > Yep, even worse.  I have applied the attached patch, which gives me the
> > right IPv4 value.  I can't test IPv6.
> 
> We're back to
> 
> psql: could not connect to server: Connection refused
>         Is the server running on host "localhost" (???) and accepting
>         TCP/IP connections on port 55555?
> could not connect to server: Connection refused
>         Is the server running on host "localhost" (127.0.0.1) and accepting
>         TCP/IP connections on port 55555?

OK, good.  :-O  I just realize I can easily test this on Ubuntu so let
me get that working now.

--  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: Alvaro Herrera
Date:
Subject: Re: memory leak in libxml2 - fix
Next
From: Tom Lane
Date:
Subject: Re: memory leak in libxml2 - fix