Re: pg_rewind restore_command issue in PG12

When I read the pg_rewind PG12 doc. It says:

"... but if the target cluster ran for a long time after the divergence,
the old WAL files might no longer be present. In that case, they can be
manually copied from the WAL archive to the pg_wal directory,* or fetched
on startup by configuring **primary_conninfo
<https://www.postgresql.org/docs/12/runtime-config-replication.html#GUC-PRIMARY-CONNINFO>
or restore_command
<https://www.postgresql.org/docs/12/runtime-config-wal.html#GUC-RESTORE-COMMAND>*
.".

So I thought we could use restore_command. But when I try to use it , I
see it doesn't work either.

Thanks.

Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, 4 Oca 2021 Pzt, 15:42 tarihinde şunu
yazdı:

> On 03/01/2021 20:13, Amine Tengilimoglu wrote:
> > In a situation where pg_rewind gets an error due to a missing
> > wall, I have set restore_command so that the needed wals can be read
> > from the archive (I don't want to manually copy the wal files), but I
> > see it doesn't work. What am I missing? Is restore_command not really
> > working with pg_rewind in PG12? Or how should I trigger pg_rewind to
> > use restore_command?
>
> Using restore_command is a new feature in pg_rewind in PostgreSQL 13. It
> doesn't work on earlier versions.
>
> - Heikki
>