| From: | Tatsuro Yamada <tatsuro(dot)yamada(dot)tf(at)nttcom(dot)co(dot)jp> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tattsu Yama <yamatattsu(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, robertmhaas(at)gmail(dot)com, Rafia Sabih <rafia(dot)pghackers(at)gmail(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, pgsql-hackers(at)postgresql(dot)org, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Subject: | Re: [HACKERS] CLUSTER command progress monitor |
| Date: | 2019-09-17 02:01:28 |
| Message-ID: | 992db8b2-7640-6b1f-6792-511412fdb5ea@nttcom.co.jp_1 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-09-17 02:08:32 | Re: [HACKERS] CLUSTER command progress monitor |
| Previous Message | Jamison, Kirk | 2019-09-17 01:44:12 | RE: [PATCH] Speedup truncates of relation forks |