Re: Requested WAL segment xxx has already been removed

From: Alexander Kukushkin <cyberdemn(at)gmail(dot)com>
To: Japin Li <japinli(at)hotmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Requested WAL segment xxx has already been removed
Date: 2025-07-15 10:12:01
Message-ID: CAFh8B=nV2w1othGwiN4O5_n1chjouP_He_esw=GUbr02_6TMrg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 15 Jul 2025 at 12:08, Japin Li <japinli(at)hotmail(dot)com> wrote:

>
> IIRC, the standby will indefinitely attempt to connect for replication,
> even
> without restore_command configured.
>

That's correct. However right now it just results in an attempt to open the
WAL segment in pg_wal and failing, what is cheap.
Calling restore_command is more expensive and therefore the impact on
resource usage will be bigger.

Regards,
--
Alexander Kukushkin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bertrand Drouvot 2025-07-15 10:18:16 Re: Improve LWLock tranche name visibility across backends
Previous Message Japin Li 2025-07-15 10:07:56 Re: Requested WAL segment xxx has already been removed