Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Commit

Permalink
Document that you shouldn't VACUUM between port runs
Browse files Browse the repository at this point in the history
  • Loading branch information
reivilibre committed Jul 6, 2022
1 parent 25d11fc commit cacd103
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions docs/postgres.md
Original file line number Diff line number Diff line change
Expand Up @@ -143,6 +143,14 @@ to do step 2.

It is safe to at any time kill the port script and restart it.

However, under no circumstances should the SQLite database be `VACUUM`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 `auto_vacuum` mechanism
is disabled, but the script is not able to protect against a manual `VACUUM` operation
performed either by the administrator or by any automated task that the administrator
may have configured.

Note that the database may take up significantly more (25% - 100% more)
space on disk after porting to Postgres.

Expand Down

0 comments on commit cacd103

Please sign in to comment.