| From: | Pavan Kumar <pavan(dot)dba27(at)gmail(dot)com> |
|---|---|
| To: | Rui DeSousa <rui(at)crazybean(dot)net> |
| Cc: | Ron <ronljohnsonjr(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: zero data loss recovery is possbile with pgbackrest tool? |
| Date: | 2019-06-19 21:40:44 |
| Message-ID: | CA+M0sHEamU3hs5b6FJSkRLG5yxhzrZyLCF2fNmxtXzjRzzhcuA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hello Rui,
yes those are committed transaction.
I have tested two cases
1. complete lost. (means complete data directory, pg_wal direcoty)
2. lost few directories (deleted few directories , except pg_wal).
both cases I do see latest data in the current wal is lost.
when I check the recovery process , wal archives are copying from
pgbackrest repository to pg_wal directory. however pgbackrest tool is not
copying current wal log at all. it is only copying archived wal's/
is there any way to copy current wal log with pgbackrest tool?
On Wed, Jun 19, 2019 at 4:33 PM Rui DeSousa <rui(at)crazybean(dot)net> wrote:
>
>
> > On Jun 19, 2019, at 5:23 PM, Ron <ronljohnsonjr(at)gmail(dot)com> wrote:
> >
> > Set the checkpoint timeout to something closer to what you want.
> >
> >
>
> Checkpoint does not matter.
>
> You shouldn’t loose committed transactions. Was the transaction
> committed? Do you have all the WALs?
>
>
>
>
--
*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 | S. Bob | 2019-06-19 23:39:53 | Vacuum not cleaning up rows. |
| Previous Message | Rui DeSousa | 2019-06-19 21:33:09 | Re: zero data loss recovery is possbile with pgbackrest tool? |