@@ -379,15 +379,14 @@ CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] [ <replaceable class="parameter">name</
379379 </para>
380380
381381 <para>
382- In a concurrent index build, the index is actually entered into the
383- system catalogs in one transaction, then the two table scans occur in a
384- second and third transaction. All active transactions at the time the
385- second table scan starts, not just ones that already involve the table,
386- have the potential to block the concurrent index creation until they
387- finish. When checking for transactions that could still use the original
388- index, concurrent index creation advances through potentially interfering
389- older transactions one at a time, obtaining shared locks on their virtual
390- transaction identifiers to wait for them to complete.
382+ In a concurrent index build, the index is actually entered into
383+ the system catalogs in one transaction, then two table scans occur in
384+ two more transactions. Any transaction active when the second table
385+ scan starts can block concurrent index creation until it completes,
386+ even transactions that only reference the table after the second table
387+ scan starts. Concurrent index creation serially waits for each old
388+ transaction to complete using the method outlined in section <xref
389+ linkend="view-pg-locks">.
391390 </para>
392391
393392 <para>