On Sat, May 15, 2010 at 3:20 AM, Robert Haas <robertmh...@gmail.com> wrote: > Hmm, OK, I think that makes sense. Would you care to propose a patch?
Yep. Here is the patch.
This patch distinguishes normal shutdown from unexpected exit, while the
server is in recovery. That is, when smart or fast shutdown is requested
during recovery, the bgwriter sets the ControlFile->state to new-introduced
DB_SHUTDOWNED_IN_RECOVERY state.
When recovery starts from the DB_SHUTDOWNED_IN_RECOVERY state, the startup
process emits
LOG: database system was shut down in recovery at 2010-05-12 20:35:24 EDT
instead of
LOG: database system was interrupted while in recovery at log
time 2010-05-12 20:35:24 EDT
HINT: If this has occurred more than once some data might be
corrupted and you might need to choose an earlier recovery target.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
db_state_for_shutdown_in_recovery_v1.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
