From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: block-level incremental backup |
Date: | 2019-04-15 18:14:31 |
Message-ID: | CA+TgmobwHTJuBbMRG2GhT34x9kLxXJ7byXhW-J0=rA4D6N1VkA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Apr 11, 2019 at 1:29 PM Anastasia Lubennikova
<a(dot)lubennikova(at)postgrespro(dot)ru> wrote:
> 2) There should be a command to get only a map of changes without actual
> data.
Good idea.
> 4) The algorithm of collecting changed blocks is another topic.
> Though, it's API should be discussed here:
>
> Do we want to have multiple implementations?
> Personally, I think that it's good to provide several strategies,
> since they have different requirements and fit for different workloads.
>
> Maybe we can add a hook to allow custom implementations.
I'm not sure a hook is going to be practical, but I do think we want
more than one strategy.
> I'll be happy to help with design, code, review, and testing.
> Hope that my experience with pg_probackup will be useful.
Great, thanks!
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2019-04-15 18:17:54 | Re: Zedstore - compressed in-core columnar storage |
Previous Message | Robert Haas | 2019-04-15 18:11:02 | Re: Zedstore - compressed in-core columnar storage |