This release adds support for Cardano node version 8.0.0 and Cardano node version 8.1.1. Newer node versions may also work, but this functionality has not been tested.
The state snapshot files for this release can be found here:
Network | Link to snapshot |
---|---|
Mainnet | https://update-cardano-mainnet.iohk.io/cardano-db-sync/index.html#13.1/ |
Documentation for restoring from these files available at state-snapshot.md.
Requires ghc-8.10.x
to build.
Static binaries download: TODO
Associated docker image: 13.1.1.3
Upgrade instructions
With this release, we continue our effort to provide easy upgrades from previous releases without the need to resync from genesis. During an upgrade from 13.x, db-sync will change the existing schema and update or fix some of the values that were inserted in the database from previous releases. Read the upgrading docs before upgrading for more details.
Changelog
Added
- compatibility with Cardano
node-8.0.0
andnode-8.1.1
- compatibility with the new format of the
CostModel
in the Alonzo genesis file - a procedure which fixes scripts with wrong cbor during upgrading
- a procedure to fix
ada_pots
during upgrading - developmental
ghc-9.2
compatibility - experimental options which turn off parts of the schema to reduce time, memory and storage requirements
- experimental extra migrations which speed up UTxO queries. Read more consumed-tx-out and prune-tx-out.
Fixed
- an issue where the
ada_pots
didn't match exactly the epoch boundary - an issue where epoch table didn't rollback
- an issue with smash returning
InvalidUrlException
Improved
- Takes less snapshots, since big rollbacks are now faster
- When
--disable-ledger
is enabled a--state-dir
is no longer required
Known issues
- The new extra migrations are only experimentally supported because they're not very well tested and there are a few known issues with them #1420
- The
epoch
table may have some wrong values after upgrading from a previous release.
Documentation
Cardano DB Sync Overview
Building and Running the Cardano DB Sync Node
Schema Management
State snapshot
Smash
Notes
There is a postgres
requirement for users that don't use docker-compose
and have to manually configure postgres
:
It is advised to increase the `maintenance_work_mem` from the Postgres configuration to 0.5GB - 1GB (default is 64MB).
Also use the default (2) or higher `max_parallel_maintenance_workers` (this parameter was introduced in `postgres` version 11)
Platforms
- Linux 64-bit
- Docker
Sign off
Role | Approval |
---|---|
Technical Lead | ✔️ |
Cardano Head of Engineering | ✔️ |
Cardano Head of Product | ✔️ |
Test Engineer | ✔️ |
Site Reliability Engineer | ✔️ |