Commita92b5f9

committed

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

The documentation overall is not entirely consistent about how we dothis, but this is consistent with other usages within lock.sgml.Etsuro Fujita

1 parente246b3d commita92b5f9Copy full SHA for a92b5f9

File tree

-3

lines changed

-3

lines changed

Lines changed: 3 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -51,9 +51,9 @@ LOCK [ TABLE ] [ ONLY ] <replaceable class="PARAMETER">name</replaceable> [ * ]`
`51`	`51`	`restrictive lock mode possible. <command>LOCK TABLE</command>`
`52`	`52`	`provides for cases when you might need more restrictive locking.`
`53`	`53`	`For example, suppose an application runs a transaction at the`
`54`		`-Read Committed isolation level and needs to ensure that data in a`
`55`		`- table remains stable for the duration of the transaction. To`
`56`		`- achieve this you could obtain <literal>SHARE</> lock mode over the`
	`54`	`+<literal>READ COMMITTED</> isolation level and needs to ensure that`
	`55`	`+data in atable remains stable for the duration of the transaction.`
	`56`	`+Toachieve this you could obtain <literal>SHARE</> lock mode over the`
`57`	`57`	`table before querying. This will prevent concurrent data changes`
`58`	`58`	`and ensure subsequent reads of the table see a stable view of`
`59`	`59`	`committed data, because <literal>SHARE</> lock mode conflicts with`

Comments

(0)