diff options
| author | Alvaro Herrera | 2019-04-02 18:18:08 +0000 |
|---|---|---|
| committer | Alvaro Herrera | 2019-04-02 18:18:08 +0000 |
| commit | ab0dfc961b6a821f23d9c40c723d11380ce195a6 (patch) | |
| tree | 106f18249990aa4da0e3e49a9bf957b8a42f34e5 /contrib/amcheck | |
| parent | 4d0e994eed83c845a05da6e9a417b4efec67efaf (diff) | |
Report progress of CREATE INDEX operations
This uses the progress reporting infrastructure added by c16dc1aca5e0,
adding support for CREATE INDEX and CREATE INDEX CONCURRENTLY.
There are two pieces to this: one is index-AM-agnostic, and the other is
AM-specific. The latter is fairly elaborate for btrees, including
reportage for parallel index builds and the separate phases that btree
index creation uses; other index AMs, which are much simpler in their
building procedures, have simplistic reporting only, but that seems
sufficient, at least for non-concurrent builds.
The index-AM-agnostic part is fairly complete, providing insight into
the CONCURRENTLY wait phases as well as block-based progress during the
index validation table scan. (The index validation index scan requires
patching each AM, which has not been included here.)
Reviewers: Rahila Syed, Pavan Deolasee, Tatsuro Yamada
Discussion: https://postgr.es/m/20181220220022.mg63bhk26zdpvmcj@alvherre.pgsql
Diffstat (limited to 'contrib/amcheck')
| -rw-r--r-- | contrib/amcheck/verify_nbtree.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contrib/amcheck/verify_nbtree.c b/contrib/amcheck/verify_nbtree.c index 9d5b2e5be67..591e0a3e46a 100644 --- a/contrib/amcheck/verify_nbtree.c +++ b/contrib/amcheck/verify_nbtree.c @@ -566,7 +566,7 @@ bt_check_every_level(Relation rel, Relation heaprel, bool heapkeyspace, RelationGetRelationName(state->rel), RelationGetRelationName(state->heaprel)); - table_index_build_scan(state->heaprel, state->rel, indexinfo, true, + table_index_build_scan(state->heaprel, state->rel, indexinfo, true, false, bt_tuple_present_callback, (void *) state, scan); ereport(DEBUG1, |