You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Motivated recently by #1277 it would be great to have a procedure that fixes old values in db-sync. Currently, if there is a bug fix, it only affects values after the upgrade, old values remain wrong. This procedure would use the chainsync server from an earlier point and replace only the wrong values.
This is related to #1172, where the end goal is to have migrations on each release, so that users don't have to resync any blocks. The procedure could also be used as a tool to fix snapshots.
The text was updated successfully, but these errors were encountered:
Motivated recently by #1277 it would be great to have a procedure that fixes old values in db-sync. Currently, if there is a bug fix, it only affects values after the upgrade, old values remain wrong. This procedure would use the chainsync server from an earlier point and replace only the wrong values.
This is related to #1172, where the end goal is to have migrations on each release, so that users don't have to resync any blocks. The procedure could also be used as a tool to fix snapshots.
The text was updated successfully, but these errors were encountered: