doc: Improve order of options on initdb reference page

Both the initdb --help output and the reference page have a section
for options and a section for less commonly used options.  But some
recently added options were sprinkled around inconsistently.  Fix that
by making the documentation match the --help output.

diff --git a/doc/src/sgml/ref/initdb.sgml b/doc/src/sgml/ref/initdb.sgml
index dc9011b40ed3e977fe195fa0a8bb311ef9802a58..6c96c0c06810e444af0f5d35cd1b0b9e20999639 100644 (file)
--- a/doc/src/sgml/ref/initdb.sgml
+++ b/doc/src/sgml/ref/initdb.sgml
@@ -343,34 +343,6 @@ PostgreSQL documentation
       
      
 
-     
-      -N
-      --no-sync
-      
-       
-        By default, initdb will wait for all files to be
-        written safely to disk.  This option causes initdb
-        to return without waiting, which is faster, but means that a
-        subsequent operating system crash can leave the data directory
-        corrupt.  Generally, this option is useful for testing, but should not
-        be used when creating a production installation.
-       
-      
-     
-
-     
-      --no-instructions
-      
-       
-        By default, initdb will write instructions for how
-        to start the cluster at the end of its output. This option causes
-        those instructions to be left out. This is primarily intended for use
-        by tools that wrap initdb in platform-specific
-        behavior, where those instructions are likely to be incorrect.
-       
-      
-     
-
      
       --pwfile=filename
       
@@ -381,42 +353,6 @@ PostgreSQL documentation
       
      
 
-     
-      --sync-method=method
-      
-       
-        When set to fsync, which is the default,
-        initdb will recursively open and synchronize all
-        files in the data directory.  The search for files will follow symbolic
-        links for the WAL directory and each configured tablespace.
-       
-       
-        On Linux, syncfs may be used instead to ask the
-        operating system to synchronize the whole file systems that contain the
-        data directory, the WAL files, and each tablespace.  See
-         for information about
-        the caveats to be aware of when using syncfs.
-       
-       
-        This option has no effect when --no-sync is used.
-       
-      
-     
-
-     
-      -S
-      --sync-only
-      
-       
-        Safely write all database files to disk and exit.  This does not
-        perform any of the normal initdb operations.
-        Generally, this option is useful for ensuring reliable recovery after
-        changing  from off to
-        on.
-       
-      
-     
-
      
       -T config
       --text-search-config=config
@@ -560,6 +496,70 @@ PostgreSQL documentation
        
       
      
+
+     
+      -N
+      --no-sync
+      
+       
+        By default, initdb will wait for all files to be
+        written safely to disk.  This option causes initdb
+        to return without waiting, which is faster, but means that a
+        subsequent operating system crash can leave the data directory
+        corrupt.  Generally, this option is useful for testing, but should not
+        be used when creating a production installation.
+       
+      
+     
+
+     
+      --no-instructions
+      
+       
+        By default, initdb will write instructions for how
+        to start the cluster at the end of its output. This option causes
+        those instructions to be left out. This is primarily intended for use
+        by tools that wrap initdb in platform-specific
+        behavior, where those instructions are likely to be incorrect.
+       
+      
+     
+
+     
+      --sync-method=method
+      
+       
+        When set to fsync, which is the default,
+        initdb will recursively open and synchronize all
+        files in the data directory.  The search for files will follow symbolic
+        links for the WAL directory and each configured tablespace.
+       
+       
+        On Linux, syncfs may be used instead to ask the
+        operating system to synchronize the whole file systems that contain the
+        data directory, the WAL files, and each tablespace.  See
+         for information about
+        the caveats to be aware of when using syncfs.
+       
+       
+        This option has no effect when --no-sync is used.
+       
+      
+     
+
+     
+      -S
+      --sync-only
+      
+       
+        Safely write all database files to disk and exit.  This does not
+        perform any of the normal initdb operations.
+        Generally, this option is useful for ensuring reliable recovery after
+        changing  from off to
+        on.
+       
+      
+