From 7ad60b49dc61d7757012f84e2fb88e4e6d30995d Mon Sep 17 00:00:00 2001
From: Alvaro Herrera
Date: Fri, 29 Aug 2008 17:28:43 +0000
Subject: Fixup pg_dumpall adding --lock-wait-timeout, to match pg_dump.
David Gould
---
doc/src/sgml/ref/pg_dumpall.sgml | 18 +++++++++++++++++-
1 file changed, 17 insertions(+), 1 deletion(-)
(limited to 'doc/src')
diff --git a/doc/src/sgml/ref/pg_dumpall.sgml b/doc/src/sgml/ref/pg_dumpall.sgml
index a8715fbd7a..df3d8521d6 100644
--- a/doc/src/sgml/ref/pg_dumpall.sgml
+++ b/doc/src/sgml/ref/pg_dumpall.sgml
@@ -1,5 +1,5 @@
@@ -195,6 +195,22 @@ PostgreSQL documentation
+
+
+
+
+ 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
+ timeout>. The timeout may be
+ specified in any of the formats accepted by 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.)
+
+
+
+
--
cgit v1.2.3