Re: On Replica - History issue

From: SOzcn <selahattinozcnma(at)gmail(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: On Replica - History issue
Date: 2023-10-30 13:27:47
Message-ID: CAJyV5AZa4bmb68JRctyPnS9u8cK-Eib3r24cgLYwKUC2Yb7NRQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

I do with absolute path already, that's the problem.

Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, 30 Eki 2023 Pzt, 15:29 tarihinde
şunu yazdı:

> On Mon, 2023-10-30 at 13:48 +0300, SOzcn wrote:
> > > > Oct 27 13:33:26 se-prd-db02 postgresql(at)13-clustername[316944]:
> 2023-10-27 13:33:26.808 +03 [316957] FATAL: could not restore file
> "00000003.history" from archive: command not found
> > > > Oct 27 13:33:26 se-prd-db02 postgresql(at)13-clustername[316944]: sh:
> 1: pgbackrest: not found
> > >
> > > You should use the absolute path to "pgbackrest" in the
> "restore_command".
> >
> > "restore_command" is default .
> > my archive command is ;
> > archive_command = 'pgbackrest --stanza=cluster_stanza archive-push %p'
> >
> > with this way I setup my backup procedure without problem, is there
> might be another problem I cannot see?
>
> You get a fatal error restoring a file from the archive, because the
> restore command is not found.
>
> What is unclear about the error message? Why don't you try the absolute
> path?
>
> Yours,
> Laurenz Albe
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Loles 2023-10-30 13:28:17 Optimized WHERE UPPER(name) LIKE UPPER('%p_name%')
Previous Message Laurenz Albe 2023-10-30 12:29:52 Re: On Replica - History issue