From 6212276e4343f729b0152e81824f850d1a21d57e Mon Sep 17 00:00:00 2001
From: Alvaro Herrera
Date: Fri, 13 Sep 2019 14:51:13 -0300
Subject: Fix progress reporting of CLUSTER / VACUUM FULL

The progress state was being clobbered once the first index completed
being rebuilt, causing the final phases of the operation not show
anything in the progress view.  This was inadvertently broken in
03f9e5cba0ee, which added progress tracking for REINDEX.

(The reason this bugfix is this small is that I had already noticed this
problem when writing monitoring for CREATE INDEX, and had already worked
around it, as can be seen in discussion starting at
https://postgr.es/m/20190329150218.GA25010@alvherre.pgsql Fixing the
problem is just a matter of fixing one place touched by the REINDEX
monitoring.)

Reported by: Álvaro Herrera
Author: Álvaro Herrera
Discussion: https://postgr.es/m/20190801184333.GA21369@alvherre.pgsql
---
 src/include/nodes/parsenodes.h | 1 +
 1 file changed, 1 insertion(+)

(limited to 'src/include/nodes')

diff --git a/src/include/nodes/parsenodes.h b/src/include/nodes/parsenodes.h
index f21ff8028a1..bb931b2cacf 100644
--- a/src/include/nodes/parsenodes.h
+++ b/src/include/nodes/parsenodes.h
@@ -3313,6 +3313,7 @@ typedef struct ConstraintsSetStmt
 
 /* Reindex options */
 #define REINDEXOPT_VERBOSE 1 << 0	/* print progress info */
+#define REINDEXOPT_REPORT_PROGRESS 1 << 1	/* report pgstat progress */
 
 typedef enum ReindexObjectType
 {
-- 
cgit v1.2.3