Date: Fri, 13 Sep 2019 15:00:25 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tatsuro Yamada <tatsuro.yamada.tf@nttcom.co.jp>
Cc: Tatsuro Yamada <yamada.tatsuro@lab.ntt.co.jp>,
	Robert Haas <robertmhaas@gmail.com>,
	Rafia Sabih <rafia.pghackers@gmail.com>,
	Dmitry Dolgov <9erthalion6@gmail.com>, Peter Geoghegan <pg@bowt.ie>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>,
	Jeff Janes <jeff.janes@gmail.com>,
	Thomas Munro <thomas.munro@enterprisedb.com>,
	Michael Paquier <michael.paquier@gmail.com>
Subject: Re: [HACKERS] CLUSTER command progress monitor
Message-ID: <20190913180025.GA1752@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <d45843c9-8f94-4528-affb-2ee4140d8bca@nttcom.co.jp_1>
User-Agent: Mutt/1.9.4 (2018-02-28)
Precedence: bulk

Hello Tatsuro,

On 2019-Aug-13, Tatsuro Yamada wrote:

> On 2019/08/02 3:43, Alvaro Herrera wrote:
> > Hmm, I'm trying this out now and I don't see the index_rebuild_count
> > ever go up.  I think it's because the indexes are built using parallel
> > index build ... or maybe it was the table AM changes that moved things
> > around, not sure.  There's a period at the end when the CLUSTER command
> > keeps working, but it's gone from pg_stat_progress_cluster.
> 
> Thanks for your report.
> I'll investigate it. :)

I have fixed it.  Can you please verify?

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services