Horton

Re: progress report for ANALYZE

Tatsuro Yamada <tatsuro.yamada.tf@nttcom.co.jp>

View thread View on postgr.es
From: Tatsuro Yamada <tatsuro.yamada.tf@nttcom.co.jp>
To: Amit Langote <amitlangote09@gmail.com>, Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: vignesh C <vignesh21@gmail.com>, Pg Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-01-27T10:16:25Z
Lists: pgsql-hackers 
Hi,

On 2020/01/24 23:44, Amit Langote wrote:
> On Fri, Jan 24, 2020 at 6:47 AM Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
>> On 2020-Jan-22, Tatsuro Yamada wrote:
>>> P.S.
>>> Next up is progress reporting for query execution?!
>>
>> Actually, I think it's ALTER TABLE.
> 
> +1.  Existing infrastructure might be enough to cover ALTER TABLE's
> needs, whereas we will very likely need to build entirely different
> infrastructure for tracking the progress for SQL query execution.

Yeah, I agree.
I will create a little POC patch after reading tablecmds.c and alter.c to
investigate how to report progress. :)

Regards,
Tatsuro Yamada

Commits

  1. Doc: Fix and tweak documentation for ANALYZE reporting