Add recovery_end_command option to recovery.conf. recovery_end_command
authorHeikki Linnakangas <heikki@enterprisedb.com>
Thu, 14 May 2009 20:31:09 +0000 (20:31 +0000)
committerHeikki Linnakangas <heikki@enterprisedb.com>
Thu, 14 May 2009 20:31:09 +0000 (20:31 +0000)
commitc516496ec3df7d64b27af2ea3d7773205106769c
treec3b5740d1421104933d8d6034c30cae20ba6bbab
parent100982fdc9926f8b2748520a549849f6c88563fd
Add recovery_end_command option to recovery.conf. recovery_end_command
is run at the end of archive recovery, providing a chance to do external
cleanup. Modify pg_standby so that it no longer removes the trigger file,
that is to be done using the recovery_end_command now.

Provide a "smart" failover mode in pg_standby, where we don't fail over
immediately, but only after recovering all unapplied WAL from the archive.
That gives you zero data loss assuming all WAL was archived before
failover, which is what most users of pg_standby actually want.

recovery_end_command by Simon Riggs, pg_standby changes by Fujii Masao and
myself.
contrib/pg_standby/pg_standby.c
doc/src/sgml/backup.sgml
doc/src/sgml/pgstandby.sgml
src/backend/access/transam/xlog.c