Re: CLUSTER command progress monitor

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Tatsuro Yamada <yamada(dot)tatsuro(at)lab(dot)ntt(dot)co(dot)jp>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CLUSTER command progress monitor
Date: 2017-09-15 18:09:13
Message-ID: CAMkU=1ydQFp0tQkXqQBRMigb_sXR0kz_5ihZJ2wHA4a+ephDgw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Aug 30, 2017 at 7:12 PM, Tatsuro Yamada <
yamada(dot)tatsuro(at)lab(dot)ntt(dot)co(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2017-09-15 18:14:36 Re: pgsql: Add support for coordinating record typmods among parallel worke
Previous Message Andres Freund 2017-09-15 18:07:08 Re: pgsql: Add support for coordinating record typmods among parallel worke