On 20/6/19 12:40 π.μ., Pavan Kumar wrote:
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?
No tool that is based on archiving is able to do that. Incomplete wals don't get archived till they are complete. So, you have the risk of losing (maximum) 16MB worth of data.
If you want to minimize the effect of this, you should set
https://www.postgresql.org/docs/11/runtime-config-wal.html#GUC-ARCHIVE-TIMEOUT (
archive_timeout) to a smaller value .
In order to achieve zero data loss, in general, you have to use a tool that can support synchronous streaming replication. For an overview you may look here :
https://severalnines.com/blog/current-state-open-source-backup-management-postgresql
> On Jun 19, 2019, at 5:23 PM, Ron <ronljohnsonjr@gmail.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, LLCCell # 267-799-3182 # pavan.dba27 (Gtalk) India # 9000459083Take Risks; if you win, you will be very happy. If you lose you will be Wise
--
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt