| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Zsolt Ero <zsolt(dot)ero(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org, Michael Paquier <michael(at)paquier(dot)xyz> |
| Subject: | Re: could not link file in wal restore lines |
| Date: | 2022-07-23 16:43:57 |
| Message-ID: | 1bbb2f44-fdf8-71ef-a8f7-24b3fadb3176@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 7/23/22 12:39, Zsolt Ero wrote:
>> On 23. Jul 2022 at 15:20:32, David Steele <david(at)pgmasters(dot)net
>> <mailto:david(at)pgmasters(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zsolt Ero | 2022-07-23 16:53:53 | Re: could not link file in wal restore lines |
| Previous Message | Zsolt Ero | 2022-07-23 16:39:55 | Re: could not link file in wal restore lines |