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

From Tatsuro Yamada
Subject Re: [HACKERS] CLUSTER command progress monitor
Date
Msg-id da3851ec-5676-d970-fbc7-f4798a65fd99@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!

>>> 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?
> 
> I committed a fix for the originally reported problem as da47e43dc32e in
> branch REL_12_STABLE.  Is that insufficient, and if so why?


Ooops, I misunderstood. I now realized you committed your patch to
fix the problem. Thanks! I'll test it later. :)

https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=da47e43dc32e3c5916396f0cbcfa974b371e4875


Thanks,
Tatsuro Yamada




pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: refactoring - share str2*int64 functions
Next
From: Michael Paquier
Date:
Subject: Re: refactoring - share str2*int64 functions