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

From Fujii Masao
Subject Re: Improve checks for GUC recovery_target_xid
Date
Msg-id CAHGQGwGuyb--9MBJX__FVJH1=ny0Jh1H+j0Z-_z-28VZy9hK8g@mail.gmail.com
Whole thread
In response to Re: Improve checks for GUC recovery_target_xid  (David Steele <david@pgbackrest.org>)
Responses Re: Improve checks for GUC recovery_target_xid
List pgsql-hackers
On Thu, Mar 5, 2026 at 5:15 PM David Steele <david@pgbackrest.org> wrote:
>
> 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.

Thanks for updating the patch! I've pushed the patch.

Regards,

--
Fujii Masao



pgsql-hackers by date:

Previous
From: shveta malik
Date:
Subject: Re: Skipping schema changes in publication
Next
From: Pavel Stehule
Date:
Subject: Re: proposal: schema variables