Re: Progress report of CREATE INDEX for nested partitioned tables
Justin Pryzby <pryzby@telsasoft.com>
From: Justin Pryzby <pryzby@telsasoft.com>
To: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: Ilya Gladyshev <ilya.v.gladyshev@gmail.com>, pgsql-hackers@lists.postgresql.org, Alvaro Herrera <alvherre@alvh.no-ip.org>
Date: 2023-01-18T15:25:35Z
Lists: pgsql-hackers
TBH, I think the best approach is what I did in: 0001-report-top-parent-progress-for-CREATE-INDEX.txt That's a minimal patch, ideal for backpatching. ..which defines/clarifies that the progress reporting is only for *direct* children. That avoids the need to change any data structures, and it's what was probably intended by the original patch, which doesn't seem to have considered intermediate partitioned tables. I think it'd be fine to re-define that in some future release, to allow showing indirect children (probably only "leaves", and not intermediate partitioned tables). Or "total_bytes" or other global progress. -- Justin
Commits
-
Fix CREATE INDEX progress reporting for multi-level partitioning.
- 27f5c712b2c5 16.0 landed