Add btree index to node_type on state_cids and storage_cids #113

New Issue

i-norden · 2021-09-06T18:55:42Z

i-norden commented

2021-09-06 18:55:42 +00:00

Maybe some additional experimentation should be done to determine if this is worth it. But certain queries against the node_type are very slow, for example if we just want to find an arbitrary "Removed" node (node_type = 4; e.g. SELECT * FROM eth.state_cids WHERE node_type = 4 LIMIT 1;) it takes a long time because "Removed" nodes are very uncommon relative to the other types so the query has to search through a ton of all the other node types to find even one of the "Removed" type.

Maybe some additional experimentation should be done to determine if this is worth it. But certain queries against the `node_type` are very slow, for example if we just want to find an arbitrary "Removed" node (node_type = 4; e.g. `SELECT * FROM eth.state_cids WHERE node_type = 4 LIMIT 1;`) it takes a long time because "Removed" nodes are very uncommon relative to the other types so the query has to search through a ton of all the other node types to find even one of the "Removed" type.

Sign in to join this conversation.

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/go-ethereum#113

Add btree index to node_type on state_cids and storage_cids #113

Add btree index to `node_type` on state_cids and storage_cids #113