Re: duplicate connection failure messages

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: duplicate connection failure messages
Дата
Msg-id 1290780384.5294.3.camel@fsopti579.F-Secure.com
обсуждение исходный текст
Ответ на Re: duplicate connection failure messages  (Bruce Momjian <bruce@momjian.us>)
Ответы Re: duplicate connection failure messages  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: duplicate connection failure messages  (Bruce Momjian <bruce@momjian.us>)
Список pgsql-hackers
On lör, 2010-11-20 at 18:07 -0500, Bruce Momjian wrote:
> The output is as expected:
> 
>     $ psql -h localhost test
>     psql: 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 5432?
>     $ psql -h 127.0.0.1 test
>     psql: could not connect to server: Connection refused
>             Is the server running on host "127.0.0.1" and accepting
>             TCP/IP connections on port 5432?

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?
 
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?
 

The "???" should presumably be "::1".

Also, this comment should be updated:
   /*    * Try to initiate a connection to one of the addresses    * returned by pg_getaddrinfo_all().  conn->addr_cur
isthe    * next one to try. We fail when we run out of addresses    * (reporting the error returned for the *last*
alternative,   * which may not be what users expect :-().    */
 




В списке pgsql-hackers по дате отправления:

Предыдущее
От: Florian Pflug
Дата:
Сообщение: Re: improving foreign key locks
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: duplicate connection failure messages