Commit046fd4f

committed

doc: clarify when row-level locks are released

They are released just like table-level locks. Also clean up wording.(Uses wording "rolled back to".)Reported-by: me@sillymon.chDiscussion:https://postgr.es/m/158074944048.1095.4309647363871637715@wrigleys.postgresql.orgBackpatch-through: 9.5

1 parent7dbe290 commit046fd4fCopy full SHA for 046fd4f

File tree

-2

lines changed

-2

lines changed

Lines changed: 5 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -1039,7 +1039,7 @@ ERROR: could not serialize access due to read/write dependencies among transact`
`1039`	`1039`	`</tip>`
`1040`	`1040`
`1041`	`1041`	`<para>`
`1042`		`- Once acquired, a lock is normally heldtillend of transaction. But if a`
	`1042`	`+ Once acquired, a lock is normally helduntil theend of the transaction. But if a`
`1043`	`1043`	`lock is acquired after establishing a savepoint, the lock is released`
`1044`	`1044`	`immediately if the savepoint is rolled back to. This is consistent with`
`1045`	`1045`	`the principle that <command>ROLLBACK</command> cancels all effects of the`
`@@ -1178,7 +1178,10 @@ ERROR: could not serialize access due to read/write dependencies among transact`
`1178`	`1178`	`conflicting locks on the same row, even in different subtransactions;`
`1179`	`1179`	`but other than that, two transactions can never hold conflicting locks`
`1180`	`1180`	`on the same row. Row-level locks do not affect data querying; they`
`1181`		`- block only <emphasis>writers and lockers</emphasis> to the same row.`
	`1181`	`+ block only <emphasis>writers and lockers</emphasis> to the same`
	`1182`	`+ row. Row-level locks are released at transaction end or during`
	`1183`	`+ savepoint rollback, just like table-level locks.`
	`1184`	`+`
`1182`	`1185`	`</para>`
`1183`	`1186`
`1184`	`1187`	`<variablelist>`

Comments

(0)