gaspersic/solana
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed issue #22124 -- missing historical data if slot updated later. (#22193) (#22259)

Browse Source 
* Fixed issue #22124 -- missing historical data if slot updated later.

* Fixed a couple of comments

(cherry picked from commit 5b6027bef0)

Co-authored-by: Lijun Wang <83639177+lijunwangs@users.noreply.github.com>
This commit is contained in:
mergify[bot]
2022-01-04 07:18:58 +00:00
committed by GitHub
parent 464d533da3
commit 77558c315d
3 changed files with 95 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/src/developing/plugins/accountsdb_plugin.md
View File

@ -381,8 +381,11 @@ psql -U solana -p 5433 -h 10.138.0.9 -w -d solana -f drop_schema.sql
### Capture Historical Account Data
The account historical data is captured using a database trigger as shown in
`create_schema.sql`,
To capture account historical data, in the configuration file, turn
`store_account_historical_data` to true.
And ensure the database trigger is created to save data in the `audit_table` when
records in `account` are updated, as shown in `create_schema.sql`,
```
CREATE FUNCTION audit_account_update() RETURNS trigger AS $audit_account_update$
@ -399,11 +402,8 @@ CREATE TRIGGER account_update_trigger AFTER UPDATE OR DELETE ON account
FOR EACH ROW EXECUTE PROCEDURE audit_account_update();
```
The historical data is stored in the account_audit table.
The trigger can be dropped to disable this feature, for example,
```
DROP TRIGGER account_update_trigger ON account;
```
@ -411,7 +411,6 @@ DROP TRIGGER account_update_trigger ON account;
Over time, the account_audit can accumulate large amount of data. You may choose to
limit that by deleting older historical data.
For example, the following SQL statement can be used to keep up to 1000 of the most
recent records for an account: