On Tue, Jan 17, 2017 at 11:27 AM, Peter Eisentraut <peter.eisentr...@2ndquadrant.com> wrote: > 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.
But what if we're restarting after, say, rebooting? Then there's nobody to see the progress messages, perhaps. The system just seems to take an eternity to return to the usual runlevel. I saw the discussion on this thread, but I didn't realize that it meant that pg_ctl was going to wait for crash recovery, let alone archive recovery. That seems not good. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
