Open gsmolk opened 4 years ago
Please, add "latest" as a valid argument for --recovery-target-timeline parameter. Very needed for restore DB to restore point from latest timeline with no additional arithmetic. "latest" as a valid argument for recovery_target_timeline parameter in postgresql
"latest" as a valid argument for recovery_target_timeline parameter in postgresql
It is. But looks like recovery_target_timeline is meaningless without other recovery-target options. Isn't it?
If you have only full backup, and restore database more than one times from it, and create restore point with unique name in the latest timeline, then when you restore database from full backup the timeline would be current of the full backup (not latest) and postgresql does not found your restore point in current timeline WALs.
This is the problem.
At now I must replace parameter recovery_target_timeline='current' to recovery_target_timeline='latest' in postgresql.auto.conf before start postgresql server. Otherwise recovery process cannot found my restore point in WALs of current timeline (sets by timeline of a full backup) because are in latest timeline.
"latest" is a valid argument for
--recovery-target-timeline
parameter.