From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: duplicate connection failure messages |
Date: | 2010-11-26 16:53:59 |
Message-ID: | 201011261653.oAQGrxw15870@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> Excerpts from Peter Eisentraut's message of vie nov 26 11:06:24 -0300 2010:
>
> > Thanks for working on this. However, the example I posted at the
> > beginning of this thread now does this:
> >
> > $ ./psql -p 55555 -h localhost
> > psql: could not connect to server: Connection refused
> > Is the server running on host "localhost" (???) and accepting
> > TCP/IP connections on port 55555?
>
> Shouldn't connectFailureMessage receive addr_cur as parameter?
> Otherwise it's not clear that it's getting the right params to report.
I am passing conn so I changed the code to always use addr_cur.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2010-11-26 17:25:44 | Re: Instrument checkpoint sync calls |
Previous Message | Bruce Momjian | 2010-11-26 16:53:23 | Re: duplicate connection failure messages |