Re: [HACKERS] CLUSTER command progress monitor - Mailing list pgsql-hackers

From Tatsuro Yamada
Subject Re: [HACKERS] CLUSTER command progress monitor
Date
Msg-id 992db8b2-7640-6b1f-6792-511412fdb5ea@nttcom.co.jp_1
Whole thread Raw
In response to Re: [HACKERS] CLUSTER command progress monitor  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: [HACKERS] CLUSTER command progress monitor
List pgsql-hackers
Hi Alvaro,


On 2019/09/16 23:12, Alvaro Herrera wrote:
> On 2019-Sep-16, Tattsu Yama wrote:
> 
>> I should have explained the API changes more. I added cmdtype as a given
>> parameter for all functions (See below).
>> Therefore, I suppose that my patch is similar to the following fix as you
>> mentioned on -hackers.
> 
> Is this fix strictly necessary for pg12, or is this something that we
> can leave for pg13?


Not only me but many DBA needs this progress report feature on PG12,
therefore I'm trying to fix the problem. If you send other patch to
fix the problem, and it is more elegant than mine, I can withdraw my patch.
Anyway, I want to avoid this feature being reverted.
Do you have any ideas to fix the problem?


Thanks,
Tatsuro Yamada







pgsql-hackers by date:

Previous
From: "Jamison, Kirk"
Date:
Subject: RE: [PATCH] Speedup truncates of relation forks
Next
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] CLUSTER command progress monitor