Re: [HACKERS] CLUSTER command progress monitor
Tatsuro Yamada <tatsuro.yamada.tf@nttcom.co.jp>
From: Tatsuro Yamada <tatsuro.yamada.tf@nttcom.co.jp>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Tattsu Yama <yamatattsu@gmail.com>, Michael Paquier <michael@paquier.xyz>,
robertmhaas@gmail.com, Rafia Sabih <rafia.pghackers@gmail.com>,
Dmitry Dolgov <9erthalion6@gmail.com>, Peter Geoghegan <pg@bowt.ie>,
pgsql-hackers@postgresql.org, Jeff Janes <jeff.janes@gmail.com>,
Thomas Munro <thomas.munro@enterprisedb.com>,
Michael Paquier <michael.paquier@gmail.com>
Date: 2019-09-17T02:34:21Z
Lists: 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
Commits
-
Fix progress reporting of CLUSTER / VACUUM FULL
- da47e43dc32e 12.0 cited