Open
Description
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?
Metadata
Metadata
Assignees
Labels
No labels