On 1/15/17 11:40 PM, Fujii Masao wrote: > This change may confuse the users who run "pg_ctl start" to perform a crash > recovery, archive recovery and standby server (with hot_standby=off) because > "pg_ctl start" would not return so long time.
Well, this change was made because the previous behavior confused people as well, because pg_ctl would return before it was actually done. The new state shouldn't be confusing because pg_ctl prints out progress messages. > Also during that long time, > the error message "FATAL: the database system is starting up" keeps > outputing. We could potentially avoid some of this by using the new facilities in pg_ctl to read pg_control and not use PQping() before the state is out of DB_IN_CRASH_RECOVERY. Note, however, that this isn't a new problem. The way pg_ctl start -w is implemented hasn't changed. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
