Re: Reviving lost replication slots

From: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
To: sirisha chamarthi <sirichamarthi22(at)gmail(dot)com>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, amit(dot)kapila16(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Reviving lost replication slots
Date: 2022-11-11 06:28:12
Message-ID: CALj2ACUGCC-bJ=jE+csFP_OHzaZCmNKY0fLpmD9McZ2aU7Fpnw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 10, 2022 at 4:12 PM sirisha chamarthi
<sirichamarthi22(at)gmail(dot)com> wrote:
>
> On Wed, Nov 9, 2022 at 12:32 AM 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.
>
> Thanks! If there is a general agreement on this in this forum, I would like to start working on this patch,

I think starting with establishing/summarizing the problem, design
approaches, implications etc. is a better idea than a patch. It might
invite more thoughts from the hackers.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2022-11-11 06:46:13 Re: Typo about subxip in comments
Previous Message Bharath Rupireddy 2022-11-11 06:23:08 Re: Use pg_pwritev_with_retry() instead of write() in dir_open_for_write() to avoid partial writes?