| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Pavan Kumar <pavan(dot)dba27(at)gmail(dot)com> |
| Cc: | "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: postgres complete recovery |
| Date: | 2019-04-22 21:20:24 |
| Message-ID: | CAKFQuwYUiebm6Dsdg5NgQ73e+SEnKsrd3BdFVe8dtT-=74Bm2w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Monday, April 22, 2019, Pavan Kumar <pavan(dot)dba27(at)gmail(dot)com> wrote:
>
> lost of latest wal file/log will give some data loss, need to find a way
> to have redundant copy on latest wall logfile
>
This is indeed the defined behavior for a cold storage backup system
relying on wal shipping.
If you want something better at maintaining recency you need to setup some
kind of hot/live standby sever where all activity is immediately sent to
and (more or less) applied to a second already running system. Though
logical replication techniques on a current release may provide additional
options.
https://www.postgresql.org/docs/11/high-availability.html
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavan Kumar | 2019-04-22 21:40:09 | Re: postgres complete recovery |
| Previous Message | Pavan Kumar | 2019-04-22 21:07:00 | postgres complete recovery |