@15066d8d Right now I'm mostly just running a script that @9046526e wrote to delete remote files older than 3 weeks. Beyond that, I think PostgreSQL performs autovacuum by default? I don't know, unsure how to really check and find out. Something more to research/read about when I get some extended downtime on my computer.
Otherwise, I occasionally run VACUUM ANALYZE manually. Might be nice to combine the script you made for pg_dump with one that can perform VACUUM ANALYZE so that the database gets dumped, vacuumed, and analyzed daily + older files get pruned daily + the server reboots daily (right now all my VMs reboot daily). @67975218 @jaf
@b17a3b4f @9046526e @67975218 @jaf
Only run full vacuums once in a while when you wanna reclaim disk space
@15066d8d I've never once yet run a VACUUM FULL and I've been warned against its utilization in general, outside of extraordinary circumstances. @9046526e @67975218 @jaf
@15066d8d @b17a3b4f @67975218 @jaf Yes, full vacuum is slow and explicite locks the table while it's working on it, meaning for example, can't record new notes in the database. So be careful with that.
@9046526e Whenever I run VACUUM ANALYZE and pg_dump I stop Misskey so that no activity is taking place while PostgreSQL does it's things. @15066d8d @67975218 @jaf
Oddbean new post about login | logout