Fix typos in comments

Commit 19d8e2308bc added enum values with the prefix TU_, but a few
comments still referred to TUUI_, which was used in development
versions of the patches committed as 19d8e2308bc.

Author: Yugo Nagata 
Discussion: https://postgr.es/m/20250701110216.8ac8a9e4c6f607f1d954f44a@sraoss.co.jp
Backpatch-through: 16

diff --git a/src/backend/executor/execIndexing.c b/src/backend/executor/execIndexing.c
index bdf862b24062e74e0fd99c9adaa3416bebc6ea8c..ca33a854278eda8a6e1b922f31063d0946626a64 100644 (file)
--- a/src/backend/executor/execIndexing.c
+++ b/src/backend/executor/execIndexing.c
@@ -279,7 +279,7 @@ ExecCloseIndices(ResultRelInfo *resultRelInfo)
  *     executor is performing an UPDATE that could not use an
  *     optimization like heapam's HOT (in more general terms a
  *     call to table_tuple_update() took place and set
- *     'update_indexes' to TUUI_All).  Receiving this hint makes
+ *     'update_indexes' to TU_All).  Receiving this hint makes
  *     us consider if we should pass down the 'indexUnchanged'
  *     hint in turn.  That's something that we figure out for
  *     each index_insert() call iff 'update' is true.
@@ -290,7 +290,7 @@ ExecCloseIndices(ResultRelInfo *resultRelInfo)
  *     HOT has been applied and any updated columns are indexed
  *     only by summarizing indexes (or in more general terms a
  *     call to table_tuple_update() took place and set
- *     'update_indexes' to TUUI_Summarizing). We can (and must)
+ *     'update_indexes' to TU_Summarizing). We can (and must)
  *     therefore only update the indexes that have
  *     'amsummarizing' = true.
  *