From 79c12e8ee62b5654c27d763b0446165cac98b606 Mon Sep 17 00:00:00 2001
From: reivilibre <reivilibre@users.noreply.github.com>
Date: Thu, 7 Jul 2022 10:08:48 +0000
Subject: deploy: fb7d24ab6de870ab21f83d49d9f1db569eff4b56

---
 develop/postgres.html | 7 +++++++
 1 file changed, 7 insertions(+)

(limited to 'develop/postgres.html')

diff --git a/develop/postgres.html b/develop/postgres.html
index 7f70667c19..780604462a 100644
--- a/develop/postgres.html
+++ b/develop/postgres.html
@@ -267,6 +267,13 @@ of the SQLite database file. This makes it safe to repeat step 1 if
 there was a delay between taking the previous snapshot and being ready
 to do step 2.</p>
 <p>It is safe to at any time kill the port script and restart it.</p>
+<p>However, under no circumstances should the SQLite database be <code>VACUUM</code>ed between
+multiple runs of the script. Doing so can lead to an inconsistent copy of your database
+into Postgres.
+To avoid accidental error, the script will check that SQLite's <code>auto_vacuum</code> mechanism
+is disabled, but the script is not able to protect against a manual <code>VACUUM</code> operation
+performed either by the administrator or by any automated task that the administrator
+may have configured.</p>
 <p>Note that the database may take up significantly more (25% - 100% more)
 space on disk after porting to Postgres.</p>
 <h3 id="using-the-port-script"><a class="header" href="#using-the-port-script">Using the port script</a></h3>
-- 
cgit 1.5.1