No-UPSERT mode #299

Closed
opened 2023-01-10 02:57:15 +00:00 by i-norden · 0 comments
Member

We currently ON CONFLICT DO UPDATE SET for a few tables (eth.header_cids, eth.state_cids, eth.storage_cids). For state_cids and storage_cids this is unnecessary here with the current natural primary key scheme. For header_cids it is only necessary in order to increment the times_validated (times seen) counter.

As a dependency in eth-statediff-service it will continue to be useful to be able to upsert to these (and other) tables in certain situations, so this mode can be toggled on and off at the indexer level.

We currently `ON CONFLICT DO UPDATE SET` for a few tables (`eth.header_cids`, `eth.state_cids`, `eth.storage_cids`). For `state_cids` and `storage_cids` this is unnecessary here with the current natural primary key scheme. For `header_cids` it is only necessary in order to increment the `times_validated` (times seen) counter. As a dependency in eth-statediff-service it will continue to be useful to be able to upsert to these (and other) tables in certain situations, so this mode can be toggled on and off at the indexer level.
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#299
No description provided.