<entry role="catalog_table_entry"><para role="column_definition">
       <structfield>heap_blks_total</structfield> <type>bigint</type>
      </para>
      <para>
       Total number of heap blocks in the table.  This number is reported
       as of the beginning of the scan; blocks added later will not be (and
       need not be) visited by this <command>VACUUM</command>.
      </para></entry>
     </row>

     <row>
      <entry role="catalog_table_entry"><para role="column_definition">
       <structfield>heap_blks_scanned</structfield> <type>bigint</type>
      </para>
      <para>
       Number of heap blocks scanned.  Because the
       <link linkend="storage-vm">visibility map</link> is used to optimize scans,
       some blocks will be skipped without inspection; skipped blocks are
       included in this total, so that this number will eventually become
       equal to <structfield>heap_blks_total</structfield> when the vacuum is complete.
       This counter only advances when the phase is <literal>scanning heap</literal>.
      </para></entry>
     </row>

     <row>
      <entry role="catalog_table_entry"><para role="column_definition">
       <structfield>heap_blks_vacuumed</structfield> <type>bigint</type>
      </para>
      <para>
       Number of heap blocks vacuumed.  Unless the table has no indexes, this
       counter only advances when the phase is <literal>vacuuming heap</literal>.
       Blocks that contain no dead tuples are skipped, so the counter may
       sometimes skip forward in large increments.
      </para></entry>
     </row>

     <row>
      <entry role="catalog_table_entry"><para role="column_definition">
       <structfield>index_vacuum_count</structfield> <type>bigint</type>
      </para>
      <para>
       Number of completed index vacuum cycles.
      </para></entry>
     </row>

     <row>
      <entry role="catalog_table_entry"><para role="column_definition">
       <structfield>max_dead_tuple_bytes</structfield> <type>bigint</type>
      </para>
      <para>
       Amount of dead tuple data that we can store before needing to perform
       an index vacuum cycle, based on
       <xref linkend="guc-maintenance-work-mem"/>.
      </para></entry>
     </row>

     <row>
      <entry role="catalog_table_entry"><para role="column_definition">
       <structfield>dead_tuple_bytes</structfield> <type>bigint</type>
      </para>
      <para>
       Amount of dead tuple data collected since the last index vacuum cycle.
      </para></entry>
     </row>

     <row>
      <entry role="catalog_table_entry"><para role="column_definition">
      <structfield>num_dead_item_ids</structfield> <type>bigint</type>
      </para>
      <para>
       Number of dead item identifiers collected since the last index vacuum cycle.
      </para></entry>
     </row>

     <row>
      <entry role="catalog_table_entry"><para role="column_definition">
       <structfield>indexes_total</structfield> <type>bigint</type>
      </para>
      <para>
       Total number of indexes that will be vacuumed or cleaned up. This
       number is reported at the beginning of the
       <literal>vacuuming indexes</literal> phase or the
       <literal>cleaning up indexes</literal> phase.
      </para></entry>
     </row>

     <row>
      <entry role="catalog_table_entry"><para role="column_definition">
       <structfield>indexes_processed</structfield> <type>bigint</type>
      </para>
      <para>
       Number of indexes processed. This counter only advances when the
       phase is <literal>vacuuming indexes</literal> or
       <literal>cleaning up indexes</literal>.
      </para></entry>
     </row>

     <row>
      <entry role="catalog_table_entry"><para role="column_definition">
       <structfield>delay_time</structfield> <type>double precision</type>
      </para>
      <para>
       Total time spent sleeping due to cost-based delay (see
       <xref linkend="runtime-config-resource-vacuum-cost"/>), in milliseconds