| From: | "Efrain J(dot) Berdecia" <ejberdecia(at)yahoo(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: New recovery_target_timeline=primary option |
| Date: | 2025-09-12 00:55:48 |
| Message-ID: | 1173640045.2783735.1757638548616@mail.yahoo.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
This option would only be applicable when the standby.signal file is used only for restoring a cluster for the purposes of establishing a standby replica.
Yahoo Mail: Search, Organize, Conquer
On Thu, Sep 11, 2025 at 8:50 PM, Euler Taveira<euler(at)eulerto(dot)com> wrote: On Thu, Sep 11, 2025, at 9:17 PM, Efrain J. Berdecia wrote:
> *One-line Summary:* This new recovery_target_timeline option would
> ensure that when rebuilding a replica cluster, the recovery stays in
> the primary cluster's timeline making it fool proof and avoiding
> recovery timeline inconsistencies.
>
Do you understand what the timeline is for? [1] You are proposing to implement
exactly what it is protecting you from: overwrite previous archived WAL after a
recovery.
[1] https://www.postgresql.org/docs/current/continuous-archiving.html#BACKUP-TIMELINES
--
Euler Taveira
EDB https://www.enterprisedb.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2025-09-12 01:05:20 | Re: New recovery_target_timeline=primary option |
| Previous Message | Euler Taveira | 2025-09-12 00:49:50 | Re: New recovery_target_timeline=primary option |