@@ -394,15 +394,14 @@ CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] [ <replaceable class="parameter">name</
394394 </para>
395395
396396 <para>
397- In a concurrent index build, the index is actually entered into the
398- system catalogs in one transaction, then the two table scans occur in a
399- second and third transaction. All active transactions at the time the
400- second table scan starts, not just ones that already involve the table,
401- have the potential to block the concurrent index creation until they
402- finish. When checking for transactions that could still use the original
403- index, concurrent index creation advances through potentially interfering
404- older transactions one at a time, obtaining shared locks on their virtual
405- transaction identifiers to wait for them to complete.
397+ In a concurrent index build, the index is actually entered into
398+ the system catalogs in one transaction, then two table scans occur in
399+ two more transactions. Any transaction active when the second table
400+ scan starts can block concurrent index creation until it completes,
401+ even transactions that only reference the table after the second table
402+ scan starts. Concurrent index creation serially waits for each old
403+ transaction to complete using the method outlined in section <xref
404+ linkend="view-pg-locks">.
406405 </para>
407406
408407 <para>