| From: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_rewind problem: cannot find WAL |
| Date: | 2025-05-08 06:54:30 |
| Message-ID: | CAKoxK+5XT5bAV+w-4dC=rP+a7t2zkvRf8+-wj087yd1Fd5b2iQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, May 7, 2025 at 3:55 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)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 server
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karsten P | 2025-05-08 09:57:09 | Feature-Request: Performance-Optimization when using limit in combination with order by on querys using union |
| Previous Message | Greg Sabino Mullane | 2025-05-07 16:52:50 | Re: huge_pages=on cause could not map anonymous shared memory: Cannot allocate memory |