Commita9a230e

committed

doc: clarify wording about phantom reads

1 parente243de0 commita9a230eCopy full SHA for a9a230e

File tree

-4

lines changed

-4

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -2194,7 +2194,7 @@ HINT: You can then restart the server after making the necessary configuration`
`2194`	`2194`	`Currently, temporary table creation is not allowed during read-only`
`2195`	`2195`	`transactions, so in some cases existing scripts will not run correctly.`
`2196`	`2196`	`This restriction might be relaxed in a later release. This is`
`2197`		`- both an SQLStandard compliance issue and a technical issue.`
	`2197`	`+ both an SQLstandard compliance issue and a technical issue.`
`2198`	`2198`	`</para>`
`2199`	`2199`
`2200`	`2200`	`<para>`

Lines changed: 4 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -277,9 +277,10 @@`
`277`	`277`
`278`	`278`	`<para>`
`279`	`279`	`The table also shows that PostgreSQL's Repeatable Read implementation`
`280`		`- does not allow phantom reads. Stricter behavior is permitted by the`
`281`		`- SQL standard: the four isolation levels only define which phenomena`
`282`		`- must not happen, not which phenomena <emphasis>must</emphasis> happen.`
	`280`	`+ does not allow phantom reads. This is acceptable under the SQL`
	`281`	`+ standard because the standard specifies which anomalies must`
	`282`	`+ <emphasis>not</emphasis> occur at certain isolation levels; higher`
	`283`	`+ guarantees are acceptable.`
`283`	`284`	`The behavior of the available isolation levels is detailed in the`
`284`	`285`	`following subsections.`
`285`	`286`	`</para>`

Comments

(0)