Commitc08b3e9

committed

doc: clarify wording about phantom reads

1 parent293f5c5 commitc08b3e9Copy full SHA for c08b3e9

File tree

-4

lines changed

-4

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -2334,7 +2334,7 @@ LOG: database system is ready to accept read only connections`
`2334`	`2334`	`Currently, temporary table creation is not allowed during read only`
`2335`	`2335`	`transactions, so in some cases existing scripts will not run correctly.`
`2336`	`2336`	`This restriction might be relaxed in a later release. This is`
`2337`		`- both a SQLStandard compliance issue and a technical issue.`
	`2337`	`+ both a SQLstandard compliance issue and a technical issue.`
`2338`	`2338`	`</para>`
`2339`	`2339`
`2340`	`2340`	`<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)