> 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.
Are you saying that "listen_addresses = '0.0.0.0' should work on Windows?
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp