Re: New recovery_target_timeline=primary option

From: "Euler Taveira" <euler(at)eulerto(dot)com>
To: "Efrain J(dot) Berdecia" <ejberdecia(at)yahoo(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: New recovery_target_timeline=primary option
Date: 2025-09-12 00:49:50
Message-ID: 7d3d643b-a685-4b87-8dd4-6f235bc4d023@app.fastmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Efrain J. Berdecia 2025-09-12 00:55:48 Re: New recovery_target_timeline=primary option
Previous Message Michael Paquier 2025-09-12 00:49:18 Re: PgStat_HashKey padding issue when passed by reference