Date: Mon, 16 Sep 2019 23:08:32 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tatsuro Yamada <tatsuro.yamada.tf@nttcom.co.jp>
Cc: Tattsu Yama <yamatattsu@gmail.com>,
	Michael Paquier <michael@paquier.xyz>, robertmhaas@gmail.com,
	Rafia Sabih <rafia.pghackers@gmail.com>,
	Dmitry Dolgov <9erthalion6@gmail.com>, Peter Geoghegan <pg@bowt.ie>,
	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: <20190917020832.GA20066@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <992db8b2-7640-6b1f-6792-511412fdb5ea@nttcom.co.jp_1>
User-Agent: Mutt/1.9.4 (2018-02-28)
Precedence: bulk

On 2019-Sep-17, Tatsuro Yamada wrote:

> On 2019/09/16 23:12, Alvaro Herrera wrote:

> > Is this fix strictly necessary for pg12, or is this something that we
> > can leave for pg13?
> 
> Not only me but many DBA needs this progress report feature on PG12,
> therefore I'm trying to fix the problem. If you send other patch to
> fix the problem, and it is more elegant than mine, I can withdraw my patch.
> Anyway, I want to avoid this feature being reverted.
> Do you have any ideas to fix the problem?

I committed a fix for the originally reported problem as da47e43dc32e in
branch REL_12_STABLE.  Is that insufficient, and if so why?

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