database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-27 12:41:57 +03:00
Code Activity

doc: Use <literal> and all-caps for READ COMMITTED isolation level.

Browse Source 
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:
Robert Haas
2014-09-19 13:07:24 -04:00
parent e246b3d6ea
commit a92b5f969b
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/src/sgml/ref/lock.sgml
View File

@ -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