mirror of
https://github.com/postgres/postgres.git
synced 2025-07-28 23:42:10 +03:00
Fixup pg_dumpall adding --lock-wait-timeout, to match pg_dump.
David Gould
This commit is contained in:
@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dumpall.sgml,v 1.72 2008/04/13 03:49:21 tgl Exp $
|
||||
$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dumpall.sgml,v 1.73 2008/08/29 17:28:43 alvherre Exp $
|
||||
PostgreSQL documentation
|
||||
-->
|
||||
|
||||
@ -195,6 +195,22 @@ PostgreSQL documentation
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><option>--lock-wait-timeout=<replaceable class="parameter">timeout</replaceable></option></term>
|
||||
<listitem>
|
||||
<para>
|
||||
Do not wait forever to acquire shared table locks at the beginning of
|
||||
the dump. Instead fail if unable to lock a table within the specified
|
||||
<replaceable class="parameter">timeout</>. The timeout may be
|
||||
specified in any of the formats accepted by <command>SET
|
||||
statement_timeout</>. (Allowed values vary depending on the server
|
||||
version you are dumping from, but an integer number of milliseconds
|
||||
is accepted by all versions since 7.3. This option is ignored when
|
||||
dumping from a pre-7.3 server.)
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><option>--no-tablespaces</option></term>
|
||||
<listitem>
|
||||
|
Reference in New Issue
Block a user