pub const AUTOMATIC_SNAPSHOT: SnapshotOptions;Expand description
What every snapshot mushroomdb takes on its own does with the WAL.
An ingest that ends past the WAL threshold, a serve --snapshot-every
tick, a graceful shutdown, and a plain mushroomdb snapshot all archive the
WAL to wal.<N>.archive rather than dropping it. node_history,
edge_history, was_linked and open_at all read WAL frames and all
consult archives, so the store opens fast and still remembers how it got
here. A truncating snapshot ends that reach — it deletes the genesis marker
as well as the tail — so it is never something mushroomdb decides for the
user: only mushroomdb snapshot --truncate does it.