Hi Igniters!
There are some updates for IEP-89 [1]. It proposes to use an incremental
snapshot for PITR.
Incremental snapshots is a lightweight alternative for Ignite full
snapshot. Incremental snapshots are created by a non-blocking Consistent
Cut algorithm, and the incremental snapshot
Hi Roman,
Thanks for your comments! Yes, at the beginning I considered using a single
class for two types of records. But it is confusing, as you're correctly
noticed. I reworked IEP, now there are 2 different classes, and both
contain a list of transactions to include. Also I added info about
Hi Maksim.
Do I understand correctly that 'consistent cut start' message always
contains IDs of transactions to include, while 'consistent cut finish'
message always contains IDs of transactions to exclude from the
consistent cut? (At least, this is the impression I got from the
example of
Dear Igniters,
I just published IEP-89 [1] that proposes a new feature to Ignite - (point
in time recovery) PITR. I propose to implement the Consistent Cut algorithm
for this, actually I achieved a working PoC for Ignite. And based on my
research I wrote this IEP.
Let's start a discussion here.
