MIME-Version: 1.0
References: <CAKoxK+5ypkP1Ts1KNuCgqAxwp=8ejQ-wfiBrpvZ1coZ3dZfOWg@mail.gmail.com>
 <a008ba3a3dab42ea0f7f3d47ad3f3304c5f3eeba.camel@cybertec.at>
In-Reply-To: <a008ba3a3dab42ea0f7f3d47ad3f3304c5f3eeba.camel@cybertec.at>
From: Luca Ferrari <fluca1978@gmail.com>
Date: Thu, 8 May 2025 08:54:30 +0200
Message-ID: <CAKoxK+5XT5bAV+w-4dC=rP+a7t2zkvRf8+-wj087yd1Fd5b2iQ@mail.gmail.com>
Subject: Re: pg_rewind problem: cannot find WAL
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: pgsql-general <pgsql-general@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAKoxK%2B5XT5bAV%2Bw-4dC%3DrP%2Ba7t2zkvRf8%2B-wj087yd1Fd5b2iQ%40mail.gmail.com>
Precedence: bulk

On Wed, May 7, 2025 at 3:55=E2=80=AFPM Laurenz Albe <laurenz.albe@cybertec.=
at> wrote:
>
> I don't think it is connected to a WAL switch.
>

Thanks.

> I'd say that you should set "wal_keep_size" high enough that all the WAL
> needed for pg_rewind is still present.
>
> If you have a WAL archive, you could define a restore_command on the serv=
er
> you want to rewind.

I've pgbackrest making backups, so I have an archive_command. I'm
going to see if putting a restore_command can fix the problem.

Thanks for the suggestion.

Luca