mirror of
https://github.com/postgres/postgres.git
synced 2025-04-22 23:02:54 +03:00
doc: Improve order of options on pg_upgrade reference page
Put the new long-only options in a location that is consistent with the existing long-only options and also the --help output.
This commit is contained in:
parent
4364e0126e
commit
84f08f2215
@ -190,29 +190,6 @@ PostgreSQL documentation
|
|||||||
variable <envar>PGSOCKETDIR</envar></para></listitem>
|
variable <envar>PGSOCKETDIR</envar></para></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
|
||||||
<term><option>--sync-method=</option><replaceable>method</replaceable></term>
|
|
||||||
<listitem>
|
|
||||||
<para>
|
|
||||||
When set to <literal>fsync</literal>, which is the default,
|
|
||||||
<command>pg_upgrade</command> will recursively open and synchronize all
|
|
||||||
files in the upgraded cluster's data directory. The search for files
|
|
||||||
will follow symbolic links for the WAL directory and each configured
|
|
||||||
tablespace.
|
|
||||||
</para>
|
|
||||||
<para>
|
|
||||||
On Linux, <literal>syncfs</literal> may be used instead to ask the
|
|
||||||
operating system to synchronize the whole file systems that contain the
|
|
||||||
upgraded cluster's data directory, its WAL files, and each tablespace.
|
|
||||||
See <xref linkend="guc-recovery-init-sync-method"/> for information
|
|
||||||
about the caveats to be aware of when using <literal>syncfs</literal>.
|
|
||||||
</para>
|
|
||||||
<para>
|
|
||||||
This option has no effect when <option>--no-sync</option> is used.
|
|
||||||
</para>
|
|
||||||
</listitem>
|
|
||||||
</varlistentry>
|
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><option>-U</option> <replaceable>username</replaceable></term>
|
<term><option>-U</option> <replaceable>username</replaceable></term>
|
||||||
<term><option>--username=</option><replaceable>username</replaceable></term>
|
<term><option>--username=</option><replaceable>username</replaceable></term>
|
||||||
@ -276,6 +253,29 @@ PostgreSQL documentation
|
|||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
|
<varlistentry>
|
||||||
|
<term><option>--sync-method=</option><replaceable>method</replaceable></term>
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
When set to <literal>fsync</literal>, which is the default,
|
||||||
|
<command>pg_upgrade</command> will recursively open and synchronize all
|
||||||
|
files in the upgraded cluster's data directory. The search for files
|
||||||
|
will follow symbolic links for the WAL directory and each configured
|
||||||
|
tablespace.
|
||||||
|
</para>
|
||||||
|
<para>
|
||||||
|
On Linux, <literal>syncfs</literal> may be used instead to ask the
|
||||||
|
operating system to synchronize the whole file systems that contain the
|
||||||
|
upgraded cluster's data directory, its WAL files, and each tablespace.
|
||||||
|
See <xref linkend="guc-recovery-init-sync-method"/> for information
|
||||||
|
about the caveats to be aware of when using <literal>syncfs</literal>.
|
||||||
|
</para>
|
||||||
|
<para>
|
||||||
|
This option has no effect when <option>--no-sync</option> is used.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><option>-?</option></term>
|
<term><option>-?</option></term>
|
||||||
<term><option>--help</option></term>
|
<term><option>--help</option></term>
|
||||||
|
Loading…
x
Reference in New Issue
Block a user