| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, 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 14:52:30 |
| Message-ID: | 1290783063-sup-8271@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2010-11-26 15:25:01 | Re: Workarounds for getBinaryStream returning ByteArrayInputStream on bytea |
| Previous Message | Peter Eisentraut | 2010-11-26 14:06:24 | Re: duplicate connection failure messages |