Re: per backend WAL statistics

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>
To: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2025-01-10T00:14:45Z
Lists: pgsql-hackers
On Thu, Jan 09, 2025 at 07:05:54AM +0000, Bertrand Drouvot wrote:
> PFA v3 which is v2 refactoring with your proposed above changes.

An extra thing I have finished by doing is removing
PgStat_BackendPendingIO, then applied the change.  It was useful when
returned as a result of pgstat_prep_backend_pending(), but not so much
with the new PgStat_BackendPending that includes all the pending stats
data.
--
Michael

Commits

  1. Fix use-after-free in pgstat_fetch_stat_backend_by_pid()

  2. Remove initialization from PendingBackendStats

  3. Add WAL data to backend statistics

  4. Improve check for detection of pending data in backend statistics

  5. Fix some gaps in pg_stat_io with WAL receiver and WAL summarizer

  6. Handle auxiliary processes in SQL functions of backend statistics

  7. Invent pgstat_fetch_stat_backend_by_pid()

  8. Refactor code of pg_stat_get_wal() building result tuple

  9. Adding new PgStat_WalCounters structure in pgstat.h

  10. Remove pgstat_flush_wal()

  11. Refactor some code related to backend statistics

  12. Add backend-level statistics to pgstats