| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Brajendra Pratap Singh <singh(dot)bpratap766(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: restore_command for postgresql streaming replication |
| Date: | 2020-07-02 15:32:52 |
| Message-ID: | 20200702153252.GR3125@tamriel.snowman.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Greetings,
* Brajendra Pratap Singh (singh(dot)bpratap766(at)gmail(dot)com) wrote:
> Please help us to configure the restore_command on postgresql replication
> server's recovery.conf file incase of ERROR: requested wal segment has
> already been removed on primary and when we have implemented pgbackrest on
> primary database.
>
> Primary database -
>
> archive_command = 'pgbackrest --stanza=uatodb archive-push %p'
For this, the restore_command would be:
restore_command = 'pgbackrest --stanza=uatodb archive-get %f "%p"'
When you use pgbackrest to do a restore with 'pgbackrest restore',
pgbackrest will also write the correct restore_command into the
configuration for the restored system for you.
You might want to check out the user guide:
https://pgbackrest.org/user-guide.html
(that's for v10 on Debian, there's a couple other user guides if you're
on something different that you could look at)
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-07-02 15:43:53 | Re: Different results from identical matviews |
| Previous Message | David G. Johnston | 2020-07-02 15:25:13 | Re: Different results from identical matviews |