Re: BUG #18179: Cluster History Error - Mailing list pgsql-bugs

From Laurenz Albe
Subject Re: BUG #18179: Cluster History Error
Date
Msg-id a6f54b6cef679e17ede0de337c3d7ddaa4432567.camel@cybertec.at
Whole thread Raw
In response to Re: BUG #18179: Cluster History Error  (Abdullah Ergin <abdullaherginwork@gmail.com>)
List pgsql-bugs
On Tue, 2023-11-14 at 00:04 +0300, Abdullah Ergin wrote:
> Laurenz Albe <laurenz.albe@cybertec.at>, 13 Kas 2023 Pzt, 23:13 tarihinde şunu yazdı:
> > On Mon, 2023-11-13 at 22:42 +0300, Abdullah Ergin wrote:
> > > I'm relatively new to database expertise, are you referring to the absolute path as follows:
> > >
> > > postgresql.auto.conf;
> > > #Recovery settings generated by pgBackRest restore on 2021-09-29 01:04:40
> > > restore_command = '/usr/bin/pgbackrest --stanza=mydb_stanza archive-get %f "%p"'
> >
> > Yes, precisely.  But if te executable is in /usr/bin, it should be found
> > anyway... Is there really a /usr/bin/pgbackrest on the standby server?
>
> pgBackRest is only installed on my master and backup servers. The directory where
> it is installed is '/usr/bin/pgbackrest.'
>
> However, pgBackRest is not installed on my replica server.

Then you shouldn't use it in your "restore_command".  Best comment that out.

This is no PostgreSQL bug.

Yours,
Laurenz Albe



pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly
Next
From: PG Bug reporting form
Date:
Subject: BUG #18195: PL/pgSQL: invalid syntax allowed in SELECT INTO statement