re-analyze all tables affected by new indexes

packages/backend/migration/1748104955717-index_IDX_instance_host_key.js

@@ -8,10 +8,6 @@ export class IndexIDXInstanceHostKey1748104955717 {
 
 	async up(queryRunner) {
 		await queryRunner.query(`CREATE UNIQUE INDEX "IDX_instance_host_key" ON "instance" (((lower(reverse("host")) || '.')::text) text_pattern_ops)`);
-
-		// Flush all cached Linear Scan Plans and redo statistics for expression index
-		// this is important for Postgres to learn that even in highly complex queries, using this index first can reduce the result set significantly
-		await queryRunner.query(`ANALYZE "instance"`);
 	}
 
 	async down(queryRunner) {

packages/backend/migration/1748191631151-analyze_instance-user-note-following.js

@@ -0,0 +1,25 @@
+/*
+ * SPDX-FileCopyrightText: hazelnoot and other Sharkey contributors
+ * SPDX-License-Identifier: AGPL-3.0-only
+ */
+
+/**
+ * @typedef {import('typeorm').MigrationInterface} MigrationInterface
+ */
+
+/**
+ * @class
+ * @implements {MigrationInterface}
+ */
+export class AnalyzeInstanceUserNoteFollowing1748191631151 {
+	name = 'AnalyzeInstanceUserNoteFollowing1748191631151'
+
+	async up(queryRunner) {
+		// Refresh statistics for tables impacted by new indexes.
+		// This helps the query planner to efficiently use them without waiting for the next full vacuum.
+		await queryRunner.query(`ANALYZE "instance", "user", "following", "note"`);
+	}
+
+	async down(queryRunner) {
+	}
+}