Hi,
I have encountered a strange pg_ctl's behavior in 8.3.
pg_ctl -w -o -p 5432 start-- works
pg_ctl -w -o -i start -- works
pg_ctl -w -o -p 5432 -i start -- doesn't work
In the last case, even postmaster starts successfully, pg_ctl keeps
trying to make sure that postmaster actually started
Tatsuo Ishii wrote:
Hi,
I have encountered a strange pg_ctl's behavior in 8.3.
pg_ctl -w -o -p 5432 start -- works
pg_ctl -w -o -i start -- works
pg_ctl -w -o -p 5432 -i start -- doesn't work
In the last case, even postmaster starts successfully, pg_ctl keeps
trying to make sure
Tatsuo Ishii wrote:
Hi,
I have encountered a strange pg_ctl's behavior in 8.3.
pg_ctl -w -o -p 5432 start-- works
pg_ctl -w -o -i start -- works
pg_ctl -w -o -p 5432 -i start -- doesn't work
In the last case, even postmaster starts successfully, pg_ctl keeps
Richard Huxton wrote:
Tatsuo Ishii wrote:
Hi,
I have encountered a strange pg_ctl's behavior in 8.3.
pg_ctl -w -o -p 5432 start-- works
pg_ctl -w -o -i start-- works
pg_ctl -w -o -p 5432 -i start-- doesn't work
In the last case, even postmaster starts successfully, pg_ctl keeps
Richard Huxton wrote:
Hmm - that does seem to be the case. I added a line to print connstr
along with the .
waiting for server to startdbname=postgres port=5483 -i
connect_timeout=5.
The code looks fine to my uneducated eye though (bin/pg_ctl/pg_ctl.c
test_postmaster_connection
Richard Huxton wrote:
Richard Huxton wrote:
Hmm - that does seem to be the case. I added a line to print connstr
along with the .
waiting for server to startdbname=postgres port=5483 -i
connect_timeout=5.
The code looks fine to my uneducated eye though
Line 52:
#define WHITESPACE \f\n\r\t\v /* as defined by isspace() */
We've defined whitespace as not including a space character :-/
Yes, we fixed this on February 20 and the fix will appear in 8.3.1 and
all back brances once a release is made.
Thanks. I should have checked the CVS
