diff --git a/docs/source/designs/backup-recovery.rst b/docs/source/designs/backup-recovery.rst index a0d186ea2f3bed2e9522fac8d5027d9d05783984..046b6f402d406dacd3962cea8da2739fa32057bf 100644 --- a/docs/source/designs/backup-recovery.rst +++ b/docs/source/designs/backup-recovery.rst @@ -145,7 +145,7 @@ ZKAPAuthorizer itself could write a log of all SQL it executes against the SQLit This log could be uploaded to the backup location. This log will be smaller than new copies of the database and save on bandwidth and storage. -This non-trivial implementation work in ZKAPAuthorizer to capture the stream of SQL statements +This involves non-trivial implementation work in ZKAPAuthorizer to capture the stream of SQL statements (including values of parameters). It is likely also sensitive to changes made outside of the control of the ZKAPAuthorizer implementation - though less sensitive than the WAL-based approach.