Re: [BUG] [PATCH] Allow physical replication slots to recover from archive after invalidation

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Joao Foltran <joao(at)foltrandba(dot)com>
Cc: "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [BUG] [PATCH] Allow physical replication slots to recover from archive after invalidation
Date: 2026-01-14 11:20:53
Message-ID: CAA4eK1L0SxQRLTrcsvNA7uBydzpWW=pGtxngLJd0_QBuvGpw9Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 6, 2026 at 3:26 AM Joao Foltran <joao(at)foltrandba(dot)com> wrote:
>
> > The slots could be invalidated due to other reasons like
> > RS_INVAL_IDLE_TIMEOUT as well.
>
> We could just filter which invalidation reasons could be "revalidated"
> for only reasons that can be resolved this way.
>

Can we make the slot valid even the required WAL is made available
afterwards? What about the removed rows due to the slot's xmin?

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jelte Fennema-Nio 2026-01-14 11:25:14 Re: Always show correct error message for statement timeouts, fixes random buildfarm failures
Previous Message Jakub Wartak 2026-01-14 11:14:35 Re: [PATCH] check kernel version for io_method