Subject: Re: progress report for ANALYZE
To: Alvaro Herrera <alvherre@2ndquadrant.com>, Pg Hackers
	<pgsql-hackers@lists.postgresql.org>
References: <20190621185207.GA27929@alvherre.pgsql>
From: Tatsuro Yamada <tatsuro.yamada.tf@nttcom.co.jp>
Message-ID: <45c2a6c0-80a1-0c55-b7d8-4ee15fd17841@nttcom.co.jp>
Date: Wed, 3 Jul 2019 13:05:24 +0900
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <20190621185207.GA27929@alvherre.pgsql>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi Alvaro!

On 2019/06/22 3:52, Alvaro Herrera wrote:
> Hello
> 
> Here's a patch that implements progress reporting for ANALYZE.

Sorry for the late reply.
My email address was changed to tatsuro.yamada.tf@nttcom.co.jp.

I have a question about your patch.
My ex-colleague Vinayak created same patch in 2017 [1], and he
couldn't get commit because there are some reasons such as the
patch couldn't handle analyzing Foreign table. Therefore, I wonder
whether your patch is able to do that or not.

However, actually, I think it's okay because the feature is useful
for DBAs, even if your patch can't handle Foreign table.

I'll review your patch in this week. :)
  
[1] ANALYZE command progress checker
https://www.postgresql.org/message-id/flat/968b4eda-2417-8b7b-d468-71643cf088b6%40openscg.com#574488592fcc9708c38fa44b0dae9006

Regards,
Tatsuro Yamada