Show record information in pg_get_wal_block_info.
commit122376f028a0e31b91d6c6bad2a9a6e994708547
authorPeter Geoghegan <pg@bowt.ie>
Thu, 30 Mar 2023 19:26:12 +0000 (30 12:26 -0700)
committerPeter Geoghegan <pg@bowt.ie>
Thu, 30 Mar 2023 19:26:12 +0000 (30 12:26 -0700)
tree80f66eee8ab43467c7690383a5bf6a1a7975c36a
parent63cc20205c1a0022d808a783b3025029bb09101e
Show record information in pg_get_wal_block_info.

Expand the output parameters in pg_walinspect's pg_get_wal_block_info
function to return additional information that was previously only
available from pg_walinspect's pg_get_wal_records_info function.  Some
of the details are attributed to individual block references, rather
than aggregated into whole-record values, since the function returns one
row per block reference per WAL record (unlike pg_get_wal_records_info,
which always returns one row per WAL record).

This structure is much easier to work with when writing queries that
track how individual blocks changed over time, or when attributing costs
to individual blocks (not WAL records) is useful.

This is the second time that pg_get_wal_block_info has been enhanced in
recent weeks.  Commit 9ecb134a expanded on the original version of the
function added in commit c31cf1c0 (where it first appeared under the
name pg_get_wal_fpi_info).  There still hasn't been a stable release
since commit c31cf1c0, so no bump in the pg_walinspect extension
version.

Author: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Author: Peter Geoghegan <pg@bowt.ie>
Reviewed-By: Peter Geoghegan <pg@bowt.ie>
Reviewed-By: Kyotaro HORIGUCHI <horikyota.ntt@gmail.com>
Discussion: https://postgr.es/m/CALj2ACVRK5=Z+2ZVsjgTTSkfEnQzCuwny7iigpG7g1btk4Ws2A@mail.gmail.com
contrib/pg_walinspect/expected/pg_walinspect.out
contrib/pg_walinspect/pg_walinspect--1.0--1.1.sql
contrib/pg_walinspect/pg_walinspect.c
contrib/pg_walinspect/sql/pg_walinspect.sql
doc/src/sgml/pgwalinspect.sgml