cerc-io/ipld-eth-db
19
0
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects Releases 4 Wiki Activity
2165b316fa
ipld-eth-db/db/migrations/00014_create_cid_indexes.sql

131 lines
6.1 KiB
MySQL
Raw Normal View History

db schema and migrations
2021-08-29 18:55:44 +00:00
-- +goose Up
-- header indexes
denormalize tables by block_number so that we can partition all tables by block_number for purposes of sharding
2022-03-15 21:06:13 +00:00
CREATE INDEX header_block_number_index ON eth.header_cids USING brin (block_number);
fixes, PKs need to include partition key
2022-04-13 02:56:27 +00:00
CREATE UNIQUE INDEX header_cid_index ON eth.header_cids USING btree (cid, block_number);
updates order of columns in compound PKs, update indexes e.g. we don't need a btree index on a column if it is the first column in the compound PK index but we do need a btree index for the later columns in a compound PK (searches on first column of a compound index are just as fast as searches on a btree index for that column alone, but searches on the 2nd or 3rd column in a compound index are significantly slower than on dedicated indexes)
2022-03-28 23:22:57 +00:00
CREATE UNIQUE INDEX header_mh_block_number_index ON eth.header_cids USING btree (mh_key, block_number);
revert hash indexes; add eth probes tables
2022-08-30 17:05:51 +00:00
CREATE INDEX state_root_index ON eth.header_cids USING btree (state_root);
db schema and migrations
2021-08-29 18:55:44 +00:00
CREATE INDEX timestamp_index ON eth.header_cids USING brin (timestamp);
new natural primary key scheme
2021-11-15 00:06:02 +00:00
-- uncle indexes
denormalize tables by block_number so that we can partition all tables by block_number for purposes of sharding
2022-03-15 21:06:13 +00:00
CREATE INDEX uncle_block_number_index ON eth.uncle_cids USING brin (block_number);
updates order of columns in compound PKs, update indexes e.g. we don't need a btree index on a column if it is the first column in the compound PK index but we do need a btree index for the later columns in a compound PK (searches on first column of a compound index are just as fast as searches on a btree index for that column alone, but searches on the 2nd or 3rd column in a compound index are significantly slower than on dedicated indexes)
2022-03-28 23:22:57 +00:00
CREATE UNIQUE INDEX uncle_mh_block_number_index ON eth.uncle_cids USING btree (mh_key, block_number);
new natural primary key scheme
2021-11-15 00:06:02 +00:00
CREATE INDEX uncle_header_id_index ON eth.uncle_cids USING btree (header_id);
db schema and migrations
2021-08-29 18:55:44 +00:00
-- transaction indexes
denormalize tables by block_number so that we can partition all tables by block_number for purposes of sharding
2022-03-15 21:06:13 +00:00
CREATE INDEX tx_block_number_index ON eth.transaction_cids USING brin (block_number);
revert hash indexes; add eth probes tables
2022-08-30 17:05:51 +00:00
CREATE INDEX tx_header_id_index ON eth.transaction_cids USING btree (header_id);
Add block hash to primary keys in transactions, receipts and logs tables (#100) * Add block hash to primary keys in transactions, receipts and logs tables * Add block hash in postgraphile triggers for transactions, receipts and logs tables * Make indexes on transaction cid and mh_key non-unique
2022-07-07 10:51:06 +00:00
CREATE INDEX tx_cid_index ON eth.transaction_cids USING btree (cid, block_number);
CREATE INDEX tx_mh_block_number_index ON eth.transaction_cids USING btree (mh_key, block_number);
revert hash indexes; add eth probes tables
2022-08-30 17:05:51 +00:00
CREATE INDEX tx_dst_index ON eth.transaction_cids USING btree (dst);
CREATE INDEX tx_src_index ON eth.transaction_cids USING btree (src);
CREATE INDEX tx_data_index ON eth.transaction_cids USING btree (tx_data);
db schema and migrations
2021-08-29 18:55:44 +00:00
-- receipt indexes
denormalize tables by block_number so that we can partition all tables by block_number for purposes of sharding
2022-03-15 21:06:13 +00:00
CREATE INDEX rct_block_number_index ON eth.receipt_cids USING brin (block_number);
revert hash indexes; add eth probes tables
2022-08-30 17:05:51 +00:00
CREATE INDEX rct_header_id_index ON eth.receipt_cids USING btree (header_id);
indexes on receipt cid and mh_key should not be unique, as it is possible (but improbable) that two receipts can be identical
2022-02-16 20:04:57 +00:00
CREATE INDEX rct_leaf_cid_index ON eth.receipt_cids USING btree (leaf_cid);
updates order of columns in compound PKs, update indexes e.g. we don't need a btree index on a column if it is the first column in the compound PK index but we do need a btree index for the later columns in a compound PK (searches on first column of a compound index are just as fast as searches on a btree index for that column alone, but searches on the 2nd or 3rd column in a compound index are significantly slower than on dedicated indexes)
2022-03-28 23:22:57 +00:00
CREATE INDEX rct_leaf_mh_block_number_index ON eth.receipt_cids USING btree (leaf_mh_key, block_number);
revert hash indexes; add eth probes tables
2022-08-30 17:05:51 +00:00
CREATE INDEX rct_contract_index ON eth.receipt_cids USING btree (contract);
db schema and migrations
2021-08-29 18:55:44 +00:00
CREATE INDEX rct_contract_hash_index ON eth.receipt_cids USING btree (contract_hash);
-- state node indexes
denormalize tables by block_number so that we can partition all tables by block_number for purposes of sharding
2022-03-15 21:06:13 +00:00
CREATE INDEX state_block_number_index ON eth.state_cids USING brin (block_number);
db schema and migrations
2021-08-29 18:55:44 +00:00
CREATE INDEX state_cid_index ON eth.state_cids USING btree (cid);
updates order of columns in compound PKs, update indexes e.g. we don't need a btree index on a column if it is the first column in the compound PK index but we do need a btree index for the later columns in a compound PK (searches on first column of a compound index are just as fast as searches on a btree index for that column alone, but searches on the 2nd or 3rd column in a compound index are significantly slower than on dedicated indexes)
2022-03-28 23:22:57 +00:00
CREATE INDEX state_mh_block_number_index ON eth.state_cids USING btree (mh_key, block_number);
revert hash indexes; add eth probes tables
2022-08-30 17:05:51 +00:00
CREATE INDEX state_header_id_index ON eth.state_cids USING btree (header_id);
state_cids and storage_cids only index leaf nodes and related adjustments
2023-01-23 23:08:20 +00:00
CREATE INDEX state_path_index ON eth.state_cids USING btree (state_path);
add removed flag; embed value in storage_cids
2023-01-23 23:12:50 +00:00
CREATE INDEX state_removed_index ON eth.state_cids USING btree (removed);
CREATE INDEX state_code_hash_index ON eth.state_cids USING btree (code_hash); -- could be useful for e.g. selecting all the state accounts with the same contract bytecode deployed
add btree indexes to storage_cids and state_cids node_type; new db schema
2021-09-10 15:12:54 +00:00
db schema and migrations
2021-08-29 18:55:44 +00:00
-- storage node indexes
denormalize tables by block_number so that we can partition all tables by block_number for purposes of sharding
2022-03-15 21:06:13 +00:00
CREATE INDEX storage_block_number_index ON eth.storage_cids USING brin (block_number);
state_cids and storage_cids only index leaf nodes and related adjustments
2023-01-23 23:08:20 +00:00
CREATE INDEX storage_state_leaf_key_index ON eth.storage_cids USING btree (state_leaf_key);
db schema and migrations
2021-08-29 18:55:44 +00:00
CREATE INDEX storage_cid_index ON eth.storage_cids USING btree (cid);
updates order of columns in compound PKs, update indexes e.g. we don't need a btree index on a column if it is the first column in the compound PK index but we do need a btree index for the later columns in a compound PK (searches on first column of a compound index are just as fast as searches on a btree index for that column alone, but searches on the 2nd or 3rd column in a compound index are significantly slower than on dedicated indexes)
2022-03-28 23:22:57 +00:00
CREATE INDEX storage_mh_block_number_index ON eth.storage_cids USING btree (mh_key, block_number);
revert hash indexes; add eth probes tables
2022-08-30 17:05:51 +00:00
CREATE INDEX storage_header_id_index ON eth.storage_cids USING btree (header_id);
state_cids and storage_cids only index leaf nodes and related adjustments
2023-01-23 23:08:20 +00:00
CREATE INDEX storage_path_index ON eth.storage_cids USING btree (state_path);
add removed flag; embed value in storage_cids
2023-01-23 23:12:50 +00:00
CREATE INDEX storage_removed_index ON eth.storage_cids USING btree (removed);
db schema and migrations
2021-08-29 18:55:44 +00:00
new natural primary key scheme
2021-11-15 00:06:02 +00:00
-- access list indexes
denormalize tables by block_number so that we can partition all tables by block_number for purposes of sharding
2022-03-15 21:06:13 +00:00
CREATE INDEX access_list_block_number_index ON eth.access_list_elements USING brin (block_number);
revert hash indexes; add eth probes tables
2022-08-30 17:05:51 +00:00
CREATE INDEX access_list_element_address_index ON eth.access_list_elements USING btree (address);
remove pks; migrations to add back pks and fks
2021-11-18 23:46:50 +00:00
CREATE INDEX access_list_storage_keys_index ON eth.access_list_elements USING gin (storage_keys);
new natural primary key scheme
2021-11-15 00:06:02 +00:00
-- log indexes
denormalize tables by block_number so that we can partition all tables by block_number for purposes of sharding
2022-03-15 21:06:13 +00:00
CREATE INDEX log_block_number_index ON eth.log_cids USING brin (block_number);
revert hash indexes; add eth probes tables
2022-08-30 17:05:51 +00:00
CREATE INDEX log_header_id_index ON eth.log_cids USING btree (header_id);
updates order of columns in compound PKs, update indexes e.g. we don't need a btree index on a column if it is the first column in the compound PK index but we do need a btree index for the later columns in a compound PK (searches on first column of a compound index are just as fast as searches on a btree index for that column alone, but searches on the 2nd or 3rd column in a compound index are significantly slower than on dedicated indexes)
2022-03-28 23:22:57 +00:00
CREATE INDEX log_leaf_mh_block_number_index ON eth.log_cids USING btree (leaf_mh_key, block_number);
new natural primary key scheme
2021-11-15 00:06:02 +00:00
CREATE INDEX log_cid_index ON eth.log_cids USING btree (leaf_cid);
revert hash indexes; add eth probes tables
2022-08-30 17:05:51 +00:00
CREATE INDEX log_address_index ON eth.log_cids USING btree (address);
CREATE INDEX log_topic0_index ON eth.log_cids USING btree (topic0);
CREATE INDEX log_topic1_index ON eth.log_cids USING btree (topic1);
CREATE INDEX log_topic2_index ON eth.log_cids USING btree (topic2);
CREATE INDEX log_topic3_index ON eth.log_cids USING btree (topic3);
CREATE INDEX log_data_index ON eth.log_cids USING btree (log_data);
new natural primary key scheme
2021-11-15 00:06:02 +00:00
db schema and migrations
2021-08-29 18:55:44 +00:00
-- +goose Down
new natural primary key scheme
2021-11-15 00:06:02 +00:00
-- log indexes
misc adjustments
2022-08-08 15:50:27 +00:00
DROP INDEX eth.log_data_index;
new natural primary key scheme
2021-11-15 00:06:02 +00:00
DROP INDEX eth.log_topic3_index;
DROP INDEX eth.log_topic2_index;
DROP INDEX eth.log_topic1_index;
DROP INDEX eth.log_topic0_index;
DROP INDEX eth.log_address_index;
DROP INDEX eth.log_cid_index;
updates order of columns in compound PKs, update indexes e.g. we don't need a btree index on a column if it is the first column in the compound PK index but we do need a btree index for the later columns in a compound PK (searches on first column of a compound index are just as fast as searches on a btree index for that column alone, but searches on the 2nd or 3rd column in a compound index are significantly slower than on dedicated indexes)
2022-03-28 23:22:57 +00:00
DROP INDEX eth.log_leaf_mh_block_number_index;
Add block hash to primary keys in transactions, receipts and logs tables (#100) * Add block hash to primary keys in transactions, receipts and logs tables * Add block hash in postgraphile triggers for transactions, receipts and logs tables * Make indexes on transaction cid and mh_key non-unique
2022-07-07 10:51:06 +00:00
DROP INDEX eth.log_header_id_index;
denormalize tables by block_number so that we can partition all tables by block_number for purposes of sharding
2022-03-15 21:06:13 +00:00
DROP INDEX eth.log_block_number_index;
new natural primary key scheme
2021-11-15 00:06:02 +00:00
-- access list indexes
DROP INDEX eth.access_list_storage_keys_index;
DROP INDEX eth.access_list_element_address_index;
denormalize tables by block_number so that we can partition all tables by block_number for purposes of sharding
2022-03-15 21:06:13 +00:00
DROP INDEX eth.access_list_block_number_index;
new natural primary key scheme
2021-11-15 00:06:02 +00:00
db schema and migrations
2021-08-29 18:55:44 +00:00
-- storage node indexes
add removed flag; embed value in storage_cids
2023-01-23 23:12:50 +00:00
DROP INDEX eth.storage_removed_index;
state_cids and storage_cids only index leaf nodes and related adjustments
2023-01-23 23:08:20 +00:00
DROP INDEX eth.storage_path_index;
updates order of columns in compound PKs, update indexes e.g. we don't need a btree index on a column if it is the first column in the compound PK index but we do need a btree index for the later columns in a compound PK (searches on first column of a compound index are just as fast as searches on a btree index for that column alone, but searches on the 2nd or 3rd column in a compound index are significantly slower than on dedicated indexes)
2022-03-28 23:22:57 +00:00
DROP INDEX eth.storage_header_id_index;
DROP INDEX eth.storage_mh_block_number_index;
db schema and migrations
2021-08-29 18:55:44 +00:00
DROP INDEX eth.storage_cid_index;
DROP INDEX eth.storage_leaf_key_index;
state_cids and storage_cids only index leaf nodes and related adjustments
2023-01-23 23:08:20 +00:00
DROP INDEX eth.storage_state_leaf_key_index;
denormalize tables by block_number so that we can partition all tables by block_number for purposes of sharding
2022-03-15 21:06:13 +00:00
DROP INDEX eth.storage_block_number_index;
db schema and migrations
2021-08-29 18:55:44 +00:00
-- state node indexes
add removed flag; embed value in storage_cids
2023-01-23 23:12:50 +00:00
DROP INDEX eth.state_code_hash_index;
DROP INDEX eth.state_removed_index;
state_cids and storage_cids only index leaf nodes and related adjustments
2023-01-23 23:08:20 +00:00
DROP INDEX eth.state_path_index;
updates order of columns in compound PKs, update indexes e.g. we don't need a btree index on a column if it is the first column in the compound PK index but we do need a btree index for the later columns in a compound PK (searches on first column of a compound index are just as fast as searches on a btree index for that column alone, but searches on the 2nd or 3rd column in a compound index are significantly slower than on dedicated indexes)
2022-03-28 23:22:57 +00:00
DROP INDEX eth.state_header_id_index;
DROP INDEX eth.state_mh_block_number_index;
db schema and migrations
2021-08-29 18:55:44 +00:00
DROP INDEX eth.state_cid_index;
denormalize tables by block_number so that we can partition all tables by block_number for purposes of sharding
2022-03-15 21:06:13 +00:00
DROP INDEX eth.state_block_number_index;
db schema and migrations
2021-08-29 18:55:44 +00:00
-- receipt indexes
DROP INDEX eth.rct_contract_hash_index;
DROP INDEX eth.rct_contract_index;
updates order of columns in compound PKs, update indexes e.g. we don't need a btree index on a column if it is the first column in the compound PK index but we do need a btree index for the later columns in a compound PK (searches on first column of a compound index are just as fast as searches on a btree index for that column alone, but searches on the 2nd or 3rd column in a compound index are significantly slower than on dedicated indexes)
2022-03-28 23:22:57 +00:00
DROP INDEX eth.rct_leaf_mh_block_number_index;
Create a docker image with postgres DB and concise migration.
2021-09-30 12:39:48 +00:00
DROP INDEX eth.rct_leaf_cid_index;
Add block hash to primary keys in transactions, receipts and logs tables (#100) * Add block hash to primary keys in transactions, receipts and logs tables * Add block hash in postgraphile triggers for transactions, receipts and logs tables * Make indexes on transaction cid and mh_key non-unique
2022-07-07 10:51:06 +00:00
DROP INDEX eth.rct_header_id_index;
denormalize tables by block_number so that we can partition all tables by block_number for purposes of sharding
2022-03-15 21:06:13 +00:00
DROP INDEX eth.rct_block_number_index;
db schema and migrations
2021-08-29 18:55:44 +00:00
-- transaction indexes
misc adjustments
2022-08-08 15:50:27 +00:00
DROP INDEX eth.tx_data_index;
db schema and migrations
2021-08-29 18:55:44 +00:00
DROP INDEX eth.tx_src_index;
DROP INDEX eth.tx_dst_index;
updates order of columns in compound PKs, update indexes e.g. we don't need a btree index on a column if it is the first column in the compound PK index but we do need a btree index for the later columns in a compound PK (searches on first column of a compound index are just as fast as searches on a btree index for that column alone, but searches on the 2nd or 3rd column in a compound index are significantly slower than on dedicated indexes)
2022-03-28 23:22:57 +00:00
DROP INDEX eth.tx_mh_block_number_index;
db schema and migrations
2021-08-29 18:55:44 +00:00
DROP INDEX eth.tx_cid_index;
DROP INDEX eth.tx_header_id_index;
denormalize tables by block_number so that we can partition all tables by block_number for purposes of sharding
2022-03-15 21:06:13 +00:00
DROP INDEX eth.tx_block_number_index;
db schema and migrations
2021-08-29 18:55:44 +00:00
new natural primary key scheme
2021-11-15 00:06:02 +00:00
-- uncle indexes
denormalize tables by block_number so that we can partition all tables by block_number for purposes of sharding
2022-03-15 21:06:13 +00:00
DROP INDEX eth.uncle_block_number_index;
updates order of columns in compound PKs, update indexes e.g. we don't need a btree index on a column if it is the first column in the compound PK index but we do need a btree index for the later columns in a compound PK (searches on first column of a compound index are just as fast as searches on a btree index for that column alone, but searches on the 2nd or 3rd column in a compound index are significantly slower than on dedicated indexes)
2022-03-28 23:22:57 +00:00
DROP INDEX eth.uncle_mh_block_number_index;
DROP INDEX eth.uncle_header_id_index;
new natural primary key scheme
2021-11-15 00:06:02 +00:00
db schema and migrations
2021-08-29 18:55:44 +00:00
-- header indexes
DROP INDEX eth.timestamp_index;
DROP INDEX eth.state_root_index;
updates order of columns in compound PKs, update indexes e.g. we don't need a btree index on a column if it is the first column in the compound PK index but we do need a btree index for the later columns in a compound PK (searches on first column of a compound index are just as fast as searches on a btree index for that column alone, but searches on the 2nd or 3rd column in a compound index are significantly slower than on dedicated indexes)
2022-03-28 23:22:57 +00:00
DROP INDEX eth.header_mh_block_number_index;
db schema and migrations
2021-08-29 18:55:44 +00:00
DROP INDEX eth.header_cid_index;
denormalize tables by block_number so that we can partition all tables by block_number for purposes of sharding
2022-03-15 21:06:13 +00:00
DROP INDEX eth.header_block_number_index;
Reference in New Issue Copy Permalink