pgsql: Fix progress reporting of CLUSTER / VACUUM FULL - Mailing list pgsql-committers

From Alvaro Herrera
Subject pgsql: Fix progress reporting of CLUSTER / VACUUM FULL
Date
Msg-id E1i8pqS-0003NO-7l@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
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

Branch
------
REL_12_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/da47e43dc32e3c5916396f0cbcfa974b371e4875

Modified Files
--------------
src/backend/catalog/index.c      | 24 +++++++++++++++---------
src/backend/commands/indexcmds.c |  4 ++--
src/include/nodes/parsenodes.h   |  1 +
3 files changed, 18 insertions(+), 11 deletions(-)


pgsql-committers by date:

Previous
From: Alexander Korotkov
Date:
Subject: pgsql: Documentation improvements to jsonpath
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Fix progress reporting of CLUSTER / VACUUM FULL