Gonna do a vacuum full on the database with pg_repack.
This shouldn't cause any downtime but it might. We'll just have to see. You might notice degraded performance tho.
So I can get a good comparison here's the size of my database before the vacuum full.
#BaestNews #BigData
Screenshot_20220927-122406.png
This shouldn't cause any downtime but it might. We'll just have to see. You might notice degraded performance tho.
So I can get a good comparison here's the size of my database before the vacuum full.
#BaestNews #BigData
Screenshot_20220927-122406.png
About ½ of the way done rebuilding the activities table. Then it'll just have to keep it in sync, rebuild the indexes, and drop in the new table. Then it'll move onto the other tables.
Screenshot_20220927-125803.png
Screenshot_20220927-125803.png
We are currently building the indexes on the temporary activities table whilst keeping it in sync with the live activities table before swapping in the temporary table and deleting the old live table.
I apologise for the degraded performance but this should improve performance in the near future.
#BaestNews
@UncleIroh
Screenshot_20220927-150010.png
I apologise for the degraded performance but this should improve performance in the near future.
#BaestNews
@UncleIroh
Screenshot_20220927-150010.png
@UncleIroh we're about halfway through creating all the indexes for the activities table
Screenshot_20220927-151837.png
Screenshot_20220927-151837.png
@sjw@bae.st @UncleIroh Alright, we've made it through the activities table (and a few other tables) and now we're on the smaller of the two god tables, the objects table.
We're currently cloning the table and then we'll build the indexes.
This table is proving be even more of a pain because it's kind of the ultimate god table in the database.
Should at least be faster tho.
@sjw@bae.st
@sjw @UncleIroh we have about 25 GB of indexes left to build on the objects table but things at least seem to be stable now.
