Re: REINDEX CONCURRENTLY 2.0

From: "Bossart, Nathan" <bossartn(at)amazon(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>, Robert Treat <rob(at)xzilla(dot)net>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Sergei Kornilov <sk(at)zsrv(dot)org>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: REINDEX CONCURRENTLY 2.0
Date: 2019-03-29 15:53:05
Message-ID: 55DE37D6-984F-4EFE-9D5E-521906D8F032@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I noticed a very small typo in the documentation for this feature.

diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index ccabb330cb..e45bf86c8d 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -349,7 +349,7 @@ REINDEX [ ( VERBOSE ) ] { INDEX | TABLE | SCHEMA | DATABASE | SYSTEM } [ CONCURR
<listitem>
<para>
The old indexes are dropped. The <literal>SHARE UPDATE
- EXCLUSIVE</literal> session locks for the indexes and the table ar
+ EXCLUSIVE</literal> session locks for the indexes and the table are
released.
</para>
</listitem>

Nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2019-03-29 15:58:14 Re: pgsql: Compute XID horizon for page level index vacuum on primary.
Previous Message Magnus Hagander 2019-03-29 15:52:16 Re: Online verification of checksums