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

Current state mode #29

Open
linuskendall opened this issue Jun 22, 2022 · 0 comments
Open

Current state mode #29

linuskendall opened this issue Jun 22, 2022 · 0 comments

Comments

@linuskendall
Copy link

Currently you need to activate historical data storage to be able to run the RPC server (https://github.com/lijunwangs/solana-postgres-rpc-server) as it can otherwise not return the correct commitment level data. If the intention is to use the postgres-rpc-server as an RPC replacement/frontend then this leads to the unfortunate challenge of having to store much more data than required.

To function properly for the RPC server we only really need to store three copies of each write:

  • Latest write (accounts)
  • Up to two additional writes for confirmed and finalized commitment levels (accounts_audit)

Proposed solution:

Have an option to upsert/overwrite the accounts_audit entries. Perhaps we could use a separate trigger for this that instead of insert does an upsert?

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

No branches or pull requests

1 participant