← Thursday, October 15, 2026ArchitectureDeep dive
Materialize builds a linearizable log on READ COMMITTED after metadata latency spikes
After SERIALIZABLE queries left PostgreSQL metadata connections waiting and pushed latency as high as 30 seconds, Materialize reworked its store to build a linearizable log under READ COMMITTED. The write-up includes invariants, correctness reasoning and rollout details.
- What
- Materialize reworked its persist metadata store to build a linearizable log using PostgreSQL READ COMMITTED isolation.
- How
- Processes extend a versioned log of shard state diffs with compare-and-set operations; writers retry when the expected version is no longer current.
- Why it matters
- The design sustained three times the write throughput and degraded gracefully under overload, while a Lean 4 model helped prove linearizability.
Discussion
Discussion is not switched on yet. Use Note above to keep your own thoughts on this story.
Headline, summary, brief and diagram are written by a model from the source's own text; the link, byline and numbers come from the source. Read the original before relying on a claim.
