postgres.git / summary / log / commit / refs

commit    8fb95a8ab6e511c049066a03fe9b81fe83ff937b
Author:   Álvaro Herrera <alvherre@kurilemu.de>
Date:     Tue Apr 07 13:33:55 2026 +0000

    doc: Add an example of REPACK (CONCURRENTLY)
    
    Suggested-by: vignesh C <vignesh21@gmail.com>
    Discussion: https://postgr.es/m/CALDaNm3tiKhtegx5Cawi34UjbHmNGEDNAtScGM1RgWRtV-5_0Q@mail.gmail.com


 doc/src/sgml/ref/repack.sgml | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/doc/src/sgml/ref/repack.sgml b/doc/src/sgml/ref/repack.sgml
index e993dfb3108..ac020406d11 100644
--- a/doc/src/sgml/ref/repack.sgml
+++ b/doc/src/sgml/ref/repack.sgml
@@ -390,13 +390,21 @@ REPACK employees;
 
   <para>
    Repack the table <literal>employees</literal> on the basis of its
-   index <literal>employees_ind</literal> (Since index is used here, this is
+   index <literal>employees_ind</literal> (since an index is specified, this is
    effectively clustering):
 <programlisting>
 REPACK employees USING INDEX employees_ind;
 </programlisting>
   </para>
 
+  <para>
+   Repack the <literal>employees</literal> table following the same index
+   as was used before, in concurrent mode:
+<programlisting>
+REPACK (CONCURRENTLY) employees USING INDEX;
+</programlisting>
+  </para>
+
   <para>
    Repack the table <literal>cases</literal> on physical ordering,
    running an <command>ANALYZE</command> on the given columns once


[parent: 9480c585df6c]