diff options
| author | Robert Haas <rhaas@postgresql.org> | 2014-09-19 13:07:24 -0400 |
|---|---|---|
| committer | Robert Haas <rhaas@postgresql.org> | 2014-09-19 13:12:52 -0400 |
| commit | a92b5f969bed9796bcb3c321e7be4124a4533067 (patch) | |
| tree | 6987486144865bd6a4a64f503e7d29a43e14f743 | |
| parent | e246b3d6eac09d0770e6f68e69f2368d02db88af (diff) | |
| download | postgresql-a92b5f969bed9796bcb3c321e7be4124a4533067.tar.gz postgresql-a92b5f969bed9796bcb3c321e7be4124a4533067.zip | |
doc: Use <literal> 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
| -rw-r--r-- | doc/src/sgml/ref/lock.sgml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/src/sgml/ref/lock.sgml b/doc/src/sgml/ref/lock.sgml index 26e424b63e8..913afe76dd4 100644 --- a/doc/src/sgml/ref/lock.sgml +++ b/doc/src/sgml/ref/lock.sgml @@ -51,9 +51,9 @@ LOCK [ TABLE ] [ ONLY ] <replaceable class="PARAMETER">name</replaceable> [ * ] restrictive lock mode possible. <command>LOCK TABLE</command> 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 <literal>SHARE</> lock mode over the + <literal>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 <literal>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 <literal>SHARE</> lock mode conflicts with |