Re: Improve checks for GUC recovery_target_xid - Mailing list pgsql-hackers

From David Steele
Subject Re: Improve checks for GUC recovery_target_xid
Date
Msg-id bc089939-a889-4fd4-bad8-42cc071cd58e@pgbackrest.org
Whole thread Raw
In response to Re: Improve checks for GUC recovery_target_xid  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Improve checks for GUC recovery_target_xid
List pgsql-hackers
On 3/5/26 12:03, Fujii Masao wrote:
> On Thu, Mar 5, 2026 at 1:21 PM 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.

Well, as it turns out I was using the primary after all because I copied 
your example and forgot to update the host. Seems weird to set these 
GUCs on the primary but as long as we get the expected errors I don't 
suppose it matters.

Regards,
-David
Attachment

pgsql-hackers by date:

Previous
From: Xuneng Zhou
Date:
Subject: Re: Add pg_stat_recovery system view
Next
From: Anthonin Bonnefoy
Date:
Subject: Re: Shutdown indefinitely stuck due to unflushed FPI_FOR_HINT record