View Single Post
Old 02-03-2018, 10:37 PM   #6
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,794
Karma: 30237628
Join Date: Mar 2012
Location: Sydney Australia
Device: none
@theducks - I overlooked the dimensions of the issue. But I have done a 'vacuum' on a database that reduced its size by 90%, admittedly that was a high volume TP application for an investment bank using Oracle on a Vaxen cluster. My predecessor was too scared to do any housekeeping of that sort, so it had been churning away 365*24*7 for several years :lol:

Quote:
Originally Posted by jhowell View Post
Some plugins store library-specific data in the database.
I have a vague recollection of a plugin that shovelled the entire text of books into a comments like custom column so it could do fast searches. It may not have been a 'known' plugin (i.e. with an entry in the Index) but one that someone asked me to test.

If you remove a plugin, then it won't remove its library specific data from metadata.db (or its global data from the config plugins directory). The Job Spy plugin has a tool to remove data left behind in library databases by defunct plugins.

BR
BetterRed is online now   Reply With Quote