Re: Re: [BUGS] BUG #13611: test_postmaster_connection failed (Windows, listen_addresses = '0.0.0.0' or '::')
От | Tom Lane |
---|---|
Тема | Re: Re: [BUGS] BUG #13611: test_postmaster_connection failed (Windows, listen_addresses = '0.0.0.0' or '::') |
Дата | |
Msg-id | 53500.1445555710@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Re: [BUGS] BUG #13611: test_postmaster_connection failed (Windows, listen_addresses = '0.0.0.0' or '::') (Tatsuo Ishii <ishii@postgresql.org>) |
Ответы |
Re: Re: [BUGS] BUG #13611: test_postmaster_connection
failed (Windows, listen_addresses = '0.0.0.0' or '::')
Re: Re: [BUGS] BUG #13611: test_postmaster_connection failed (Windows, listen_addresses = '0.0.0.0' or '::') |
Список | pgsql-hackers |
Tatsuo Ishii <ishii@postgresql.org> writes: >> The original post used only "0.0.0.0" and "::", not "localhost" or anything >> else entailing name resolution. As I wrote above, Kondo proposed for pg_ctl >> to use PQping("host='127.0.0.1'") in place of PQping("host='0.0.0.0'"). >> That's all. pg_ctl would continue to use PQping("host='localhost'") where >> it's doing so today. AFAICS, the only hard-wired hostname reference in pg_ctl is "localhost", not "127.0.0.1" (much less "0.0.0.0"). So what you're proposing doesn't seem to me to have anything to do with what's there. I continue to think that the OP's complaint is somehow founded on a bad address obtained by looking up "localhost", because where else would it've come from? regards, tom lane
В списке pgsql-hackers по дате отправления: