Difference between revisions of "PostgreSQL Index Locking"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
[[Index (PostgreSQL)|Index]] [[locking]] | [[Index (PostgreSQL)|Index]] [[locking]] | ||
* https://www.postgresql.org/docs/current/index-locking.html | * https://www.postgresql.org/docs/current/index-locking.html | ||
| + | |||
| + | Index access methods must handle concurrent updates of the index by multiple processes. The core PostgreSQL system obtains [[AccessShareLock]] on the index during an [[index scan]], and [[RowExclusiveLock]] when updating the index (including plain [[VACUUM]]) | ||
| + | |||
== Related == | == Related == | ||
Revision as of 10:30, 11 July 2023
Index access methods must handle concurrent updates of the index by multiple processes. The core PostgreSQL system obtains AccessShareLock on the index during an index scan, and RowExclusiveLock when updating the index (including plain VACUUM)
Related
AccessShareLock
See also
Advertising:
