Re: block-level incremental backup - Mailing list pgsql-hackers

From Rajkumar Raghuwanshi
Subject Re: block-level incremental backup
Date
Msg-id CAKcux6nYbNi2PjZYGFwjxo7HRMPGWHN2vfa_fcGsJiLezXFz9Q@mail.gmail.com
Whole thread Raw
In response to Re: block-level incremental backup  (Jeevan Ladhe <jeevan.ladhe@enterprisedb.com>)
List pgsql-hackers
Hi,

I am doing some testing on pg_basebackup and pg_combinebackup patches. I have also tried to create tap test for pg_combinebackup by taking  reference from pg_basebackup tap cases.
Attaching first draft test patch.

I have done some testing with compression options, both -z and -Z level is working with incremental backup.

A minor comment : It is mentioned in pg_combinebackup help that maximum 10 incremental backup can be given with -i option, but I found maximum 9 incremental backup directories can be given at a time.

Thanks & Regards,
Rajkumar Raghuwanshi
QMG, EnterpriseDB Corporation


On Thu, Aug 29, 2019 at 10:06 PM Jeevan Ladhe <jeevan.ladhe@enterprisedb.com> wrote:
Due to the inherent nature of pg_basebackup, the incremental backup also
allows taking backup in tar and compressed format. But, pg_combinebackup
does not understand how to restore this. I think we should either make
pg_combinebackup support restoration of tar incremental backup or restrict
taking the incremental backup in tar format until pg_combinebackup
supports the restoration by making option '--lsn' and '-Ft' exclusive.

It is arguable that one can take the incremental backup in tar format, extract
that manually and then give the resultant directory as input to the
pg_combinebackup, but I think that kills the purpose of having
pg_combinebackup utility.

Thoughts?

Regards,
Jeevan Ladhe
Attachment

pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: WIP: Generic functions for Node types using generated metadata
Next
From: Fabien COELHO
Date:
Subject: Re: WIP: Generic functions for Node types using generated metadata