On Wed, Apr 10, 2019 at 12:56 PM Ashwin Agrawal <aagra...@pivotal.io> wrote: > Not to fork the conversation from incremental backups, but similar approach > is what we have been thinking for pg_rewind. Currently, pg_rewind requires > all the WAL logs to be present on source side from point of divergence to > rewind. Instead just parse the wal and keep the changed blocks around on > sourece. Then don't need to retain the WAL but can still rewind using the > changed block map. So, rewind becomes much similar to incremental backup > proposed here after performing rewind activity using target side WAL only.
Interesting. So if we build a system like this for incremental backup, or for pg_rewind, the other one can use the same infrastructure. That sound excellent. I'll start a new thread to talk about that, and hopefully you and Heikki and others will chime in with thoughts. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
