From: | Benoit Lobréau <benoit(dot)lobreau(at)gmail(dot)com> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | recovery_target_timeline & documentation |
Date: | 2021-01-05 11:18:10 |
Message-ID: | CAPE8EZ7c3aruEmM24GYkj8y8WmHKD1m9TtPtgCF0nQ3zw4LCkQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
It seems like this part of the documentation was not updated after changing
the default value of recovery_target_timeline to latest in v12.
"The default behavior of recovery is to recover along the same timeline
that was current when the base backup was taken. If you wish to recover
into some child timeline (that is, you want to return to some state that
was itself generated after a recovery attempt), you need to specify the
target timeline ID in recovery_target_timeline
<https://www.postgresql.org/docs/13/runtime-config-wal.html#GUC-RECOVERY-TARGET-TIMELINE>.
You cannot recover into timelines that branched off earlier than the base
backup." [1][2]
Here is an attempt to fix that.
regards,
Benoit
[1]
https://www.postgresql.org/docs/13/continuous-archiving.html#BACKUP-TIMELINES
[2]
https://www.postgresql.org/docs/12/continuous-archiving.html#BACKUP-TIMELINES
Attachment | Content-Type | Size |
---|---|---|
0001-Fix-recovery_target_timeline-default-in-backup.sgml.patch | text/x-patch | 1.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Victor Yegorov | 2021-01-05 11:26:47 | Re: Deadlock between backend and recovery may not be detected |
Previous Message | Luc Vlaming | 2021-01-05 11:02:03 | Re: Parallel Inserts in CREATE TABLE AS |