MIME-Version: 1.0
References: <f14463ab-990b-4ae9-a177-998d2677aae0@pgbackrest.org>
 <CAHGQGwEnakTrosMp3Y=Trya4MTC-h8Lqx3FDU1mOALRQ0rz59Q@mail.gmail.com>
 <9e8b7ee9-4a16-477a-baa5-0cdf37a04798@pgbackrest.org>
 <CAHGQGwG44vZbSoBmg076G+xkR6n=Tj2=q+fVkfP7yEsyF1daFA@mail.gmail.com>
 <c2e97e35-1227-4351-8faa-fa95208f6cf9@pgbackrest.org>
 <aakAmNjKyBWRU1vR@paquier.xyz>
 <e6a27751-8c91-4bff-ba07-2e97de99e34f@pgbackrest.org>
In-Reply-To: <e6a27751-8c91-4bff-ba07-2e97de99e34f@pgbackrest.org>
From: Fujii Masao <masao.fujii@gmail.com>
Date: Thu, 5 Mar 2026 14:03:37 +0900
Message-ID: 
 <CAHGQGwEYYad_=fiBkt8HZ=aknXoCUx=2cL7UwSQSYM3nozHMyg@mail.gmail.com>
Subject: Re: Improve checks for GUC recovery_target_xid
To: David Steele <david@pgbackrest.org>
Cc: Michael Paquier <michael@paquier.xyz>,
 =?UTF-8?Q?H=C3=BCseyin_Demir?= <huseyin.d3r@gmail.com>,
	Pg Hackers <pgsql-hackers@postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAHGQGwEYYad_%3DfiBkt8HZ%3DaknXoCUx%3D2cL7UwSQSYM3nozHMyg%40mail.gmail.com>
Precedence: bulk

On Thu, Mar 5, 2026 at 1:21=E2=80=AFPM David Steele <david@pgbackrest.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,

--=20
Fujii Masao