feat: introduced an index on transactions to speed up sorting by block_timestamp and index_in_chunk #139
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.
Resolves #135
To apply it to mainnet, we should use
(We never put
CONCURRENTLY
to migration files, I decided that I should be consistent here)Applying it to
35.233.39.106
(it's copy of mainnet with data till 10th of May 2021) took 75 seconds.Select from @frol works in a moment.
Important: columns
block_timestamp, index_in_chunk
should always go in this order, and we should specifydesc
for both or for no columns. That anyway sounds logical.For 14M lines, it took 550 MB of storage. Mainnet has 17M lines, so hopefully it should not be so far from these numbers.
Can I apply it to mainnet?