@@ -300,19 +300,19 @@ REINDEX [ ( VERBOSE ) ] { INDEX | TABLE | SCHEMA | DATABASE | SYSTEM } [ CONCURR
300
300
<orderedlist>
301
301
<listitem>
302
302
<para>
303
- A new temporary index definition is added into the catalog
303
+ A new temporary index definition is added to the catalog
304
304
<literal>pg_index</literal>. This definition will be used to replace
305
305
the old index. A <literal>SHARE UPDATE EXCLUSIVE</literal> lock at
306
- session level is taken on the indexes being reindexed as well as its
307
- associated table to prevent any schema modification while processing.
306
+ session level is taken on the indexes being reindexed as well as their
307
+ associated tables to prevent any schema modification while processing.
308
308
</para>
309
309
</listitem>
310
310
311
311
<listitem>
312
312
<para>
313
313
A first pass to build the index is done for each new index. Once the
314
314
index is built, its flag <literal>pg_index.indisready</literal> is
315
- switched to <quote>true</quote> to make ready for inserts, making it
315
+ switched to <quote>true</quote> to make it ready for inserts, making it
316
316
visible to other sessions once the transaction that performed the build
317
317
is finished. This step is done in a separate transaction for each
318
318
index.
@@ -322,7 +322,7 @@ REINDEX [ ( VERBOSE ) ] { INDEX | TABLE | SCHEMA | DATABASE | SYSTEM } [ CONCURR
322
322
<listitem>
323
323
<para>
324
324
Then a second pass is performed to add tuples that were added while the
325
- first pass build was running. This step is also done in a separate
325
+ first pass was running. This step is also done in a separate
326
326
transaction for each index.
327
327
</para>
328
328
</listitem>
@@ -331,10 +331,10 @@ REINDEX [ ( VERBOSE ) ] { INDEX | TABLE | SCHEMA | DATABASE | SYSTEM } [ CONCURR
331
331
<para>
332
332
All the constraints that refer to the index are changed to refer to the
333
333
new index definition, and the names of the indexes are changed. At
334
- this point <literal>pg_index.indisvalid</literal> is switched to
334
+ this point, <literal>pg_index.indisvalid</literal> is switched to
335
335
<quote>true</quote> for the new index and to <quote>false</quote> for
336
- the old, and a cache invalidation is done so as all the sessions that
337
- referenced the old index are invalidated.
336
+ the old, and a cache invalidation is done causing all sessions that
337
+ referenced the old index to be invalidated.
338
338
</para>
339
339
</listitem>
340
340
@@ -359,8 +359,8 @@ REINDEX [ ( VERBOSE ) ] { INDEX | TABLE | SCHEMA | DATABASE | SYSTEM } [ CONCURR
359
359
<para>
360
360
If a problem arises while rebuilding the indexes, such as a
361
361
uniqueness violation in a unique index, the <command>REINDEX</command>
362
- command will fail but leave behind an <quote>invalid</quote> new index on top
363
- of the existing one. This index will be ignored for querying purposes
362
+ command will fail but leave behind an <quote>invalid</quote> new index in addition to
363
+ the pre- existing one. This index will be ignored for querying purposes
364
364
because it might be incomplete; however it will still consume update
365
365
overhead. The <application>psql</application> <command>\d</command> command will report
366
366
such an index as <literal>INVALID</literal>:
@@ -387,7 +387,7 @@ Indexes:
387
387
388
388
<para>
389
389
Regular index builds permit other regular index builds on the same table
390
- to occur in parallel , but only one concurrent index build can occur on a
390
+ to occur simultaneously , but only one concurrent index build can occur on a
391
391
table at a time. In both cases, no other types of schema modification on
392
392
the table are allowed meanwhile. Another difference is that a regular
393
393
<command>REINDEX TABLE</command> or <command>REINDEX INDEX</command>
@@ -406,7 +406,7 @@ Indexes:
406
406
concurrently. If such an index is named directly in this command, an
407
407
error is raised. If a table or database with exclusion constraint indexes
408
408
is reindexed concurrently, those indexes will be skipped. (It is possible
409
- to reindex such indexes without the concurrently option.)
409
+ to reindex such indexes without the <command>CONCURRENTLY</command> option.)
410
410
</para>
411
411
</refsect2>
412
412
</refsect1>
0 commit comments