Skip to content

Instantly share code, notes, and snippets.

@s3krit

s3krit/paritydb-migration.md

Last active October 21, 2021 18:52
Show Gist options
  • Save s3krit/3ae07cf448f9bd1bb599b0b071562b3c to your computer and use it in GitHub Desktop.
Save s3krit/3ae07cf448f9bd1bb599b0b071562b3c to your computer and use it in GitHub Desktop.
Download ZIP
ParityDB-experimental migration
Raw
paritydb-migration.md

If you are using the EXPERIMENTAL paritydb database for your Polkadot node, when upgrading to Polkadot v0.9.12 from Polkadot v0.9.11, you will need to perform the following manual step after updating your node.

If you are not using the EXPERIMENTAL paritydb (using the --database paritydb-experimental flag) you do not need to take any action and this document can be ignored.

For the below commands, $CHAIN will depend on which chain you are syncing with your node.

  • For Polkadot, $CHAIN is polkadot
  • For Kusama, $CHAIN is ksmcc3
  • For Westend, $CHAIN is westend2

If you do not specify a custom BASE_PATH with --base-path/-d $SOME_LOCATION, execute the following command to move your database to the new location:

  • mv ~/.local/share/polkadot/chains/$CHAIN/db/ ~/.local/share/polkadot/chains/$CHAIN/paritydb/

If you do specify a custom BASE_PATH with --base-path/-d $SOME_LOCATION, execute the following command to move your database to the new location, where $BASE_PATH is the current location provided to the --base-path/-d argument:

  • mv $BASE_PATH/chains/$CHAIN/db $BASE_PATH/chains/$CHAIN/paritydb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment