Re: duplicate connection failure messages

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>

To: Peter Eisentraut <peter_e@gmx.net>

Cc: Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@commandprompt.com>, Magnus Hagander <magnus@hagander.net>, pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2010-11-26T18:27:22Z

Lists: pgsql-hackers

Attachments

/rtmp/diff (text/x-diff) patch

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.

I am finding the sock_addr structures confusing.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

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