diff options
| -rw-r--r-- | doc/src/sgml/ref/pg_dump.sgml | 39 | ||||
| -rw-r--r-- | doc/src/sgml/ref/pg_restore.sgml | 22 | ||||
| -rw-r--r-- | doc/src/sgml/ref/pgbench.sgml | 26 |
3 files changed, 47 insertions, 40 deletions
diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index bc286841e17..be1b684082d 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -545,23 +545,6 @@ PostgreSQL documentation </varlistentry> <varlistentry> - <term><option>--strict-names</></term> - <listitem> - <para> - Require that each schema (-n / --schema) and table (-t / --table) - qualifier match at least one schema/table in the database to be dumped. - Note that if none of the schema/table qualifiers find matches pg_dump - will generate an error even without --strict-names. - </para> - <para> - This option has no effect on -N/--exclude-schema, -T/--exclude_table - or --exclude-table-date. An exclude pattern failing to match - any objects is not considered an error. - </para> - </listitem> - </varlistentry> - - <varlistentry> <term><option>-T <replaceable class="parameter">table</replaceable></option></term> <term><option>--exclude-table=<replaceable class="parameter">table</replaceable></option></term> <listitem> @@ -926,6 +909,28 @@ PostgreSQL documentation </varlistentry> <varlistentry> + <term><option>--strict-names</></term> + <listitem> + <para> + Require that each schema + (<option>-n</option>/<option>--schema</option>) and table + (<option>-t</option>/<option>--table</option>) qualifier match at + least one schema/table in the database to be dumped. Note that if + none of the schema/table qualifiers find + matches, <application>pg_dump</application> will generate an error + even without <option>--strict-names</option>. + </para> + <para> + This option has no effect + on <option>-N</option>/<option>--exclude-schema</option>, + <option>-T</option>/<option>--exclude-table</option>, + or <option>--exclude-table-data</option>. An exclude pattern failing + to match any objects is not considered an error. + </para> + </listitem> + </varlistentry> + + <varlistentry> <term><option>--use-set-session-authorization</></term> <listitem> <para> diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml index 66d09f42090..c9069193afc 100644 --- a/doc/src/sgml/ref/pg_restore.sgml +++ b/doc/src/sgml/ref/pg_restore.sgml @@ -432,16 +432,6 @@ </varlistentry> <varlistentry> - <term><option>--strict-names</></term> - <listitem> - <para> - Require that each schema (-n / --schema) and table (-t / --table) - qualifier match at least one schema/table in the backup file. - </para> - </listitem> - </varlistentry> - - <varlistentry> <term><option>-T <replaceable class="parameter">trigger</replaceable></option></term> <term><option>--trigger=<replaceable class="parameter">trigger</replaceable></option></term> <listitem> @@ -616,6 +606,18 @@ </varlistentry> <varlistentry> + <term><option>--strict-names</></term> + <listitem> + <para> + Require that each schema + (<option>-n</option>/<option>--schema</option>) and table + (<option>-t</option>/<option>--table</option>) qualifier match at + least one schema/table in the backup file. + </para> + </listitem> + </varlistentry> + + <varlistentry> <term><option>--use-set-session-authorization</option></term> <listitem> <para> diff --git a/doc/src/sgml/ref/pgbench.sgml b/doc/src/sgml/ref/pgbench.sgml index 50a14f67f3a..f3afedb0409 100644 --- a/doc/src/sgml/ref/pgbench.sgml +++ b/doc/src/sgml/ref/pgbench.sgml @@ -445,19 +445,6 @@ pgbench <optional> <replaceable>options</> </optional> <replaceable>dbname</> </varlistentry> <varlistentry> - <term><option>--progress-timestamp</option></term> - <listitem> - <para> - When showing progress (option <option>-P</>), use a timestamp - (Unix epoch) instead of the number of seconds since the - beginning of the run. The unit is in seconds, with millisecond - precision after the dot. - This helps compare logs generated by various tools. - </para> - </listitem> - </varlistentry> - - <varlistentry> <term><option>-r</option></term> <term><option>--report-latencies</option></term> <listitem> @@ -597,6 +584,19 @@ pgbench <optional> <replaceable>options</> </optional> <replaceable>dbname</> </varlistentry> <varlistentry> + <term><option>--progress-timestamp</option></term> + <listitem> + <para> + When showing progress (option <option>-P</>), use a timestamp + (Unix epoch) instead of the number of seconds since the + beginning of the run. The unit is in seconds, with millisecond + precision after the dot. + This helps compare logs generated by various tools. + </para> + </listitem> + </varlistentry> + + <varlistentry> <term><option>--sampling-rate=<replaceable>rate</></option></term> <listitem> <para> |