Repository navigation
A regular release from master. The region, database and log formats, the
soname (libdb-2026.0) and the public ABI of a default build are the same as
2026.10.7, so no upgrade procedure is needed. Environments created by
2026.10.7 or 2026.10.7.1 open with 2026.10.8 and the other way round.
Faster transactional writes (#228):
- lock: with detection on every conflict, each blocking thread built the
full waits-for graph, taking all 64 locker stripes. Nearly every conflict
is a convoy behind one page and cannot deadlock. The detector now skips
the graph when every waiter is on one object and none is an upgrade
behind another holder. A victim abort locks only its own stripe. - db: inserts and deletes no longer lock the cursor-queue partitions that
have no cursors.
Against 2026.10.7, median of 3:
| workload | Linux x86_64 | Linux aarch64 | FreeBSD aarch64 |
|---|---|---|---|
| btree insert, 4 threads | 1.43× | 1.65× | 1.50× |
| recno read-modify-write, 4 threads | 1.88× | 2.47× | 2.38× |
| hash insert, 16 threads | 1.49× | 2.34× | 1.05× |
| reads and scans | 0.95–1.10× (62 cells) |
Against Berkeley DB 5.3.28 on Linux x86_64 metal: concurrent reads and scans
1.18-5.05x, TPC-C-like 5.6-6.4x, single-threaded 0.98x (geomean). Still
slower: inserts at 16-32 threads and TPC-B write-no-sync at 16-32 threads.
test/bench/XREL-2026-10.md has every number. Upgrade note: upgrade_2026_10_8.md.
Also since 2026.10.7: typed data and constraints (RFC 0014, opt-in
--enable-typed, #217); Rust and Zig bindings (RFC 0016, #213); DTrace
probes for the log fsync and the async checkpoint write (#224); the three
2026.10.7.1 fixes (#218, #219, #220); the configure-option gate sweeps
--enable-typed (#229).
Known issues: configure needs --build=aarch64-unknown-linux-gnu on Linux
aarch64 (2011 config.guess, every release); macOS arm64 multi-process
contention can panic (fix in review, #226).
Qualified on Linux x86_64 (c6id.metal, Fedora 45), Linux aarch64
(c7gd.metal, Debian 12), FreeBSD 14.5 x86_64 and FreeBSD 14.5 aarch64
(c7g.metal). The --enable-diagnostic test/db tier ran 40 runners with 0
failures on each. The region signature equals 2026.10.7's on each:
0x841f4ea8, 0x10ccbca0, 0x56a06689, 0x56a06689. CI is at job level,
0 failed. The record is in the release PR (#230).