Re: CLUSTER command progress monitor

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Tatsuro Yamada <yamada(dot)tatsuro(at)lab(dot)ntt(dot)co(dot)jp>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, sawada(dot)mshk(at)gmail(dot)com
Subject: Re: CLUSTER command progress monitor
Date: 2017-09-06 07:11:55
Message-ID: CAB7nPqS4eRdfXr8+PgJp3ot6WGKs5+uDDtxpCnKrLwhJGi=LhQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 6, 2017 at 3:58 PM, Tatsuro Yamada
<yamada(dot)tatsuro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> I revised the patch like this:

You should avoid top-posting.

> I didn't change the name of view (pg_stat_progress_cluster) because I'm not
> sure
> whether the new name (pg_stat_progress_reorg) is suitable or not.

Here are some ideas: rewrite (incorrect for ALTER TABLE), organize
(somewhat fine), order, operate (too general?), bundle, reform,
assemble.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Rushabh Lathia 2017-09-06 07:36:06 Re: dropping partitioned tables without CASCADE
Previous Message Ashutosh Bapat 2017-09-06 07:08:24 Re: paths in partitions of a dummy partitioned table