Re: Proposal: Incremental Backup
От | Marco Nenciarini |
---|---|
Тема | Re: Proposal: Incremental Backup |
Дата | |
Msg-id | 53E3A29B.2080906@2ndquadrant.it обсуждение исходный текст |
Ответ на | Re: Proposal: Incremental Backup (Bruce Momjian <bruce@momjian.us>) |
Ответы |
Re: Proposal: Incremental Backup
|
Список | pgsql-hackers |
Il 07/08/14 17:25, Bruce Momjian ha scritto: > On Thu, Aug 7, 2014 at 08:35:53PM +0900, Michael Paquier wrote: >> On Thu, Aug 7, 2014 at 8:11 PM, Fujii Masao <masao.fujii@gmail.com> wrote: >>> There are some data which don't have LSN, for example, postgresql.conf. >>> When such data has been modified since last backup, they also need to >>> be included in incremental backup? Probably yes. >> Definitely yes. That's as well the case of paths like pg_clog, >> pg_subtrans and pg_twophase. > > I assumed these would be unconditionally backed up during an incremental > backup because they relatively small and you don't want to make a mistake. > You could decide to always copy files which doesn't have LSN, but you don't know what the user could put inside PGDATA. I would avoid any assumption on files which are not owned by Postgres. With the current full backup procedure they are backed up, so I think that having them backed up with a rsync-like algorithm is what an user would expect for an incremental backup. Regards, Marco -- Marco Nenciarini - 2ndQuadrant Italy PostgreSQL Training, Services and Support marco.nenciarini@2ndQuadrant.it | www.2ndQuadrant.it
В списке pgsql-hackers по дате отправления: