Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Write directly to Postgres #15

Closed
i-norden opened this issue Nov 9, 2020 · 4 comments · Fixed by #16
Closed

Write directly to Postgres #15

i-norden opened this issue Nov 9, 2020 · 4 comments · Fixed by #16
Assignees

Comments

@i-norden
Copy link
Collaborator

i-norden commented Nov 9, 2020

To avoid the rate limiting issues we are experiencing by proceeding through the go-ethereum RPC server interfaces (e.g. EOFs) we should have an option to write statediffs directly to Postgres, directly analogous to cerc-io/go-ethereum#30

We should be able to operate it in two modes:

  1. Load the desired ranges from the .toml params, index statediffs from LevelDB directly into Postgres for the blocks in those ranges, and exit
  2. Service runs indefinitely, awaiting RPC calls which tell it which historical blocks for which to index statediffs from LevelDB directly into Postgres
@i-norden
Copy link
Collaborator Author

More info in #11

@roysc
Copy link
Contributor

roysc commented Nov 13, 2020

Do we want to be able to specify multiple ranges in the config? Or just start/stop like for resync?

@roysc roysc mentioned this issue Nov 16, 2020
1 task
@i-norden
Copy link
Collaborator Author

i-norden commented Dec 2, 2020

@roysc sorry for missing that, ideally we would be able to specify multiple ranges but starting with a single start/stop is fine for now

@roysc
Copy link
Contributor

roysc commented Dec 3, 2020

No worries - this implementation does work with multiple ranges

@roysc roysc closed this as completed in #16 Dec 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants