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

From Peter Eisentraut
Subject Re: duplicate connection failure messages
Date
Msg-id 1290801264.12170.2.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: duplicate connection failure messages  (Bruce Momjian <bruce@momjian.us>)
Responses Re: duplicate connection failure messages
List pgsql-hackers
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?
 




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running
Next
From: Alvaro Herrera
Date:
Subject: Re: memory leak in libxml2 - fix