From 40e8c89908dd4e0852a2758809812e60d235f710 Mon Sep 17 00:00:00 2001
From: Jean-Paul Calderone <exarkun@twistedmatrix.com>
Date: Wed, 2 Feb 2022 14:31:07 -0500
Subject: [PATCH] mention [event-stream] handling wrt snapshot creation
---
docs/source/designs/backup-recovery.rst | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/docs/source/designs/backup-recovery.rst b/docs/source/designs/backup-recovery.rst
index bfa6855..998b5de 100644
--- a/docs/source/designs/backup-recovery.rst
+++ b/docs/source/designs/backup-recovery.rst
@@ -222,7 +222,7 @@ A replica consists of the following pieces of state:
A snapshot the minimal sequence of SQL statements
(with arguments embedded)
- which will re-create the database from which it was created.
+ which will re-create the database from which it was created [10]_.
A snapshot can be produced using the ``iterdump`` feature of the Python SQLite3 module.
#. an event stream
@@ -253,6 +253,11 @@ The event stream is represented in the local database in a new table::
Arguments are substituted into the statement so that they match the form of statements generated during the *snapshot* phase.
+.. [10] Rows in the ``[event-stream]`` table are always excluded from the snapshot.
+ They are not needed for recovery.
+ The state they represent is always reflected elsewhere in the database.
+ The DDL statements for ``[event-stream]`` *are* included.
+
Replication
~~~~~~~~~~~
--
GitLab