Re: BUG #18179: Cluster History Error

On Mon, 2023-11-13 at 21:00 +0300, Abdullah Ergin wrote:
>  Nov 09 17:01:44 se-prd-db02 postgresql@13-mydb[767207]: sh: 1: pgbackrest: not found
>  Nov 09 17:01:44 se-prd-db02 postgresql@13-mydb[767207]: 2023-11-09 17:01:44.700 +03 [767228] FATAL: could not
restorefile "00000004.history" from archive: command not found 
>  Nov 09 17:01:44 se-prd-db02 postgresql@13-mydb[767207]: 2023-11-09 17:01:44.703 +03 [767227] LOG: startup process
(PID767228) exited with exit code 1 
>  Nov 09 17:01:44 se-prd-db02 postgresql@13-mydb[767207]: 2023-11-09 17:01:44.703 +03 [767227] LOG: aborting startup
dueto startup process failure 
>  Nov 09 17:01:44 se-prd-db02 postgresql@13-mydb[767207]: 2023-11-09 17:01:44.745 +03 [767227] LOG: database system is
shutdown 
>
> Based on this, I checked the `postgresql.auto.conf` on my master server, and the restore information found there is
asfollows: 
>
> # Recovery settings generated by pgBackRest restore on 2021-09-29 01:04:40
> restore_command = 'pgbackrest --stanza=mydb_stanza archive-get %f "%p'

Use the absolute path for "pgbackrest".
Did you install pgBackRest on the standby?

Yours,
Laurenz Albe