| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: doc: Mention pg_stat_force_next_flush() |
| Date: | 2026-09-10 04:23:41 |
| Message-ID: | E1x4WK4-00000004EKP-3FT5@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
doc: Mention pg_stat_force_next_flush()
pg_stat_force_next_flush() has primarily been used in in-core tests to
force cumulative statistics to be flushed at the end of a transaction
without waiting for the PGSTAT_MIN_INTERVAL throttle, to speed up
things.
It is also useful in tests outside the core tree. Spoiler: I have used
it myself for some out-of-core work for the same reason as the in-core
tests, and would have unlikely known about it without my work on the
core code.
Author: Sami Imseih <samimseih(dot)pg(at)gmail(dot)com>
Discussion: https://postgr.es/m/aqEONVuLhgBiqHW6@paquier.xyz
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/c8985a09b7b52519f794c433e5f8f7311a77a2fc
Modified Files
--------------
doc/src/sgml/monitoring.sgml | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2026-09-10 04:34:53 | pgsql: Take RI fast-path snapshot after locking referenced relation |
| Previous Message | Michael Paquier | 2026-09-10 04:11:22 | pgsql: pgbench: Improve handling of NULL in \gset and \aset |