Re: [HACKERS] CLUSTER command progress monitor - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: [HACKERS] CLUSTER command progress monitor
Date
Msg-id CAMkU=1ydQFp0tQkXqQBRMigb_sXR0kz_5ihZJ2wHA4a+ephDgw@mail.gmail.com
Whole thread Raw
In response to [HACKERS] CLUSTER command progress monitor  (Tatsuro Yamada <yamada.tatsuro@lab.ntt.co.jp>)
List 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

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [HACKERS] POC: Sharing record typmods between backends
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] SendRowDescriptionMessage() is slow for queries with alot of columns