Re: block-level incremental backup
От | vignesh C |
---|---|
Тема | Re: block-level incremental backup |
Дата | |
Msg-id | CALDaNm2dO5caOQUvSsA=BWLgFxpVYvntWVG9wZh=eEsyg+Q-zA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: block-level incremental backup (Jeevan Chalke <jeevan.chalke@enterprisedb.com>) |
Ответы |
Re: block-level incremental backup
|
Список | pgsql-hackers |
Hi Jeevan, The idea is very nice. When Insert/update/delete and truncate/drop happens at various combinations, How the incremental backup handles the copying of the blocks? On Wed, Jul 17, 2019 at 8:12 PM Jeevan Chalke <jeevan.chalke@enterprisedb.com> wrote: > > > > On Wed, Jul 17, 2019 at 7:38 PM Ibrar Ahmed <ibrar.ahmad@gmail.com> wrote: >> >> >> >> On Wed, Jul 17, 2019 at 6:43 PM Jeevan Chalke <jeevan.chalke@enterprisedb.com> wrote: >>> >>> On Wed, Jul 17, 2019 at 2:15 PM Ibrar Ahmed <ibrar.ahmad@gmail.com> wrote: >>>> >>>> >>>> At what stage you will apply the WAL generated in between the START/STOP backup. >>> >>> >>> In this design, we are not touching any WAL related code. The WAL files will >>> get copied with each backup either full or incremental. And thus, the last >>> incremental backup will have the final WAL files which will be copied as-is >>> in the combined full-backup and they will get apply automatically if that >>> the data directory is used to start the server. >> >> >> Ok, so you keep all the WAL files since the first backup, right? > > > The WAL files will anyway be copied while taking a backup (full or incremental), > but only last incremental backup's WAL files are copied to the combined > synthetic full backup. > >>> >>>> >>>> -- >>>> Ibrar Ahmed >>> >>> >>> -- >>> Jeevan Chalke >>> Technical Architect, Product Development >>> EnterpriseDB Corporation >>> >> >> >> -- >> Ibrar Ahmed > > > > -- > Jeevan Chalke > Technical Architect, Product Development > EnterpriseDB Corporation > -- Regards, vignesh EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: