Re: block-level incremental backup
От | Rajkumar Raghuwanshi |
---|---|
Тема | Re: block-level incremental backup |
Дата | |
Msg-id | CAKcux6nYbNi2PjZYGFwjxo7HRMPGWHN2vfa_fcGsJiLezXFz9Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: block-level incremental backup (Jeevan Ladhe <jeevan.ladhe@enterprisedb.com>) |
Список | 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 alsoallows taking backup in tar and compressed format. But, pg_combinebackupdoes not understand how to restore this. I think we should either makepg_combinebackup support restoration of tar incremental backup or restricttaking the incremental backup in tar format until pg_combinebackupsupports the restoration by making option '--lsn' and '-Ft' exclusive.It is arguable that one can take the incremental backup in tar format, extractthat manually and then give the resultant directory as input to thepg_combinebackup, but I think that kills the purpose of havingpg_combinebackup utility.Thoughts?Regards,Jeevan Ladhe
Вложения
В списке pgsql-hackers по дате отправления: