Re: Improve checks for GUC recovery_target_xid

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: David Steele <david(at)pgbackrest(dot)org>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Hüseyin Demir <huseyin(dot)d3r(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improve checks for GUC recovery_target_xid
Date: 2026-03-05 05:03:37
Message-ID: CAHGQGwEYYad_=fiBkt8HZ=aknXoCUx=2cL7UwSQSYM3nozHMyg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 5, 2026 at 1:21 PM David Steele <david(at)pgbackrest(dot)org> wrote:
> The prior standby is not running because of the invalid config. I
> figured it was better to start clean but when I update the
> recovery_target_timeline tests I was planning to use the same standby
> for all the new tests.

Alternatively, we can use $node_primary, since ALTER SYSTEM SET with
invalid recovery_target_timeline or recovery_target_xid does not
affect the primary.

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message ls7777 2026-03-05 05:04:05 Patch for migration of the pg_commit_ts directory
Previous Message Henson Choi 2026-03-05 04:59:41 Re: Row pattern recognition