Support efficient query for related account with method filter #897
Conversation
ptrus
changed the title
ptrus
force-pushed
the
ptrus/feature/related-txs-denom
branch
2 times, most recently
from
35a0bc7 to
61c160b
Compare
ptrus
force-pushed
the
ptrus/feature/related-txs-denom
branch
from
61c160b to
d1e1d73
Compare
| end_block INT; | ||
| max_block INT; | ||
| affected_rows INT; | ||
| BEGIN |
There was a problem hiding this comment.
some of this stuff seems to be in the wrong commit?
The related accounts change (#809) was only for the events tables. Transactions tables already had related accounts split out in a separate table, so no changes were needed in #809. This PR only deals with transaction tables. We denomralize some fields so that we can have more efficient indexes for the combination of related accounts + method filters. These filters are not needed for the events tables at this time, so no changes there. |
ptrus
force-pushed
the
ptrus/feature/related-txs-denom
branch
5 times, most recently
from
ce7f74f to
8151721
Compare
ptrus
force-pushed
the
ptrus/feature/related-txs-denom
branch
from
8151721 to
f1b94db
Compare
| CREATE INDEX ix_runtime_related_transactions_address_method_round ON chain.runtime_related_transactions (runtime, account_address, method, tx_round, tx_index); | ||
| CREATE INDEX ix_runtime_related_transactions_address_native_transfer_round ON chain.runtime_related_transactions (runtime, account_address, likely_native_transfer, tx_round, tx_index); | ||
| -- This combination is needed, since explorer needs to obtain evm.Call's which are not native transfers. | ||
| CREATE INDEX ix_runtime_related_transactions_address_method_native_transfer_round ON chain.runtime_related_transactions (runtime, account_address, method, likely_native_transfer, tx_round, tx_index); |
There was a problem hiding this comment.
do we want tx_round DESC here?
There was a problem hiding this comment.
should be equivalent either way, with the preceding fields only filtered by equality
Fixes: #896
Note: The migrations will likely take multiple hours Before this is released and deployed, it would be good to have "Nexus Blue " ready so that we can switch Nexus backend explorer uses during the update.