Bodobolero/test cum stats persistence

[Bodobolero]

Problem

So far cumulative statistics have not been persisted when Neon scales to zero (suspends endpoint).
With PR #6560 the cumulative statistics should now survive endpoint restarts and correctly trigger the auto- vacuum and auto analyze maintenance

So far we did not have a testcase that validates that improvement in our dev cloud environment with a real project.

Summary of changes

Introduce testcase test_cumulative_statistics_persistencein the benchmarking workflow running daily to verify:

• Verifies that the cumulative statistics are correctly persisted across restarts.
• Cumulative statistics are important to persist across restarts because they are used
• when auto-vacuum an auto-analyze trigger conditions are met.
• The test performs the following steps:
  • Seed a new project using pgbench
  • insert tuples that by itself are not enough to trigger auto-vacuum
  • suspend the endpoint
  • resume the endpoint
  • insert additional tuples that by itself are not enough to trigger auto-vacuum but in combination with the previous tuples are
  • verify that autovacuum is triggered by the combination of tuples inserted before and after endpoint suspension

Test run

/~https://github.com/neondatabase/neon/actions/runs/13546879714/job/37860609089#step:6:282

[github-actions]

7744 tests run: 7365 passed, 0 failed, 379 skipped (full report)

---

Flaky tests (4)

Postgres 17

• test_tx_abort_with_many_relations[v2]: release-x86-64-with-lfc, release-arm64-without-lfc
• test_s3_wal_replay[local_fs]: release-arm64-with-lfc

Postgres 15

• test_pageserver_gc_compaction_idempotent[after_restart]: release-x86-64-with-lfc

Code coverage* (full report)

• functions: 32.8% (8632 of 26347 functions)
• lines: 48.6% (73078 of 150346 lines)

* collected from Rust tests only

---

_{The comment gets automatically updated with the latest test results
f6c5134 at 2025-02-26T16:30:55.518Z :recycle:}

[alexanderlaw]

This test looks good to me in general.