Re: could not link file in wal restore lines - Mailing list pgsql-bugs

From Zsolt Ero
Subject Re: could not link file in wal restore lines
Date
Msg-id CAKw-smA-0yhaJJQxqjmYn+dMzLmWoCbwiS7P5jeKe5DjzvM2xA@mail.gmail.com
Whole thread Raw
In response to Re: could not link file in wal restore lines  (David Steele <david@pgmasters.net>)
Responses Re: could not link file in wal restore lines  (David Steele <david@pgmasters.net>)
List pgsql-bugs
I did that, attached the new log.



On 23. Jul 2022 at 18:43:57, David Steele <david@pgmasters.net> wrote:
On 7/23/22 12:39, Zsolt Ero wrote:
> On 23. Jul 2022 at 15:20:32, David Steele <david@pgmasters.net
> <mailto:david@pgmasters.net>> wrote:
> Zsolt, can you add --log-level-console=info to your archive_command so
> we can see what parameters are being passed to pgbackrest?

archive_command = 'pgbackrest --stanza=app --log-level-console=info
archive-push %p'

on the destination server (where the restore happens). There are no
changes in the log, only 3 lines appear once everything is done. I've
attached the log. Do I need to change this command on the source server?

Oops, sorry, I meant the restore_command on the server where you do the
restore.

You'll need to edit this in postgresql.auto.conf after the pgbackrest
restore but before starting PostgreSQL.

Regards,
-David
Attachment

pgsql-bugs by date:

Previous
From: David Steele
Date:
Subject: Re: could not link file in wal restore lines
Next
From: Marco Boeringa
Date:
Subject: Re: Fwd: "SELECT COUNT(*) FROM" still causing issues (deadlock) in PostgreSQL 14.3/4?