From e1ea7cc2e562b9e61528f37affada72a08a8adeb Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Thu, 3 Jun 1999 19:18:00 +0000 Subject: Update lock sgml/man/psql help pages. --- doc/src/sgml/ref/lock.sgml | 23 +++++------------------ 1 file changed, 5 insertions(+), 18 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/ref/lock.sgml b/doc/src/sgml/ref/lock.sgml index dc702b0cdb8..804872d4a10 100644 --- a/doc/src/sgml/ref/lock.sgml +++ b/doc/src/sgml/ref/lock.sgml @@ -18,7 +18,7 @@ 1998-09-24 - LOCK [ TABLE ] table + LOCK [ TABLE ] [[IN] [ROW|ACCESS] [SHARE|EXCLUSIVE] MODE] table @@ -55,20 +55,6 @@ - - - DELETE 0 - - - - Message returned on a successful lock. - LOCK is implemented as a - DELETE FROM table - which is guaranteed to not delete any rows. - - - - ERROR table: Table does not exist. @@ -92,8 +78,9 @@ Description - LOCK locks in exclusive mode a table inside - a transaction. The classic use for this is + By default, LOCK locks in exclusive mode a table inside + a transaction. Various options allow shared access, or row-level locking + control. The classic use for this is the case where you want to select some data, then update it inside a transaction. If you don't explicit lock a table using LOCK statement, it will be @@ -183,7 +170,7 @@ There is no LOCK TABLE in SQL92, which instead uses SET TRANSACTION to specify - concurrency level on transactions. + concurrency level on transactions. We support that too. -- cgit v1.2.3