Commit5042d16

committed

Remove old claim that ExclusiveLock is sometimes taken on system catalogs.

We used to do that on pg_listener, but pg_listener is no more.Also add a bit more documentation for ShareRowExclusive mode.

1 parent558d1c9 commit5042d16Copy full SHA for 5042d16

File tree

-3

lines changed

-3

lines changed

Lines changed: 4 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -692,6 +692,8 @@ SELECT SUM(value) FROM mytab WHERE class = 2;`
`692`	`692`	`<literal>SHARE</literal>, <literal>SHARE ROW`
`693`	`693`	`EXCLUSIVE</literal>, <literal>EXCLUSIVE</literal>, and`
`694`	`694`	`<literal>ACCESS EXCLUSIVE</literal> lock modes.`
	`695`	`+ This mode protects a table against concurrent data changes, and`
	`696`	`+ is self-exclusive so that only one session can hold it at a time.`
`695`	`697`	`</para>`
`696`	`698`
`697`	`699`	`<para>`
`@@ -719,9 +721,8 @@ SELECT SUM(value) FROM mytab WHERE class = 2;`
`719`	`721`	`</para>`
`720`	`722`
`721`	`723`	`<para>`
`722`		`- This lock mode is not automatically acquired on user tables by any`
`723`		`- <productname>PostgreSQL</productname> command. However it is`
`724`		`- acquired on certain system catalogs in some operations.`
	`724`	`+ This lock mode is not automatically acquired on tables by any`
	`725`	`+ <productname>PostgreSQL</productname> command.`
`725`	`726`	`</para>`
`726`	`727`	`</listitem>`
`727`	`728`	`</varlistentry>`

Comments

(0)