From: Bruce Momjian Date: Mon, 17 Oct 2022 19:07:02 +0000 (-0400) Subject: doc: warn pg_stat_reset() can cause vacuum/analyze problems X-Git-Tag: REL_11_18~16 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=5f9372028bd8e6b4f71425c1a64ec2cf528533b8;p=thirdparty%2Fpostgresql.git doc: warn pg_stat_reset() can cause vacuum/analyze problems The fix is to run ANALYZE. Discussion: https://postgr.es/m/YzRr+ys98UzVQJvK@momjian.us, https://postgr.es/m/flat/CAKJS1f8DTbCHf9gedU0He6ARsd58E6qOhEHM1caomqj_r9MOiQ%40mail.gmail.com, https://postgr.es/m/CAKJS1f80o98hcfSk8j%3DfdN09S7Sjz%2BvuzhEwbyQqvHJb_sZw0g%40mail.gmail.com Backpatch-through: 10 --- diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index 9ba8eeea46b..87e2a91da51 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -3190,6 +3190,17 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i + + + Using pg_stat_reset() also resets counters that + autovacuum uses to determine when to trigger a vacuum or an analyze. + Resetting these counters can cause autovacuum to not perform necessary + work, which can cause problems such as table bloat or out-dated + table statistics. A database-wide ANALYZE is + recommended after the statistics have been reset. + + + pg_stat_get_activity, the underlying function of the pg_stat_activity view, returns a set of records