Re: monitoring CREATE INDEX [CONCURRENTLY]
Amit Langote <langote_amit_f8@lab.ntt.co.jp>
From: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
To: Simon Riggs <simon@2ndquadrant.com>,
Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Rahila Syed <rahilasyed90@gmail.com>,
Pg Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-02-13T04:20:08Z
Lists: pgsql-hackers
On 2019/02/13 11:59, Simon Riggs wrote: > On Wed, 13 Feb 2019 at 00:46, Alvaro Herrera <alvherre@2ndquadrant.com> > wrote: > >> Here's a sample >> concurrent index build on a 100M tuple table. > > > Cool +1 Looking at the "([phase] x of x)" in the sample output, I thought pg_stat_progress_vacuum's output should've had it too (not a concern of Alvaro's patch though.) Thanks, Amit
Commits
-
Report progress of REINDEX operations
- 03f9e5cba0ee 12.0 landed
-
Report progress of CREATE INDEX operations
- ab0dfc961b6a 12.0 landed
-
Fix error handling of readdir() port implementation on first file lookup
- 754b90f657bd 12.0 cited