| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | Benoit Lobréau <benoit(dot)lobreau(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: recovery_target_timeline & documentation |
| Date: | 2021-01-06 03:03:29 |
| Message-ID: | 9c429896-a523-32aa-5c46-fdae54029726@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2021/01/06 3:01, Fujii Masao wrote:
>
>
> On 2021/01/05 20:18, Benoit Lobréau wrote:
>> 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.
>
> Thanks for the patch! This looks good to me. Barring any objection, I will commit it.
Pushed. Thanks!
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2021-01-06 03:10:01 | Re: Single transaction in the tablesync worker? |
| Previous Message | Zhihong Yu | 2021-01-06 02:50:51 | Re: Parallel Inserts in CREATE TABLE AS |