The database maintenance tasks doc says you shouldn’t (and/or shouldn’t need to) regularly run a vacuum when pruning objects, but it doesn’t say how frequently a prune_objects task should be run. I’m currently digging my server out after letting it go too long between pruning tasks, and I’m wondering: once I get things back to “normal” is it safe to put this task in cron (omitting --vacuum) and let it run daily/weekly, or is there some reason not to do that?
Also while I’m asking, a related question: is it possible to set the log level just for a single task? I normally set my server log level to error, but I’d like it to be info for this task so I can actually see what it’s doing.
im not sure if there’s really a how frequent it should run, but i run it on a weekly basis using cron.
1 Like
We are talking about Database maintenance tasks - Akkoma Documentation right?
Why not use the config value and have Akkoma do the pruning itself? Or am I missing something?
Or is the config value only for the length and it still needs to be triggered manually?
It still needs to be triggered manually (or scheduled in cron), but it uses the “Remote post retention days” configuration value visible on the Instance page. I had been pretty good about running it whenever I happened to remember it, but it turns out that I hadn’t happened to remember it for far too long.