Db migration app from mainnet to berkeley #12906
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
!ci-build-me |
|
!ci-build-me |
|
!ci-build-me |
MartinMinkov
approved these changes
Mar 23, 2023
|
!ci-build-me |
| |sql} ) | ||
| (Mina_caqti.insert_into_cols ~returning:"id" ~table_name | ||
| ~tannot:(function | ||
| | "sub_window_densities" -> |
There was a problem hiding this comment.
Would this change affect the archiver on berkeley branch?
There was a problem hiding this comment.
Do you mean the berkeley testnet (this PR is against the berkeley branch)?
This fix affects only archiving extensional blocks, so it doesn't affect the processor running on the testnet.
ghost-not-in-the-shell
approved these changes
Oct 31, 2023
|
!ci-build-me |
|
!approved-for-mainnet |
This was referenced Nov 13, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
App to migrate mainnet archive db data to berkeley schema. Ledger hashes and snarked ledger hashes are left intact. The implementation converts each block into the "extensional" format, and imports that into the new db.
Notes:
accounts_accessedtable is not populated, that requires the ledger contents; a modified replayer will do that in a separate migration stepPart of #12676.
Part of #14313.
Closes #10945.