Commit2fa255c

committed

doc: clarify text around MVCC example query

Reported-by: marlene.brandstaetter@cargonet.softwareDiscussion:https://postgr.es/m/167765529052.987840.12345375075704447735@wrigleys.postgresql.orgBackpatch-through: master

1 parent4a9effe commit2fa255cCopy full SHA for 2fa255c

File tree

-4

lines changed

-4

lines changed

Lines changed: 4 additions & 4 deletions

Original file line number	Diff line number	Diff line change
`@@ -417,8 +417,8 @@`
`417`	`417`	`does not see effects of those commands on other rows in the database.`
`418`	`418`	`This behavior makes Read Committed mode unsuitable for commands that`
`419`	`419`	`involve complex search conditions; however, it is just right for simpler`
`420`		`- cases. For example, considerupdating bank balances with transactions`
`421`		`-like:`
	`420`	`+ cases. For example, considertransferring $100 from one account`
	`421`	`+to another:`
`422`	`422`
`423`	`423`	`<screen>`
`424`	`424`	`BEGIN;`
`@@ -427,8 +427,8 @@ UPDATE accounts SET balance = balance - 100.00 WHERE acctnum = 7534;`
`427`	`427`	`COMMIT;`
`428`	`428`	`</screen>`
`429`	`429`
`430`		`- Iftwo suchtransactions concurrentlytry to change the balance of account`
`431`		`-12345, we clearly want the secondtransaction to start with the updated`
	`430`	`+ Ifanothertransactions concurrentlytries to change the balance of account`
	`431`	`+7534, we clearly want the secondstatement to start with the updated`
`432`	`432`	`version of the account's row. Because each command is affecting only a`
`433`	`433`	`predetermined row, letting it see the updated version of the row does`
`434`	`434`	`not create any troublesome inconsistency.`

Comments

(0)