Re: block-level incremental backup
От | Robert Haas |
---|---|
Тема | Re: block-level incremental backup |
Дата | |
Msg-id | CA+TgmoZVTRah+ty2wA=BCPjHcqrxZgNy9-nbyna8Ly5dJEGuZQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: block-level incremental backup (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: block-level incremental backup
|
Список | pgsql-hackers |
On Wed, Sep 4, 2019 at 10:08 PM Michael Paquier <michael@paquier.xyz> wrote: > > For generating a > > file, you can always emit the newest and "best" tar format, but for > > reading a file, you probably want to be prepared for older or cruftier > > variants. Maybe not -- I'm not super-familiar with the tar on-disk > > format. But I think there must be a reason why tar libraries exist, > > and I don't want to write a new one. > > We need to be sure as well that the library chosen does not block > access to a feature in all the various platforms we have. Well, again, my preference is to just not make this particular feature work natively with tar files. Then I don't need to choose a library, so the question is moot. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: