aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2019-12-15 22:05:33 +0900
committerMichael Paquier <michael@paquier.xyz>2019-12-15 22:05:33 +0900
commite5a02e0fc68bd57048f2c74a89f5412dbf87015e (patch)
tree8b6efcbd3b2e7d7a1640f06b935bc75e7f53c9cb
parentbaa32ce28b39eccdf384e979dac5ad8be91ff44e (diff)
downloadpostgresql-e5a02e0fc68bd57048f2c74a89f5412dbf87015e.tar.gz
postgresql-e5a02e0fc68bd57048f2c74a89f5412dbf87015e.zip
Remove duplicated progress reporting during heap scan of VACUUM
This has been introduced by c16dc1a since progress reporting for VACUUM has been added. As this issue just causes some extra work and is harmless, no backpatch is done. Author: Justin Pryzby Discussion: https://postgr.es/m/20191213030831.GT2082@telsasoft.com
-rw-r--r--src/backend/access/heap/vacuumlazy.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/src/backend/access/heap/vacuumlazy.c b/src/backend/access/heap/vacuumlazy.c
index a3c4a1df3b4..ab09d8408cc 100644
--- a/src/backend/access/heap/vacuumlazy.c
+++ b/src/backend/access/heap/vacuumlazy.c
@@ -1445,8 +1445,6 @@ lazy_scan_heap(Relation onerel, VacuumParams *params, LVRelStats *vacrelstats,
pgstat_progress_update_multi_param(2, hvp_index, hvp_val);
/* Remove tuples from heap */
- pgstat_progress_update_param(PROGRESS_VACUUM_PHASE,
- PROGRESS_VACUUM_PHASE_VACUUM_HEAP);
lazy_vacuum_heap(onerel, vacrelstats);
vacrelstats->num_index_scans++;
}