@@ -372,46 +372,46 @@ postgres 27093 0.0 0.0 30096 2752 ? Ss 11:34 0:00 postgres: ser
372
372
<entry><structname>pg_stat_progress_analyze</structname><indexterm><primary>pg_stat_progress_analyze</primary></indexterm></entry>
373
373
<entry>One row for each backend (including autovacuum worker processes) running
374
374
<command>ANALYZE</command>, showing current progress.
375
- See <xref linkend=' analyze-progress-reporting' />.
375
+ See <xref linkend=" analyze-progress-reporting" />.
376
376
</entry>
377
377
</row>
378
378
379
379
<row>
380
380
<entry><structname>pg_stat_progress_create_index</structname><indexterm><primary>pg_stat_progress_create_index</primary></indexterm></entry>
381
381
<entry>One row for each backend running <command>CREATE INDEX</command> or <command>REINDEX</command>, showing
382
382
current progress.
383
- See <xref linkend=' create-index-progress-reporting' />.
383
+ See <xref linkend=" create-index-progress-reporting" />.
384
384
</entry>
385
385
</row>
386
386
387
387
<row>
388
388
<entry><structname>pg_stat_progress_vacuum</structname><indexterm><primary>pg_stat_progress_vacuum</primary></indexterm></entry>
389
389
<entry>One row for each backend (including autovacuum worker processes) running
390
390
<command>VACUUM</command>, showing current progress.
391
- See <xref linkend=' vacuum-progress-reporting' />.
391
+ See <xref linkend=" vacuum-progress-reporting" />.
392
392
</entry>
393
393
</row>
394
394
395
395
<row>
396
396
<entry><structname>pg_stat_progress_cluster</structname><indexterm><primary>pg_stat_progress_cluster</primary></indexterm></entry>
397
397
<entry>One row for each backend running
398
398
<command>CLUSTER</command> or <command>VACUUM FULL</command>, showing current progress.
399
- See <xref linkend=' cluster-progress-reporting' />.
399
+ See <xref linkend=" cluster-progress-reporting" />.
400
400
</entry>
401
401
</row>
402
402
403
403
<row>
404
404
<entry><structname>pg_stat_progress_basebackup</structname><indexterm><primary>pg_stat_progress_basebackup</primary></indexterm></entry>
405
405
<entry>One row for each WAL sender process streaming a base backup,
406
406
showing current progress.
407
- See <xref linkend=' basebackup-progress-reporting' />.
407
+ See <xref linkend=" basebackup-progress-reporting" />.
408
408
</entry>
409
409
</row>
410
410
411
411
<row>
412
412
<entry><structname>pg_stat_progress_copy</structname><indexterm><primary>pg_stat_progress_copy</primary></indexterm></entry>
413
413
<entry>One row for each backend running <command>COPY</command>, showing current progress.
414
- See <xref linkend=' copy-progress-reporting' />.
414
+ See <xref linkend=" copy-progress-reporting" />.
415
415
</entry>
416
416
</row>
417
417
</tbody>
@@ -7055,7 +7055,7 @@ FROM pg_stat_get_backend_idset() AS backendid;
7055
7055
<structname>pg_stat_progress_cluster</structname>
7056
7056
because both <command>VACUUM FULL</command> and <command>CLUSTER</command>
7057
7057
rewrite the table, while regular <command>VACUUM</command> only modifies it
7058
- in place. See <xref linkend=' cluster-progress-reporting' />.
7058
+ in place. See <xref linkend=" cluster-progress-reporting" />.
7059
7059
</para>
7060
7060
7061
7061
<table id="pg-stat-progress-vacuum-view" xreflabel="pg_stat_progress_vacuum">
0 commit comments