Re: block-level incremental backup

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: block-level incremental backup
Дата
Msg-id 20190411042228.GO2728@paquier.xyz
обсуждение исходный текст
Ответ на Re: block-level incremental backup  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Ответы Re: block-level incremental backup  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
On Wed, Apr 10, 2019 at 09:42:47PM +0200, Peter Eisentraut wrote:
> That is a great analysis.  Seems like block-level is the preferred way
> forward.

In any solution related to incremental backups I have see from
community, all of them tend to prefer block-level backups per the
filtering which is possible based on the LSN of the page header.  The
holes in the middle of the page are also easier to handle so as an
incremental page size is reduced in the actual backup.  My preference
tends toward a block-level approach if we were to do something in this
area, though I fear that performance will be bad if we begin to scan
all the relation files to fetch a set of blocks since a past LSN.
Hence we need some kind of LSN map so as it is possible to skip a
one block or a group of blocks (say one LSN every 8/16 blocks for
example) at once for a given relation if the relation is mostly
read-only.
--
Michael

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: pg_rewind vs superuser
Следующее
От: David Rowley
Дата:
Сообщение: Re: Proper usage of ndistinct vs. dependencies extended statistics