Skip to content

P
Postgres FD Implementation
Commit 238d21d7 authored by Bruce Momjian's avatar Bruce Momjian
Browse files
Options

Modify pg_standby, pgbench, and pg_upgrade manual pages to be consistent 

in their display of command-line options with other client applications.
parent 7ff79fa4
Hide whitespace changes
Inline Side-by-side
Showing with 411 additions and 329 deletions
contrib/pg_upgrade/option.c
View file @ 238d21d7
...@@ -226,21 +226,21 @@ usage(migratorContext *ctx) ...@@ -226,21 +226,21 @@ usage(migratorContext *ctx)
printf(_("\nUsage: pg_upgrade [OPTIONS]...\n\ printf(_("\nUsage: pg_upgrade [OPTIONS]...\n\
\n\ \n\
Options:\n\ Options:\n\
-b, --old-bindir=OLDBINDIR old cluster executable directory\n\ -b, --old-bindir=old_bindir old cluster executable directory\n\
-B, --new-bindir=NEWBINDIR new cluster executable directory\n\ -B, --new-bindir=new_bindir new cluster executable directory\n\
-c, --check check clusters only, don't change any data\n\ -c, --check check clusters only, don't change any data\n\
-d, --old-datadir=OLDDATADIR old cluster data directory\n\ -d, --old-datadir=old_datadir old cluster data directory\n\
-D, --new-datadir=NEWDATADIR new cluster data directory\n\ -D, --new-datadir=new_datadir new cluster data directory\n\
-g, --debug enable debugging\n\ -g, --debug enable debugging\n\
-G, --debugfile=DEBUGFILENAME output debugging activity to file\n\ -G, --debugfile=debug_filename output debugging activity to file\n\
-k, --link link instead of copying files to new cluster\n\ -k, --link link instead of copying files to new cluster\n\
-l, --logfile=LOGFILENAME log session activity to file\n\ -l, --logfile=log_filename log session activity to file\n\
-p, --old-port=portnum old cluster port number (default %d)\n\ -p, --old-port=old_portnum old cluster port number (default %d)\n\
-P, --new-port=portnum new cluster port number (default %d)\n\ -P, --new-port=new_portnum new cluster port number (default %d)\n\
-u, --user=username clusters superuser (default \"%s\")\n\ -u, --user=username clusters superuser (default \"%s\")\n\
-v, --verbose enable verbose output\n\ -v, --verbose enable verbose output\n\
-V, --version display version information, then exit\n\ -V, --version display version information, then exit\n\
-h, --help show this help, then exit\n\ -h, --help show this help, then exit\n\
\n\ \n\
Before running pg_upgrade you must:\n\ Before running pg_upgrade you must:\n\
create a new database cluster (using the new version of initdb)\n\ create a new database cluster (using the new version of initdb)\n\
......
doc/src/sgml/oid2name.sgml
View file @ 238d21d7
<!-- $PostgreSQL: pgsql/doc/src/sgml/oid2name.sgml,v 1.7 2010/05/20 03:45:38 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/oid2name.sgml,v 1.8 2010/05/25 15:55:28 momjian Exp $ -->
<sect1 id="oid2name"> <sect1 id="oid2name">
<title>oid2name</title> <title>oid2name</title>
...@@ -36,7 +36,7 @@ ...@@ -36,7 +36,7 @@
</sect2> </sect2>
<sect2> <sect2>
<title><application>oid2name</> options</title> <title><application>oid2name</> Options</title>
<para> <para>
<application>oid2name</application> accepts the following command-line arguments: <application>oid2name</application> accepts the following command-line arguments:
......
doc/src/sgml/pgbench.sgml
View file @ 238d21d7
<!-- $PostgreSQL: pgsql/doc/src/sgml/pgbench.sgml,v 1.15 2010/04/23 23:21:43 rhaas Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/pgbench.sgml,v 1.16 2010/05/25 15:55:28 momjian Exp $ -->
<sect1 id="pgbench"> <sect1 id="pgbench">
<title>pgbench</title> <title>pgbench</title>
...@@ -116,218 +116,285 @@ pgbench <optional> <replaceable>options</> </optional> <replaceable>dbname</> ...@@ -116,218 +116,285 @@ pgbench <optional> <replaceable>options</> </optional> <replaceable>dbname</>
in both cases. in both cases.
</para> </para>
<table id="pgbench-init-options"> </sect2>
<title><application>pgbench</application> initialization options</title>
<tgroup cols="2"> <sect2 id="pgbench-init-options">
<thead> <title><application>pgbench</> Initialization Options</title>
<row>
<entry>Option</entry> <para>
<entry>Description</entry> <application>pgbench</application> accepts the following command-line
</row> initialization arguments:
</thead>
<variablelist>
<tbody>
<row> <varlistentry>
<entry><literal>-i</literal></entry> <term><option>-F</option> <replaceable>fillfactor</></term>
<entry> <listitem>
Required to invoke initialization mode. <para>
</entry> Create the <structname>pgbench_accounts</>,
</row> <structname>pgbench_tellers</> and
<row> <structname>pgbench_branches</> tables with the given fillfactor.
<entry><literal>-s</literal> <replaceable>scale_factor</></entry> Default is 100.
<entry> </para>
Multiply the number of rows generated by the scale factor. </listitem>
For example, <literal>-s 100</> will create 10,000,000 rows </varlistentry>
in the <structname>pgbench_accounts</> table. Default is 1.
</entry> <varlistentry>
</row> <term><option>-i</option></term>
<row> <listitem>
<entry><literal>-F</literal> <replaceable>fillfactor</></entry> <para>
<entry> Required to invoke initialization mode.
Create the <structname>pgbench_accounts</>, </para>
<structname>pgbench_tellers</> and </listitem>
<structname>pgbench_branches</> tables with the given fillfactor. </varlistentry>
Default is 100.
</entry> <varlistentry>
</row> <term><option>-s</option> <replaceable>scale_factor</></term>
</tbody> <listitem>
</tgroup> <para>
</table> Multiply the number of rows generated by the scale factor.
For example, <literal>-s 100</> will create 10,000,000 rows
<table id="pgbench-run-options"> in the <structname>pgbench_accounts</> table. Default is 1.
<title><application>pgbench</application> benchmarking options</title> </para>
<tgroup cols="2"> </listitem>
<thead> </varlistentry>
<row>
<entry>Option</entry> </variablelist>
<entry>Description</entry> </para>
</row>
</thead> </sect2>
<tbody> <sect2 id="pgbench-run-options">
<row> <title><application>pgbench</> Benchmarking Options</title>
<entry><literal>-c</literal> <replaceable>clients</></entry>
<entry> <para>
Number of clients simulated, that is, number of concurrent database <application>pgbench</application> accepts the following command-line
sessions. Default is 1. benchmarking arguments:
</entry>
</row> <variablelist>
<row>
<entry><literal>-j</literal> <replaceable>threads</></entry> <varlistentry>
<entry> <term><option>-c</option> <replaceable>clients</></term>
Number of worker threads within <application>pgbench</application>. <listitem>
Using more than one thread can be helpful on multi-CPU machines. <para>
The number of clients must be a multiple of the number of threads, Number of clients simulated, that is, number of concurrent database
since each thread is given the same number of client sessions to manage. sessions. Default is 1.
Default is 1. </para>
</entry> </listitem>
</row> </varlistentry>
<row>
<entry><literal>-t</literal> <replaceable>transactions</></entry> <varlistentry>
<entry> <term><option>-C</option></term>
Number of transactions each client runs. Default is 10. <listitem>
</entry> <para>
</row> Establish a new connection for each transaction, rather than
<row> doing it just once per client session.
<entry><literal>-T</literal> <replaceable>seconds</></entry> This is useful to measure the connection overhead.
<entry> </para>
Run the test for this many seconds, rather than a fixed number of </listitem>
transactions per client. <literal>-t</literal> and </varlistentry>
<literal>-T</literal> are mutually exclusive.
</entry> <varlistentry>
</row> <term><option>-d</option></term>
<row> <listitem>
<entry><literal>-M</literal> <replaceable>querymode</></entry> <para>
<entry> Print debugging output.
Protocol to use for submitting queries to the server: </para>
<itemizedlist> </listitem>
<listitem> </varlistentry>
<para><literal>simple</>: use simple query protocol.</para>
</listitem> <varlistentry>
<listitem> <term><option>-D</option> <replaceable>varname</><literal>=</><replaceable>value</></term>
<para><literal>extended</>: use extended query protocol.</para> <listitem>
</listitem> <para>
<listitem> Define a variable for use by a custom script (see below).
<para><literal>prepared</>: use extended query protocol with prepared statements.</para> Multiple <literal>-D</> options are allowed.
</listitem> </para>
</itemizedlist> </listitem>
The default is simple query protocol. (See <xref linkend="protocol"> </varlistentry>
for more information.)
</entry> <varlistentry>
</row> <term><option>-f</option> <replaceable>filename</></term>
<row> <listitem>
<entry><literal>-N</literal></entry> <para>
<entry> Read transaction script from <replaceable>filename</>.
Do not update <structname>pgbench_tellers</> and See below for details.
<structname>pgbench_branches</>. <literal>-N</literal>, <literal>-S</literal>, and <literal>-f</literal>
This will avoid update contention on these tables, but are mutually exclusive.
it makes the test case even less like TPC-B. </para>
</entry> </listitem>
</row> </varlistentry>
<row>
<entry><literal>-S</literal></entry> <varlistentry>
<entry> <term><option>-j</option> <replaceable>threads</></term>
Perform select-only transactions instead of TPC-B-like test. <listitem>
</entry> <para>
</row> Number of worker threads within <application>pgbench</application>.
<row> Using more than one thread can be helpful on multi-CPU machines.
<entry><literal>-f</literal> <replaceable>filename</></entry> The number of clients must be a multiple of the number of threads,
<entry> since each thread is given the same number of client sessions to manage.
Read transaction script from <replaceable>filename</>. Default is 1.
See below for details. </para>
<literal>-N</literal>, <literal>-S</literal>, and <literal>-f</literal> </listitem>
are mutually exclusive. </varlistentry>
</entry>
</row> <varlistentry>
<row> <term><option>-l</option></term>
<entry><literal>-n</literal></entry> <listitem>
<entry> <para>
Perform no vacuuming before running the test. Write the time taken by each transaction to a logfile.
This option is <emphasis>necessary</> See below for details.
if you are running a custom test scenario that does not include </para>
the standard tables <structname>pgbench_accounts</>, </listitem>
<structname>pgbench_branches</>, <structname>pgbench_history</>, and </varlistentry>
<structname>pgbench_tellers</>.
</entry> <varlistentry>
</row> <term><option>-M</option> <replaceable>querymode</></term>
<row> <listitem>
<entry><literal>-v</literal></entry> <para>
<entry> Protocol to use for submitting queries to the server:
Vacuum all four standard tables before running the test. <itemizedlist>
With neither <literal>-n</> nor <literal>-v</>, pgbench will vacuum the <listitem>
<structname>pgbench_tellers</> and <structname>pgbench_branches</> <para><literal>simple</>: use simple query protocol.</para>
tables, and will truncate <structname>pgbench_history</>. </listitem>
</entry> <listitem>
</row> <para><literal>extended</>: use extended query protocol.</para>
<row> </listitem>
<entry><literal>-D</literal> <replaceable>varname</><literal>=</><replaceable>value</></entry> <listitem>
<entry> <para><literal>prepared</>: use extended query protocol with prepared statements.</para>
Define a variable for use by a custom script (see below). </listitem>
Multiple <literal>-D</> options are allowed. </itemizedlist>
</entry> The default is simple query protocol. (See <xref linkend="protocol">
</row> for more information.)
<row> </para>
<entry><literal>-C</literal></entry> </listitem>
<entry> </varlistentry>
Establish a new connection for each transaction, rather than
doing it just once per client session. <varlistentry>
This is useful to measure the connection overhead. <term><option>-n</option></term>
</entry> <listitem>
</row> <para>
<row> Perform no vacuuming before running the test.
<entry><literal>-l</literal></entry> This option is <emphasis>necessary</>
<entry> if you are running a custom test scenario that does not include
Write the time taken by each transaction to a logfile. the standard tables <structname>pgbench_accounts</>,
See below for details. <structname>pgbench_branches</>, <structname>pgbench_history</>, and
</entry> <structname>pgbench_tellers</>.
</row> </para>
<row> </listitem>
<entry><literal>-s</literal> <replaceable>scale_factor</></entry> </varlistentry>
<entry>
Report the specified scale factor in <application>pgbench</>'s <varlistentry>
output. With the built-in tests, this is not necessary; the <term><option>-N</option></term>
correct scale factor will be detected by counting the number of <listitem>
rows in the <structname>pgbench_branches</> table. However, when testing <para>
custom benchmarks (<literal>-f</> option), the scale factor Do not update <structname>pgbench_tellers</> and
will be reported as 1 unless this option is used. <structname>pgbench_branches</>.
</entry> This will avoid update contention on these tables, but
</row> it makes the test case even less like TPC-B.
<row> </para>
<entry><literal>-d</literal></entry> </listitem>
<entry> </varlistentry>
Print debugging output.
</entry> <varlistentry>
</row> <term><option>-s</option> <replaceable>scale_factor</></term>
</tbody> <listitem>
</tgroup> <para>
</table> Report the specified scale factor in <application>pgbench</>'s
output. With the built-in tests, this is not necessary; the
<table id="pgbench-common-options"> correct scale factor will be detected by counting the number of
<title><application>pgbench</application> common options</title> rows in the <structname>pgbench_branches</> table. However, when testing
<tgroup cols="2"> custom benchmarks (<literal>-f</> option), the scale factor
<thead> will be reported as 1 unless this option is used.
<row> </para>
<entry>Option</entry> </listitem>
<entry>Description</entry> </varlistentry>
</row>
</thead> <varlistentry>
<term><option>-S</option></term>
<tbody> <listitem>
<row> <para>
<entry><literal>-h</literal> <replaceable>hostname</></entry> Perform select-only transactions instead of TPC-B-like test.
<entry>database server's host</entry> </para>
</row> </listitem>
<row> </varlistentry>
<entry><literal>-p</literal> <replaceable>port</></entry>
<entry>database server's port</entry> <varlistentry>
</row> <term><option>-t</option> <replaceable>transactions</></term>
<row> <listitem>
<entry><literal>-U</literal> <replaceable>login</></entry> <para>
<entry>username to connect as</entry> Number of transactions each client runs. Default is 10.
</row> </para>
</tbody> </listitem>
</tgroup> </varlistentry>
</table>
<varlistentry>
<term><option>-T</option> <replaceable>seconds</></term>
<listitem>
<para>
Run the test for this many seconds, rather than a fixed number of
transactions per client. <literal>-t</literal> and
<literal>-T</literal> are mutually exclusive.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-v</option></term>
<listitem>
<para>
Vacuum all four standard tables before running the test.
With neither <literal>-n</> nor <literal>-v</>, pgbench will vacuum the
<structname>pgbench_tellers</> and <structname>pgbench_branches</>
tables, and will truncate <structname>pgbench_history</>.
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
</sect2>
<sect2 id="pgbench-common-options">
<title><application>pgbench</> Common Options</title>
<para>
<application>pgbench</application> accepts the following command-line
common arguments:
<variablelist>
<varlistentry>
<term><option>-h</option> <replaceable>hostname</></term>
<listitem>
<para>
The database server's hostname
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-p</option> <replaceable>port</></term>
<listitem>
<para>
The database server's port number
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-U</option> <replaceable>login</></term>
<listitem>
<para>
The username to connect as
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
</sect2> </sect2>
<sect2> <sect2>
......
doc/src/sgml/pgstandby.sgml
View file @ 238d21d7
<!-- $PostgreSQL: pgsql/doc/src/sgml/pgstandby.sgml,v 2.10 2009/06/25 12:03:11 heikki Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/pgstandby.sgml,v 2.11 2010/05/25 15:55:28 momjian Exp $ -->
<sect1 id="pgstandby"> <sect1 id="pgstandby">
<title>pg_standby</title> <title>pg_standby</title>
...@@ -122,99 +122,114 @@ pg_standby <optional> <replaceable>option</> ... </optional> <replaceable>archiv ...@@ -122,99 +122,114 @@ pg_standby <optional> <replaceable>option</> ... </optional> <replaceable>archiv
</variablelist> </variablelist>
</para> </para>
<table> </sect2>
<title><application>pg_standby</> options</title>
<tgroup cols="3"> <sect2>
<thead> <title><application>pg_standby</> Options</title>
<row>
<entry>Option</entry> <para>
<entry>Default</entry> <application>pg_standby</application> accepts the following command-line arguments:
<entry>Description</entry>
</row> <variablelist>
</thead>
<tbody> <varlistentry>
<row> <term><option>-c</option></term>
<entry><literal>-c</></entry> <listitem>
<entry>yes</entry> <para>
<entry> Use <literal>cp</> or <literal>copy</> command to restore WAL files
Use <literal>cp</> or <literal>copy</> command to restore WAL files from archive. This is the only supported behavior so this option is useless.
from archive. </para>
</entry> </listitem>
</row> </varlistentry>
<row>
<entry><literal>-d</></entry> <varlistentry>
<entry>no</entry> <term><option>-d</option></term>
<entry>Print lots of debug logging output on <filename>stderr</>.</entry> <listitem>
</row> <para>
<row> Print lots of debug logging output on <filename>stderr</>.
<entry><literal>-k</> <replaceable>numfiles</></entry> </para>
<entry>0</entry> </listitem>
<entry> </varlistentry>
Remove files from <replaceable>archivelocation</replaceable> so that
no more than this many WAL files before the current one are kept in the <varlistentry>
archive. Zero (the default) means not to remove any files from <term><option>-k</option></term>
<replaceable>archivelocation</replaceable>. <listitem>
This parameter will be silently ignored if <para>
<replaceable>restartwalfile</replaceable> is specified, since that Remove files from <replaceable>archivelocation</replaceable> so that
specification method is more accurate in determining the correct no more than this many WAL files before the current one are kept in the
archive cut-off point. archive. Zero (the default) means not to remove any files from
Use of this parameter is <emphasis>deprecated</> as of <replaceable>archivelocation</replaceable>.
<productname>PostgreSQL</> 8.3; it is safer and more efficient to This parameter will be silently ignored if
specify a <replaceable>restartwalfile</replaceable> parameter. A too <replaceable>restartwalfile</replaceable> is specified, since that
small setting could result in removal of files that are still needed specification method is more accurate in determining the correct
for a restart of the standby server, while a too large setting wastes archive cut-off point.
archive space. Use of this parameter is <emphasis>deprecated</> as of
</entry> <productname>PostgreSQL</> 8.3; it is safer and more efficient to
</row> specify a <replaceable>restartwalfile</replaceable> parameter. A too
<row> small setting could result in removal of files that are still needed
<entry><literal>-r</> <replaceable>maxretries</></entry> for a restart of the standby server, while a too large setting wastes
<entry>3</entry> archive space.
<entry> </para>
Set the maximum number of times to retry the copy command if it </listitem>
fails. After each failure, we wait for <replaceable>sleeptime</> * </varlistentry>
<replaceable>num_retries</>
<varlistentry>
<term><option>-r</option> <replaceable>maxretries</></term>
<listitem>
<para>
Set the maximum number of times to retry the copy command if
it fails (default 3). After each failure, we wait for
<replaceable>sleeptime</> * <replaceable>num_retries</>
so that the wait time increases progressively. So by default, so that the wait time increases progressively. So by default,
we will wait 5 secs, 10 secs, then 15 secs before reporting we will wait 5 secs, 10 secs, then 15 secs before reporting
the failure back to the standby server. This will be the failure back to the standby server. This will be
interpreted as end of recovery and the standby will come interpreted as end of recovery and the standby will come
up fully as a result. up fully as a result.
</entry> </para>
</row> </listitem>
<row> </varlistentry>
<entry><literal>-s</> <replaceable>sleeptime</></entry>
<entry>5</entry> <varlistentry>
<entry> <term><option>-s</option> <replaceable>sleeptime</></term>
Set the number of seconds (up to 60) to sleep between tests to see <listitem>
if the WAL file to be restored is available in the archive yet. <para>
The default setting is not necessarily recommended; Set the number of seconds (up to 60, default 5) to sleep between
consult <xref linkend="warm-standby"> for discussion. tests to see if the WAL file to be restored is available in
</entry> the archive yet. The default setting is not necessarily
</row> recommended; consult <xref linkend="warm-standby"> for discussion.
<row> </para>
<entry><literal>-t</> <replaceable>triggerfile</></entry> </listitem>
<entry>none</entry> </varlistentry>
<entry>
Specify a trigger file whose presence should cause failover. <varlistentry>
It is recommended that you use a structured filename to <term><option>-t</option> <replaceable>triggerfile</></term>
avoid confusion as to which server is being triggered <listitem>
when multiple servers exist on the same system; for example <para>
<filename>/tmp/pgsql.trigger.5432</>. Specify a trigger file whose presence should cause failover.
</entry> It is recommended that you use a structured filename to
</row> avoid confusion as to which server is being triggered
<row> when multiple servers exist on the same system; for example
<entry><literal>-w</> <replaceable>maxwaittime</></entry> <filename>/tmp/pgsql.trigger.5432</>.
<entry>0</entry> </para>
<entry> </listitem>
Set the maximum number of seconds to wait for the next WAL file, </varlistentry>
after which a fast failover will be performed.
A setting of zero (the default) means wait forever. <varlistentry>
The default setting is not necessarily recommended; <term><option>-w</option> <replaceable>maxwaittime</></term>
consult <xref linkend="warm-standby"> for discussion. <listitem>
</entry> <para>
</row> Set the maximum number of seconds to wait for the next WAL file,
</tbody> after which a fast failover will be performed.
</tgroup> A setting of zero (the default) means wait forever.
</table> The default setting is not necessarily recommended;
consult <xref linkend="warm-standby"> for discussion.
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
</sect2> </sect2>
<sect2> <sect2>
......
doc/src/sgml/pgupgrade.sgml
View file @ 238d21d7
<!-- $PostgreSQL: pgsql/doc/src/sgml/pgupgrade.sgml,v 1.11 2010/05/25 14:50:56 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/pgupgrade.sgml,v 1.12 2010/05/25 15:55:28 momjian Exp $ -->
<sect1 id="pgupgrade"> <sect1 id="pgupgrade">
<title>pg_upgrade</title> <title>pg_upgrade</title>
...@@ -38,7 +38,7 @@ ...@@ -38,7 +38,7 @@
</sect2> </sect2>
<sect2> <sect2>
<title><application>pg_upgrade</> options</title> <title><application>pg_upgrade</> Options</title>
<para> <para>
<application>pg_upgrade</application> accepts the following command-line arguments: <application>pg_upgrade</application> accepts the following command-line arguments:
...@@ -46,13 +46,13 @@ ...@@ -46,13 +46,13 @@
<variablelist> <variablelist>
<varlistentry> <varlistentry>
<term><option>-b</option> <replaceable>OLDBINDIR</></term> <term><option>-b</option> <replaceable>old_bindir</></term>
<term><option>--old-bindir</option> <replaceable>OLDBINDIR</></term> <term><option>--old-bindir</option> <replaceable>OLDBINDIR</></term>
<listitem><para>specify the old cluster executable directory</para></listitem> <listitem><para>specify the old cluster executable directory</para></listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term><option>-B</option> <replaceable>NEWBINDIR</></term> <term><option>-B</option> <replaceable>new_bindir</></term>
<term><option>--new-bindir</option> <replaceable>NEWBINDIR</></term> <term><option>--new-bindir</option> <replaceable>NEWBINDIR</></term>
<listitem><para>specify the new cluster executable directory</para></listitem> <listitem><para>specify the new cluster executable directory</para></listitem>
</varlistentry> </varlistentry>
...@@ -64,13 +64,13 @@ ...@@ -64,13 +64,13 @@
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term><option>-d</option> <replaceable>OLDDATADIR</></term> <term><option>-d</option> <replaceable>old_datadir</></term>
<term><option>--old-datadir</option> <replaceable>OLDDATADIR</></term> <term><option>--old-datadir</option> <replaceable>OLDDATADIR</></term>
<listitem><para>specify the old cluster data directory</para></listitem> <listitem><para>specify the old cluster data directory</para></listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term><option>-D</option> <replaceable>NEWDATADIR</></term> <term><option>-D</option> <replaceable>new_datadir</></term>
<term><option>--new-datadir</option> <replaceable>NEWDATADIR</></term> <term><option>--new-datadir</option> <replaceable>NEWDATADIR</></term>
<listitem><para>specify the new cluster data directory</para></listitem> <listitem><para>specify the new cluster data directory</para></listitem>
</varlistentry> </varlistentry>
...@@ -82,7 +82,7 @@ ...@@ -82,7 +82,7 @@
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term><option>-G</option> <replaceable>DEBUGFILENAME</></term> <term><option>-G</option> <replaceable>debug_filename</></term>
<term><option>--debugfile</option> <replaceable>DEBUGFILENAME</></term> <term><option>--debugfile</option> <replaceable>DEBUGFILENAME</></term>
<listitem><para>output debugging activity to file</para></listitem> <listitem><para>output debugging activity to file</para></listitem>
</varlistentry> </varlistentry>
...@@ -94,19 +94,19 @@ ...@@ -94,19 +94,19 @@
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term><option>-l</option> <replaceable>LOGFILENAME</></term> <term><option>-l</option> <replaceable>log_filename</></term>
<term><option>--logfile</option> <replaceable>LOGFILENAME</></term> <term><option>--logfile</option> <replaceable>LOGFILENAME</></term>
<listitem><para>log session activity to file</para></listitem> <listitem><para>log session activity to file</para></listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term><option>-p</option> <replaceable>portnum</></term> <term><option>-p</option> <replaceable>old_portnum</></term>
<term><option>--old-port</option> <replaceable>portnum</></term> <term><option>--old-port</option> <replaceable>portnum</></term>
<listitem><para>specify the old cluster port number</para></listitem> <listitem><para>specify the old cluster port number</para></listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term><option>-P</option> <replaceable>portnum</></term> <term><option>-P</option> <replaceable>new_portnum</></term>
<term><option>--new-port</option> <replaceable>portnum</></term> <term><option>--new-port</option> <replaceable>portnum</></term>
<listitem><para>specify the new cluster port number</para></listitem> <listitem><para>specify the new cluster port number</para></listitem>
</varlistentry> </varlistentry>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment