Menu

#90 Unintentional database erase in setting non-existing value to recovery-target-timeline

Fixed
None
Medium
Improvement
2014-10-31
2014-10-22
No

Setting non-existing value in recovery-target-timeline option, pg_rman restore fails with error.

$ pg_rman -B /home/postgres/pg_data/backup/ -A /home/postgres/pg_data/archive/ restore --recovery-target-timeline 39
ERROR: no full backup found, can't restore.

Though restore failed, the restore destination, that is an original database cluster was erased by pg_rman.

This is because the check of existence of full backcup which can be used as base backup for specified timeline is done after deletion of restore destination.

I think this check should be done before deletion of restore destination.

Discussion

  • Takashi Ohnishi

    Takashi Ohnishi - 2014-10-22

    Attached a patch created by Amit Langote.

     
  • Takashi Ohnishi

    Takashi Ohnishi - 2014-10-31

    I have committed.

     
  • Takashi Ohnishi

    Takashi Ohnishi - 2014-10-31
    • status: New --> Fixed
     

Log in to post a comment.