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 | 11077.1442205374@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | 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: [BUGS] BUG #13611: test_postmaster_connection failed (Windows, listen_addresses = '0.0.0.0' or '::') |
Список | pgsql-hackers |
Tatsuo Ishii <ishii@postgresql.org> writes: >> When pg_ctl tries to connect to postmaster, it uses "0.0.0.0" as the >> target ip address. Unfortunately "0.0.0.0" is not a valid address on >> Windows and it fails. Shouldn't pg_ctl translate "0.0.0.0" to >> "127.0.0.1" in this case? > I think this is definitely a bug. I privately heard from the reporter > that if postmaster is started by not using pg_ctl, it happily starts > with "listen_addresses = '0.0.0.0'. That means, postmaster itself > works as advertised, but pg_ctl does not. I looked at this before, and could not see anything in either the postmaster or pg_ctl that would invent the address 0.0.0.0 out of thin air. I think this report most likely depends on some misconfiguration of the OP's system. I doubt it should be our business to work around such misconfiguration. In particular, magically substituting 127.0.0.1 for 0.0.0.0 seems utterly without principle. regards, tom lane
В списке pgsql-hackers по дате отправления: