From a92b5f969bed9796bcb3c321e7be4124a4533067 Mon Sep 17 00:00:00 2001 From: Robert Haas Date: Fri, 19 Sep 2014 13:07:24 -0400 Subject: [PATCH] doc: Use and all-caps for READ COMMITTED isolation level. The documentation overall is not entirely consistent about how we do this, but this is consistent with other usages within lock.sgml. Etsuro Fujita --- doc/src/sgml/ref/lock.sgml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/ref/lock.sgml b/doc/src/sgml/ref/lock.sgml index 26e424b63e..913afe76dd 100644 --- a/doc/src/sgml/ref/lock.sgml +++ b/doc/src/sgml/ref/lock.sgml @@ -51,9 +51,9 @@ LOCK [ TABLE ] [ ONLY ] name [ * ] restrictive lock mode possible. LOCK TABLE provides for cases when you might need more restrictive locking. For example, suppose an application runs a transaction at the - Read Committed isolation level and needs to ensure that data in a - table remains stable for the duration of the transaction. To - achieve this you could obtain SHARE lock mode over the + READ COMMITTED isolation level and needs to ensure that + data in a table remains stable for the duration of the transaction. + To achieve this you could obtain SHARE lock mode over the table before querying. This will prevent concurrent data changes and ensure subsequent reads of the table see a stable view of committed data, because SHARE lock mode conflicts with