Horton

Re: CLUSTER command progress monitor

Jeff Janes <jeff.janes@gmail.com>

View thread View on postgr.es
From: Jeff Janes <jeff.janes@gmail.com>
To: Tatsuro Yamada <yamada.tatsuro@lab.ntt.co.jp>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2017-09-15T18:09:13Z
Lists: pgsql-hackers 
On Wed, Aug 30, 2017 at 7:12 PM, Tatsuro Yamada <
yamada.tatsuro@lab.ntt.co.jp> wrote:

>
> The view provides the information of CLUSTER command progress details as
> follows
> postgres=# \d pg_stat_progress_cluster
>            View "pg_catalog.pg_stat_progress_cluster"
>        Column        |  Type   | Collation | Nullable | Default
> ---------------------+---------+-----------+----------+---------
>  pid                 | integer |           |          |
>  datid               | oid     |           |          |
>  datname             | name    |           |          |
>  relid               | oid     |           |          |
>  phase               | text    |           |          |
>  scan_method         | text    |           |          |
>  scan_index_relid    | bigint  |           |          |
>  heap_tuples_total   | bigint  |           |          |
>  heap_tuples_scanned | bigint  |           |          |
>

I think it should be cluster_index_relid, not scan_index_relid.  If the
scan_method is seq, then the index isn't being scanned.

Cheers,

Jeff

Commits

  1. Fix progress reporting of CLUSTER / VACUUM FULL

  2. Fix thinko when ending progress report for a backend

  3. Report progress of REINDEX operations

  4. Add progress reporting for CLUSTER and VACUUM FULL.

  5. Un-hide most cascaded-drop details in regression test results.

  6. Fix memory leak in printtup.c.

  7. Remove unused macro