This release fixes issue #1831, which could cause DB-Sync to crash under some unusual conditions
(while executing a rollback following an update to constitutional committee members).
It applies the following SQL code to the schema:
ALTER TABLE "committee_member" DROP CONSTRAINT "committee_member_committee_id_fkey";
ALTER TABLE "committee_member" ADD CONSTRAINT "committee_member_committee_id_fkey" FOREIGN KEY("committee_id") REFERENCES "committee"("id") ON DELETE CASCADE ON UPDATE RESTRICT;
Users can alternatively apply this fix manually to any 13.4.x.x
release to avoid or to fix the issue. It is recommended that all
DB-Sync users either upgrade to version 13.5.0.0
or apply the fix manually.
Upgrading
Upgrading from any 13.4.x.x
release happens instantly.
Upgrading from other 13.x.x.x
releases is also possible. A ledger state replay may be necessary from genesis. The existing db is not affected by this, only the ledger snapshot.
If you restart db-sync with different genesis files, you need to initially delete the ledger state snapshots files.
The release is compatible with 13.4
, 13.3
, 13.2
and 13.1
snapshots. They can be found at:
Network | Link to snapshot |
---|---|
Mainnet-13.5 | https://update-cardano-mainnet.iohk.io/cardano-db-sync/index.html#13.5/ |
Mainnet-13.4 | https://update-cardano-mainnet.iohk.io/cardano-db-sync/index.html#13.4/ |
Mainnet-13.2 | https://update-cardano-mainnet.iohk.io/cardano-db-sync/index.html#13.2/ |
Mainnet-13.1 | https://update-cardano-mainnet.iohk.io/cardano-db-sync/index.html#13.1/ |
Documentation
Cardano DB Sync Overview
Building and Running the Cardano DB Sync Node
Schema Management
State snapshot
Smash
Postgres setup
It is advised to use a postgres version >= 14. The default docker postgres has been upgraded to 14.10-alpine
.
There is a postgres
requirement for users that don't use docker-compose
and have to manually configure postgres
:
It is advised to increase `maintenance_work_mem` from the Postgres configuration to 0.5GB - 1GB (the default is 64MB).
Also use the default (2) or higher for `max_parallel_maintenance_workers` (this parameter was introduced in `postgres` version 11)
Notes
When running db-sync
make sure you enable only the data that you need. This can be configured in the db-sync
config file as documented here configuration.md
Platforms
- Linux 64-bit
- Docker
Requiresghc-8.10.x
to build.
Non-default Changelog (this only affect users that use non default options)
- Fix
consumed_by
option for Byron inputs. A migration fixes old wrong values in place. 1821 - Fix only-utxo preset populating the metadata instead of the multiassets
Sign off
Role | Approval |
---|---|
Technical Lead | 🟢 |
Cardano Head of Engineering | 🟢 |
Cardano Head of Product | 🟢 |
Test Engineer | 🟢 |
Site Reliability Engineer | 🟢 |