pg_stat_progress_data_checksums

PostgreSQL documentation ↗Source definition ↗

When data checksums are being enabled or disabled on a running cluster, the pg_stat_progress_data_checksums view will contain a row for the launcher process. When enabling data checksums, the view will also contain one row for each worker process which is currently calculating and writing checksums for the data pages in a database. The launcher provides an overview of the overall progress, such as how many databases have been processed and how many remain, while the workers track progress for currently processed databases.

First seen PG 19Last seen PG 19Columns 10

9.0 9.1 9.2 9.3 9.4 9.5 9.6 10 11 12 13 14 15 16 17 18 19^β3

Checked column by column against a PostgreSQL 19beta3 instance · Raw measurement record ↗

Columns PostgreSQL 19

pg_stat_progress_data_checksums

COLUMN	TYPE	DESCRIPTION
`pid`	`integer`	Process ID of the data checksum process, launcher or worker.
`datid`	`oid`	OID of this database, or 0 for the launcher process.
`datname`	`name`	Name of this database, or NULL for the launcher process.
`phase`	`text`	Current processing phase, see Table 27.55 for description of the phases.
`databases_total`	`bigint`	The total number of databases which will be processed. Only the launcher process has this value set when enabling data checksums; otherwise this is set to NULL.
`databases_done`	`bigint`	The number of databases which have been processed. Only the launcher process has this value set when enabling data checksums; otherwise this is set to NULL.
`relations_total`	`bigint`	The total number of relations which will be processed, or NULL if the worker process hasn't calculated the number of relations yet. The launcher process has this set to NULL since it isn't responsible for processing relations, only launching worker processes.
`relations_done`	`bigint`	The number of relations which have been processed. The launcher process has this set to NULL.
`blocks_total`	`bigint`	The number of blocks in the current relation which will be processed, or NULL if the worker process hasn't calculated the number of blocks yet. The launcher process has this set to NULL.
`blocks_done`	`bigint`	The number of blocks in the current relation which have been processed. The launcher process has this set to NULL.

Columns marked "implicit" are not included in SELECT *; some early statistics views are completed from same-version source, and the extra provenance is shown in the column description.

Column evolution matrix

Hover a cell for the column type

PresentAdded / type or attribute changeRemoved

COLUMN	9.0	9.1	9.2	9.3	9.4	9.5	9.6	10	11	12	13	14	15	16	17	18
`pid`	–	–	–	–	–	–	–	–	–	–	–	–	–	–	–	–
`datid`	–	–	–	–	–	–	–	–	–	–	–	–	–	–	–	–
`datname`	–	–	–	–	–	–	–	–	–	–	–	–	–	–	–	–
`phase`	–	–	–	–	–	–	–	–	–	–	–	–	–	–	–	–
`databases_total`	–	–	–	–	–	–	–	–	–	–	–	–	–	–	–	–
`databases_done`	–	–	–	–	–	–	–	–	–	–	–	–	–	–	–	–
`relations_total`	–	–	–	–	–	–	–	–	–	–	–	–	–	–	–	–
`relations_done`	–	–	–	–	–	–	–	–	–	–	–	–	–	–	–	–
`blocks_total`	–	–	–	–	–	–	–	–	–	–	–	–	–	–	–	–
`blocks_done`	–	–	–	–	–	–	–	–	–	–	–	–	–	–	–	–

9.0 is the coverage baseline; a column already present in the baseline is not marked as added. The matrix aligns columns by name, so a rename appears as the old column removed and a new column added.

Evolution timeline

Changes between adjacent majors

PostgreSQL 19 ← 18Catalog added

+ pid+ datid+ datname+ phase+ databases_total+ databases_done+ relations_total+ relations_done+ blocks_total+ blocks_done

Compare any two versions

FROMTOInclude description updates

Pick two versions to see added, removed, and retyped columns. The interactive comparison needs JavaScript; the evolution timeline reads fine without it.