Is the vacuum necessary?

[Alexey]

@SGC

meaning that the next time something is changed, it will not be written inside the database… then it would be written behind the sequentially written database file, which is… data fragmentation… which is exactly what you are trying to avoid…

You perfectly right. It will happen again. And can be worse than before the vacuum. But can temporary fix the problem (or more like shift it to the future).

This is why @littleskunk mentioned

@littleskunk

Why do we have to call vacuum? That shouldn’t be needed. Autovacuum should also not be needed. It could be a problem with the go sqlite driver.