Re: Re: [HACKERS] CLUSTER command progress monitor

David Steele <david@pgmasters.net>

From: David Steele <david@pgmasters.net>

To: Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>, Tatsuro Yamada <yamada.tatsuro@lab.ntt.co.jp>

Cc: pgsql-hackers@lists.postgresql.org

Date: 2019-03-05T08:29:42Z

Lists: pgsql-hackers

On 3/1/19 7:48 AM, Etsuro Fujita wrote:
> (2019/03/01 14:17), Tatsuro Yamada wrote:
>>> Attached patch is wip patch.
>>
>> Is it possible to remove the following patch?
>> Because I registered the patch twice on CF Mar.
>>
>> https://commitfest.postgresql.org/22/2049/
> 
> Please remove the above and keep this:
> 
> https://commitfest.postgresql.org/22/1779/
> 
> which I moved from the January CF to the March one on behalf of him.

I have closed the duplicate entry (#2049) and retained the entry which 
contains the CF history (#1779).

Regards,
-- 
-David
david@pgmasters.net

Commits

Fix progress reporting of CLUSTER / VACUUM FULL
- 6212276e4343 13.0 landed
- da47e43dc32e 12.0 landed
Fix thinko when ending progress report for a backend
- f4b91a50e9e6 9.6.16 landed
- 4950f09e7ae2 10.11 landed
- af28744288b1 11.6 landed
- 4c3e750ab4b5 12.0 landed
- ae060a52b288 13.0 landed
Report progress of REINDEX operations
- 03f9e5cba0ee 12.0 cited
Add progress reporting for CLUSTER and VACUUM FULL.
- 6f97457e0ddd 12.0 landed
Un-hide most cascaded-drop details in regression test results.
- 940311e4bb32 12.0 cited
Fix memory leak in printtup.c.
- f2004f19ed9c 12.0 cited
Remove unused macro
- fb5806533f9f 12.0 cited