You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/quick-reference.md
-12Lines changed: 0 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,18 +59,6 @@ You have some control over which peers you're connected to:
59
59
* the `connect` command asks the instance to connect to a specific peer.
60
60
* the `droppeer` command asks the instance to drop the connection with a specific peer.
61
61
62
-
### Maintenance
63
-
64
-
Core keeps historical data needed for publish (such as SCP history)
65
-
66
-
Sometimes you need to clean up more than this (for example, if you have a large maintenance debt).
67
-
In this case running the command `maintenance?count=100000000` (integer is a large number, bigger than your max backlog) will perform the full maintenance.
68
-
69
-
Note that this may hang the instance for minutes (hours even).
70
-
71
-
After performing such maintenance, you may issue a postgres `VACUUM FULL;` that will reclaim all
72
-
disk space (note that this requires a lot of free disk space).
73
-
74
62
### Testing
75
63
76
64
The `manualclose` command allows to close a ledger, this is used when the instance is
0 commit comments