Skip to content
This repository has been archived by the owner on Aug 31, 2021. It is now read-only.

Stored Forked Blocks in Postgres #11

Open
mkrump opened this issue Jan 30, 2018 · 1 comment
Open

Stored Forked Blocks in Postgres #11

mkrump opened this issue Jan 30, 2018 · 1 comment

Comments

@mkrump
Copy link
Contributor

mkrump commented Jan 30, 2018

Geth drops blocks that are forked. Instead of dropping these blocks we want to store them in a separate postgres table.

elizabethengelman pushed a commit that referenced this issue Oct 30, 2018
Add Postgraphile subscription exposure for price feed
i-norden pushed a commit that referenced this issue Apr 9, 2019
i-norden pushed a commit that referenced this issue Apr 18, 2019
Add Postgraphile subscription exposure for price feed
i-norden pushed a commit that referenced this issue Apr 18, 2019
@i-norden
Copy link
Collaborator

Super Node will persist any forked blocks the node it is syncing from streams out. More specifically, it publishes and indexes all blocks that Geth syncs at its head, where reorgs can still occur. There is no explicit indication in the Super Node db or on IPFS that a block is a forked block- this must be reasoned about by the greater context.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants