Horton

Re: [HACKERS] CLUSTER command progress monitor

Tatsuro Yamada <yamada.tatsuro@lab.ntt.co.jp>

View thread View on postgr.es
From: Tatsuro Yamada <yamada.tatsuro@lab.ntt.co.jp>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Dmitry Dolgov <9erthalion6@gmail.com>, pg@bowt.ie, Robert Haas <robertmhaas@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Jeff Janes <jeff.janes@gmail.com>, Thomas Munro <thomas.munro@enterprisedb.com>, Michael Paquier <michael.paquier@gmail.com>
Date: 2018-12-19T06:48:27Z
Lists: pgsql-hackers 
Hi Alvaro,

On 2018/12/19 2:23, Alvaro Herrera wrote:
> Hello Yamada-san,
> 
> On 2018-Dec-03, Tatsuro Yamada wrote:
> 
>> Thank you for managing the CF and Sorry for the late reply.
>> I'll rebase it for the next CF and also I'll clear my head because the patch
>> needs design change to address the feedbacks, I guess. Therefore, the status is
>> reconsidering the design of the patch. :)
> 
> Do you have a new version of this patch?  If not, do you think you'll
> have something in time for the upcoming commitfest?

Not yet, I'll be able to send only a rebased patch by the end of this month.
I mean it has no design change because I can't catch up on how to get a progress
from sort and index scan. However I'm going to register the patch on next CF.
I'm happy if you have interested in the patch. :)

Thanks,
Tatsuro Yamada

Commits

  1. Fix progress reporting of CLUSTER / VACUUM FULL

  2. Fix thinko when ending progress report for a backend

  3. Report progress of REINDEX operations

  4. Add progress reporting for CLUSTER and VACUUM FULL.

  5. Un-hide most cascaded-drop details in regression test results.

  6. Fix memory leak in printtup.c.

  7. Remove unused macro