From: | Pavan Kumar <pavan(dot)dba27(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(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:40:09 |
Message-ID: | CA+M0sHHqKYZK3N-S6DRHtFrBvkvSxyq=N5o6U3M-VtqNXPgnAg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hello David,
Thank you so much for quick response.
I have couple of questions on recoveries.
1. my postgres did not recovered/read all the wal logs that are existed in
wal location? is it some thing wrong i am doing ?
content of my recovery file command
cat recovery.conf
restore_command = 'cp /pgdata/archive/5444/%f %p'
2. what is the best way to instruct postgresql to read and apply all the
logs are presented on wal location ?
please advise
On Mon, Apr 22, 2019 at 4:20 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> 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.
>
--
*Regards,#! Pavan Kumar----------------------------------------------*-
*Sr. Database Administrator..!*
*NEXT GENERATION PROFESSIONALS, LLC*
*Cell # 267-799-3182 # pavan.dba27 (Gtalk) *
*India # 9000459083*
*Take Risks; if you win, you will be very happy. If you lose you will be
Wise *
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2019-04-22 21:51:24 | Re: postgres complete recovery |
Previous Message | David G. Johnston | 2019-04-22 21:20:24 | Re: postgres complete recovery |