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
This commit is contained in:
parent
e246b3d6ea
commit
a92b5f969b
|
@ -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
|
||||
|
|
Loading…
Reference in New Issue