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 01:19:18
Message-ID: 741bf468-aa4e-41c1-943f-ccfdbcf2239f@app.fastmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 11, 2025, at 10:07 PM, Efrain J. Berdecia wrote:
> The error I would like to address with this feature is the following:
>
> FATAL: highest timeline xxx of the primary is behind timeline yyy
>

It seems your procedure to set up a standby is incorrect. See [1]. You are not
using the base backup from the primary server.

You didn't describe the whole procedure so it is hard to point out where the
problem is.

[1] https://www.postgresql.org/docs/current/warm-standby.html#STANDBY-SERVER-SETUP

--
Euler Taveira
EDB https://www.enterprisedb.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-09-12 01:36:18 Re: [PATCH] Add tests for Bitmapset
Previous Message Efrain J. Berdecia 2025-09-12 01:07:17 Re: New recovery_target_timeline=primary option