Data Monitoring / PostgreSQL Monitoring
PostgreSQL: Statement counter reset boundaries
Per-query rates spike after statistics are reset. Record the statistics reset time and compare consecutive counters only within a continuous series.
Environment and inputs: PostgreSQL 18 documentation baseline; views, extensions and permissions vary across versions and managed services.
Failure scenario
Per-query rates spike after statistics are reset. Confirm the cause before choosing a fix.
Evidence to collect
Record the statistics reset time and compare consecutive counters only within a continuous series. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Discard invalid deltas across resets and label the monitoring discontinuity. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for statement counter reset boundaries using the same scope and a representative interval. Check that the symptom is resolved, expected records are present and downstream results are correct. If coverage, correctness or latency worsens, restore the recorded configuration through the agreed rollback process.
Scope and precautions
Prefer read-only access and limit queries to the relevant period or dataset. This example has not been tested on your systems. Test changes in an approved environment. Keep credentials and sensitive data out of shared evidence.