From 996c52beff9031d7dcb0d1a5ed19e28ad7c9ea6a Mon Sep 17 00:00:00 2001 From: "Thomas G. Lockhart" Date: Fri, 1 Oct 1999 15:26:29 +0000 Subject: [PATCH] Refer to "name", rather than "table" as the replaceable parameter. Seems to read better this way... --- doc/src/sgml/ref/lock.sgml | 21 +++++++++++---------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/doc/src/sgml/ref/lock.sgml b/doc/src/sgml/ref/lock.sgml index 79d558da12..da753b9bb3 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 - Explicit lock of a table inside a transaction + Explicitly lock a table inside a transaction @@ -23,9 +23,9 @@ Postgres documentation 1999-07-20 -LOCK [ TABLE ] table -LOCK [ TABLE ] table IN [ ROW | ACCESS ] { SHARE | EXCLUSIVE } MODE -LOCK [ TABLE ] table IN SHARE ROW EXCLUSIVE MODE +LOCK [ TABLE ] name +LOCK [ TABLE ] name IN [ ROW | ACCESS ] { SHARE | EXCLUSIVE } MODE +LOCK [ TABLE ] name IN SHARE ROW EXCLUSIVE MODE @@ -39,7 +39,7 @@ LOCK [ TABLE ] table IN SHARE ROW E - table + name The name of an existing table to lock. @@ -195,11 +195,11 @@ LOCK TABLE -ERROR table: Table does not exist. +ERROR name: Table does not exist. - Message returned if table + Message returned if name does not exist. @@ -230,8 +230,9 @@ ERROR table: Table does not exist. table before querying. This will protect data from concurrent changes and provide any further read operations over the table with data in their actual current state, because SHARE lock mode conflicts with any ROW EXCLUSIVE - one acquired by writers, and your LOCK TABLE table IN SHARE MODE statement - will wait until any concurrent write operations commit or rollback. + one acquired by writers, and your + LOCK TABLE name IN SHARE MODE + statement will wait until any concurrent write operations commit or rollback.