View Single Post
Old 07-29-2022, 07:53 AM   #3
DrChiper
Bookish
DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.
 
DrChiper's Avatar
 
Posts: 1,029
Karma: 2003162
Join Date: Jun 2011
Device: PC, t1, t2, t3, Clara BW, Clara HD, Libra 2, Libra Color, Nxtpaper 11
Hmmm, what I witnessed: full-text-search.db is not vacuumed when applying the normal DB maintenance.

What did I do: I copied the full-text-search.db to another location, noted its size and applied vacuum via SQLiteSpy (1.9.16) which took some time to compress it slightly. That indicated to me that full-text-search.db would likely to be a vacuum candidate.

Thereafter I fired-up calibre, choose maintenance (=Check Library) and saw the metadata.db being vacuumed after a short time, while file full-text-search.db was never touched. The short time it took was also an indication.

I'm currently using calibre 6.2. Did I applied the maintenance correctly?
DrChiper is offline   Reply With Quote