From 77a69a2ed165c31a981ac553f56c7b43e12d9ab5 Mon Sep 17 00:00:00 2001
From: Bruce Momjian
Date: Fri, 10 Aug 2001 14:30:15 +0000
Subject: Patch to LOCK multiple tables in one LOCK command.
Neil Padgett
---
doc/src/sgml/ref/lock.sgml | 16 ++++++++++++----
1 file changed, 12 insertions(+), 4 deletions(-)
(limited to 'doc/src')
diff --git a/doc/src/sgml/ref/lock.sgml b/doc/src/sgml/ref/lock.sgml
index 20530d75d71..b66f42e7ebc 100644
--- a/doc/src/sgml/ref/lock.sgml
+++ b/doc/src/sgml/ref/lock.sgml
@@ -1,5 +1,5 @@
@@ -15,7 +15,7 @@ Postgres documentation
LOCK
- Explicitly lock a table inside a transaction
+ Explicitly lock a table / tables inside a transaction
@@ -23,8 +23,8 @@ Postgres documentation
2001-07-09
-LOCK [ TABLE ] name
-LOCK [ TABLE ] name IN lockmode MODE
+LOCK [ TABLE ] name [, ...]
+LOCK [ TABLE ] name [, ...] IN lockmode MODE
where lockmode is one of:
@@ -373,6 +373,7 @@ ERROR name: Table does not exist.
An example for this rule was given previously when discussing the
use of SHARE ROW EXCLUSIVE mode rather than SHARE mode.
+
@@ -383,6 +384,12 @@ ERROR name: Table does not exist.
+
+ When locking multiple tables, the command LOCK a, b; is equivalent to LOCK
+ a; LOCK b;. The tables are locked one-by-one in the order specified in the
+ LOCK command.
+
+
1999-06-08
@@ -406,6 +413,7 @@ ERROR name: Table does not exist.
LOCK works only inside transactions.
+
--
cgit v1.2.3