You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Performance
File and PostgreSQL: a handle hashes each distinct blob content once, as SQLite already did,
instead of on every read. EventStore::get_blob and every callback's ProjectionStore::get_blob
still read the bytes from storage on each call and accept them without SHA-256 only when they
equal, in full, content the handle verified or hashed while writing under the same hash; any
other bytes are hashed and refused on a mismatch, so content changed after a verified read is
refused on the next read through the same handle. A guard that reads a batch blob once per member
of an M-member batch now pays one hash instead of M. The memory is the new provider-neutral eventlog_core::VerifiedContent (32 MiB per handle, cleared on blob deletion, tenant erasure
and a failed blob-binding write), which SQLite now uses unchanged in behaviour. Nothing persisted
changes.
Fixed
ess/effects validates on ess 0.56.0: the EffectBoundaryCoverage invariant that one of records_terminal and records_incomplete holds is written with structured any:, since the
compact predicate form has no or. The condition is unchanged.