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: David Steele <david@pgmasters.net>, Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2019-03-05T08:37:17Z
Lists: pgsql-hackers 
Hi David,

On 2019/03/05 17:29, David Steele wrote:
> 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).


Thank you! :)


Regards,
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