DB Sync 13.7.1.0
DB Sync 13.7.1.0 is a fix on the epoch table. It fixes in place any older possibly wrong values, caused by bugs from older versions.
Upgrading
Upgrading from 13.7.0.X takes a few minutes and runs the epoch table fix migration migration-2-0048-20260520.sql
Otherwise this release is similar to 13.7.0.5
Snapshots
The release is compatible with both 13.7 and 13.6 DB snapshots:
| Network | Link |
|---|---|
| Mainnet 13.7 | https://update-cardano-mainnet.iohk.io/cardano-db-sync/index.html#13.7/ |
| Mainnet 13.6 | https://update-cardano-mainnet.iohk.io/cardano-db-sync/index.html#13.6/ |
Changelog
https://github.com/IntersectMBO/cardano-db-sync/blob/release/13.7.1.0/CHANGELOG.md#13710
LSM (experimental)
- Enable by setting
"ledger_backend": "lsm"in the db-sync config — see config docs. - Snapshots can be converted between InMemory and LSM with
snapshot-converter— see snapshot docs.
The compatiblesnapshot-converteris shipped with node-11.0.1. --bootstrap-tx-outis not supported with LSM.
Notes
When running db-sync, enable only the data you actually need. This is
configured in the db-sync config file — see config docs.
Platforms
- Linux 64-bit
- Docker image
- Requires
ghc-9.6.xto build
Known issues (identical to cardano-node)
- When using the LSM storage backend,
db-synccannot read blocks with more than 4096 items due to a bug inblockio-uring. This issue already has a fix that will be included into the next release. - When using the LSM storage backend,
db-synccould crash due to howghchandles system threads. This only happens on resource-constrained devices such as the Raspberry Pi. The fix will be shipped in the next release. - When using the LSM storage backend, the CPU idle time is reported as
iowait. This is not a performance or correctness issue, but it may be confusing. The fix will be shipped in the next release.
Sign-off
| Role | Approval |
|---|---|
| Technical Lead | 🟢 |
| Intersect TSC | 🟢 |
| Intersect Product Committee | 🟢 |
| Test Engineer | |
| Site Reliability Engineer |