Date: Mon, 16 Sep 2019 11:12:15 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tattsu Yama <yamatattsu@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>,
	Tatsuro Yamada <tatsuro.yamada.tf@nttcom.co.jp>,
	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: <20190916141214.GA10855@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAOKkKFtN97_LjhLCuqxdrnQQAYLzDwy40L6gtuXiHWkeN97yoA@mail.gmail.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
Precedence: bulk

On 2019-Sep-16, Tattsu Yama wrote:

> I should have explained the API changes more. I added cmdtype as a given
> parameter for all functions (See below).
> Therefore, I suppose that my patch is similar to the following fix as you
> mentioned on -hackers.

Is this fix strictly necessary for pg12, or is this something that we
can leave for pg13?


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