aboutsummaryrefslogtreecommitdiff
path: root/src/include/pgstat.h
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2016-03-15 13:31:18 -0400
committerRobert Haas <rhaas@postgresql.org>2016-03-15 13:32:56 -0400
commitc16dc1aca5e01e6acaadfcf38f5fc964a381dc62 (patch)
tree6fa736eac082c521a56151badea923c039ef806a /src/include/pgstat.h
parent0e9b89986b7ced6daffdf14638a25a35c45423ff (diff)
downloadpostgresql-c16dc1aca5e01e6acaadfcf38f5fc964a381dc62.tar.gz
postgresql-c16dc1aca5e01e6acaadfcf38f5fc964a381dc62.zip
Add simple VACUUM progress reporting.
There's a lot more that could be done here yet - in particular, this reports only very coarse-grained information about the index vacuuming phase - but even as it stands, the new pg_stat_progress_vacuum can tell you quite a bit about what a long-running vacuum is actually doing. Amit Langote and Robert Haas, based on earlier work by Vinayak Pokale and Rahila Syed.
Diffstat (limited to 'src/include/pgstat.h')
-rw-r--r--src/include/pgstat.h2
1 files changed, 2 insertions, 0 deletions
diff --git a/src/include/pgstat.h b/src/include/pgstat.h
index e7fbf1e3926..1fc45acc239 100644
--- a/src/include/pgstat.h
+++ b/src/include/pgstat.h
@@ -978,6 +978,8 @@ extern const char *pgstat_get_crashed_backend_activity(int pid, char *buffer,
extern void pgstat_progress_start_command(ProgressCommandType cmdtype,
Oid relid);
extern void pgstat_progress_update_param(int index, int64 val);
+extern void pgstat_progress_update_multi_param(int nparam, const int *index,
+ const int64 *val);
extern void pgstat_progress_end_command(void);
extern PgStat_TableStatus *find_tabstat_entry(Oid rel_id);