docs(2meet-data-optimizer): correct the 1.4.0 upgrade step for the copy index

- Replace the index only on tables listed in tmdo_post_status_columns (ALTER ADD idx_post_status_date_id / DROP idx_post_status_date) - Warn that `wp tmdo post-status-sync` also adds and backfills copy columns on every other post group (large ALTER + UPDATE) - Found in the 2.4 rollout (dev21: aeav_only, over ten million posts)
2026-09-28 00:03:02 +08:00
parent b30baeddf0
commit 4b34851316
2 changed files with 9 additions and 5 deletions
@@ -110,7 +110,7 @@ The Classifier tab analyzes your existing `wp_postmeta` data (access frequency,
 = 1.4.0 =
 * Flat-first sorts read the ID tie-break from the flat post_id, so a declared (column, post_id) index returns rows in order; ties now follow the sort direction
 * Meta clauses without a value route as EXISTS; HivePress's featured-listing lookup on every search page uses the flat table
-* Date-ordered routed searches drop the redundant GROUP BY and use a (post_status, post_date, post_id) index (run `wp tmdo post-status-sync` once to replace the index)
+* Date-ordered routed searches drop the redundant GROUP BY and use a (post_status, post_date, post_id) index (replace the index on the tables listed in `tmdo_post_status_columns`; `wp tmdo post-status-sync` also adds the copy columns to every other post group)
 * Rows rebuilt by the migration engine keep their status/date copies and invalidate cached routed counts
 * Live test tools no longer flush the object cache