| From: | David Steele <david(at)pgbackrest(dot)org> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| 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 08:15:29 |
| Message-ID: | bc089939-a889-4fd4-bad8-42cc071cd58e@pgbackrest.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/5/26 12:03, Fujii Masao wrote:
> 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.
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 | Content-Type | Size |
|---|---|---|
| recovery-target-xid-v4.patch | text/plain | 5.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anthonin Bonnefoy | 2026-03-05 08:40:25 | Re: Shutdown indefinitely stuck due to unflushed FPI_FOR_HINT record |
| Previous Message | Xuneng Zhou | 2026-03-05 07:37:10 | Re: Add pg_stat_recovery system view |