VACUUM INTO fits really well into the general use case of "I need a persistent, read-only backup that is as small as possible". Only issue was that it used to not call fsync, so you could think you have a backup safely secured on disk and then find out after a hard power cycle that it was not actually there (great times!).
Anyhow this was fixed 3.45.1 SQLite and as of writing we are at 3.38.5 SQLite
sqlite/sqlite@80b30f9
The SQLite Forum post about this is here (with recent entries explaining how the documentation could use some work)
https://sqlite.org/forum/info/8c83764a7355f6cc8208cdf96e533dd2f91f939770c193d20980fa45140e8908
Closing note, looks like @crawshaw is a fan of VACUUM INTO as well:
#36 (comment)
VACUUM INTOfits really well into the general use case of "I need a persistent, read-only backup that is as small as possible". Only issue was that it used to not callfsync, so you could think you have a backup safely secured on disk and then find out after a hard power cycle that it was not actually there (great times!).Anyhow this was fixed
3.45.1SQLite and as of writing we are at3.38.5SQLitesqlite/sqlite@80b30f9
The SQLite Forum post about this is here (with recent entries explaining how the documentation could use some work)
https://sqlite.org/forum/info/8c83764a7355f6cc8208cdf96e533dd2f91f939770c193d20980fa45140e8908
Closing note, looks like @crawshaw is a fan of
VACUUM INTOas well:#36 (comment)