florijan 1ee6d6d05e Make WAL recovery linear ... Summary: This is a proposal on how the WAL recovery process can be implemented so that Deltas aren't accumulated, but instead applied in the same order they are written to the WAL. I *believe* that the only additional requirement on the system are atomic transaction Begin/Commit/Abort. By atomic I mean that they are present in the WAL in exactly the same ordering like in the transaciton engine, to ensure the same commitability of original and recovery transactions. This could be a requirement for HA recovery. It is desirable that WAL and HA log become the same thing, and the recovery process too. Reviewers: mtomic, dgleich, mislav.bradac Reviewed By: mislav.bradac Subscribers: pullbot Differential Revision: https://phabricator.memgraph.io/D1068		2017-12-22 10:02:09 +01:00
..
commit_log.hpp	Add RPC to distributed tx::Engine	2017-12-11 11:05:01 +01:00
engine_master.cpp	Make WAL recovery linear	2017-12-22 10:02:09 +01:00
engine_master.hpp	Make WAL recovery linear	2017-12-22 10:02:09 +01:00
engine_rpc_messages.hpp	Generalize cereal message macro	2017-12-13 12:53:15 +01:00
engine_worker.cpp	Add master/worker flags, main functions and coordination	2017-12-19 16:05:57 +01:00
engine_worker.hpp	Add master/worker flags, main functions and coordination	2017-12-19 16:05:57 +01:00
engine.hpp	Prepare transactional engine for distributed	2017-12-01 09:17:44 +01:00
lock_store.hpp	Replace debug_assert, permanent_assert with DCHECK/CHECK	2017-10-11 14:43:32 +02:00
snapshot.hpp	Add RPC to distributed tx::Engine	2017-12-11 11:05:01 +01:00
transaction.hpp	Remove tx::Transaction undefined methods	2017-12-21 12:02:39 +01:00
type.hpp	Fix SegFault within executor state	2017-11-20 11:27:08 +01:00