Re: monitoring CREATE INDEX [CONCURRENTLY]
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Rahila Syed <rahila.syed@2ndquadrant.com>
Cc: Andres Freund <andres@anarazel.de>, Robert Haas <robertmhaas@gmail.com>, Simon Riggs <simon@2ndquadrant.com>, Pg Hackers <pgsql-hackers@lists.postgresql.org>, David Fetter <david@fetter.org>, Pavan Deolasee <pavan.deolasee@gmail.com>, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Date: 2019-04-01T16:10:44Z
Lists: pgsql-hackers
Attachments
- v9-0001-Report-progress-of-CREATE-INDEX-operations.patch (text/x-diff)
Hi Rahila, thanks for reviewing. On 2019-Mar-25, Rahila Syed wrote: > Please see few comments below: > > 1. Makecheck fails currently as view definition of expected rules.out does > not reflect latest changes in progress metrics numbering. Ouch ... fixed. > 2. + <entry> > I think there is a typo here 's/partitioned/partitioned table/' Ah, so there is. Fixed. > 3. > I think parallel scan equivalent bpscan->phs_nblocks along with > hscan->rs_nblocks should be used similar to startblock computation above. Hmm, yeah. I think the way things are setup currently it doesn't matter much, but it seems fragile to rely on that. I also moved the reporting of total blocks to scan in the initial table scan so that it occurs wholly in heapam_index_build_range_scan; I had originally put that code in _bt_spools_heapscan, but that was a modularity violation I think. (It didn't make a practical difference, but it made no sense to have the two cases report the number in wildly different locations.) Also added a final nblocks metric update after the scan is done. I think this patch is done. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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