Re: Reviving lost replication slots

On Wed, Nov 9, 2022 at 3:53 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> On Wed, Nov 9, 2022 at 3:00 PM Bharath Rupireddy
> <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
> >
> > On Wed, Nov 9, 2022 at 2:02 PM Kyotaro Horiguchi
> > <horikyota(dot)ntt(at)gmail(dot)com> wrote:
> > >
> > > I don't think walsenders fetching segment from archive is totally
> > > stupid. With that feature, we can use fast and expensive but small
> > > storage for pg_wal, while avoiding replciation from dying even in
> > > emergency.
> >
> > It seems like a useful feature to have at least as an option and it
> > saves a lot of work - failovers, expensive rebuilds of
> > standbys/subscribers, manual interventions etc.
> >
> > If you're saying that even the walsedners serving logical replication
> > subscribers would go fetch from the archive location for the removed
> > WAL files, it mandates enabling archiving on the subscribers.
> >
>
> Why archiving on subscribers is required? Won't it be sufficient if
> that is enabled on the publisher where we have walsender?

Ugh. A typo. I meant it mandates enabling archiving on publishers.

--
Bharath Rupireddy
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com