pg_stat_progress_cluster

PostgreSQL documentation ↗Source definition ↗

Whenever CLUSTER or VACUUM FULL is running, the pg_stat_progress_cluster view will contain a row for each backend that is currently running either command. The tables below describe the information that will be reported and provide information about how to interpret it.

First seen PG 12Last seen PG 19Columns 12

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 18.6 instance · Raw measurement record ↗

Columns PostgreSQL 18

pg_stat_progress_cluster

COLUMN	TYPE	DESCRIPTION
`pid`	`integer`	Process ID of backend.
`datid`	`oid`	OID of the database to which this backend is connected.
`datname`	`name`	Name of the database to which this backend is connected.
`relid`	`oid`	OID of the table being clustered.
`command`	`text`	The command that is running. Either CLUSTER or VACUUM FULL.
`phase`	`text`	Current processing phase. See Table 27.41.
`cluster_index_relid`	`oid`	If the table is being scanned using an index, this is the OID of the index being used; otherwise, it is zero.
`heap_tuples_scanned`	`bigint`	Number of heap tuples scanned. This counter only advances when the phase is seq scanning heap, index scanning heap or writing new heap.
`heap_tuples_written`	`bigint`	Number of heap tuples written. This counter only advances when the phase is seq scanning heap, index scanning heap or writing new heap.
`heap_blks_total`	`bigint`	Total number of heap blocks in the table. This number is reported as of the beginning of seq scanning heap.
`heap_blks_scanned`	`bigint`	Number of heap blocks scanned. This counter only advances when the phase is seq scanning heap.
`index_rebuild_count`	`bigint`	Number of indexes rebuilt. This counter only advances when the phase is rebuilding index.

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
`pid`	–	–	–	–	–	–	–	–	–
`datid`	–	–	–	–	–	–	–	–	–
`datname`	–	–	–	–	–	–	–	–	–
`relid`	–	–	–	–	–	–	–	–	–
`command`	–	–	–	–	–	–	–	–	–
`phase`	–	–	–	–	–	–	–	–	–
`cluster_index_relid`	–	–	–	–	–	–	–	–	–
`heap_tuples_scanned`	–	–	–	–	–	–	–	–	–
`heap_tuples_written`	–	–	–	–	–	–	–	–	–
`heap_blks_total`	–	–	–	–	–	–	–	–	–
`heap_blks_scanned`	–	–	–	–	–	–	–	–	–
`index_rebuild_count`	–	–	–	–	–	–	–	–	–

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 ← 18

2 column description updatesCatalog description updated

PostgreSQL 17 ← 16

1 column description updates

PostgreSQL 16 ← 15

1 column description updates

PostgreSQL 15 ← 14

1 column description updates

PostgreSQL 14 ← 13

1 column description updates

PostgreSQL 13 ← 12

1 column description updates

PostgreSQL 12 ← 11Catalog added

+ pid+ datid+ datname+ relid+ command+ phase+ cluster_index_relid+ heap_tuples_scanned+ heap_tuples_written+ heap_blks_total+ heap_blks_scanned+ index_rebuild_count

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.