Re: pgsql: Prevent invalidation of newly synced replication slots. - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: pgsql: Prevent invalidation of newly synced replication slots.
Date
Msg-id CAA4eK1KOjv0sLKfwWddR_tLzK=Tfnsszy-PKM4xHTs7nFX3nMg@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Prevent invalidation of newly synced replication slots.  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: pgsql: Prevent invalidation of newly synced replication slots.
List pgsql-hackers
On Wed, Jan 28, 2026 at 11:17 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> It is not clear to me either why the similar test like
> 040_standby_failover_slots_sync is successful and
> 046_checkpoint_logical_slot is failing. I am still thinking about it
> but thought of sharing the information I could gather by debugging.
>

It seems there is some interaction with previous test in same file
which is causing this failure as we are using the primary node from
previous test. When I tried to comment out get_changes and its
corresponding injection_point in the previous test as attached, the
entire test passed. I think if we use a freshly created primary node,
this test will pass but I wanted to spend some more time to see
how/why previous test is causing this issue?

--
With Regards,
Amit Kapila.

Attachment

pgsql-hackers by date:

Previous
From: Andrey Borodin
Date:
Subject: Re: pgsql: Prevent invalidation of newly synced replication slots.
Next
From: Jakub Wartak
Date:
Subject: Re: pg_stat_io_histogram