From: | kondo(at)sraoss(dot)co(dot)jp |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #13611: test_postmaster_connection failed (Windows, listen_addresses = '0.0.0.0' or '::') |
Date: | 2015-09-10 04:15:18 |
Message-ID: | 20150910041518.635.87615@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
The following bug has been logged on the website:
Bug reference: 13611
Logged by: Kondo Yuta
Email address: kondo(at)sraoss(dot)co(dot)jp
PostgreSQL version: 9.4.4
Operating system: Windows 7
Description:
Hello,
According to PostgreSQL document, listen_addresses = '0.0.0.0' or '::' are
allowed.
http://www.postgresql.org/docs/9.4/static/runtime-config-connection.html#GUC-LISTEN-ADDRESSES
But I found "pg_ctl -w ..." timeouts connection test on Windows with
listen_addresses = '0.0.0.0' or '::'.
I found this reason in src/bin/pg_ctl/pg_ctl.c
[test_postmaster_connection(bool)].
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?
From | Date | Subject | |
---|---|---|---|
Next Message | allan.kristsensen | 2015-09-10 08:13:12 | BUG #13612: postgresql94-setup initdb in kickstart fails |
Previous Message | Fujii Masao | 2015-09-09 14:11:43 | Re: BUG #13368: standby cluster immediately promotes after pg_basebackup from previously promoted master |
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2015-09-10 04:26:58 | Re: Re: [COMMITTERS] pgsql: Map basebackup tablespaces using a tablespace_map file |
Previous Message | Amit Kapila | 2015-09-10 04:12:43 | Re: Parallel Seq Scan |