Difference between revisions of "PostgreSQL Index Locking"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
| − | 2023-07- | + | 2023-07-10 09:59:58 UTC [519304]: LOG: process 519114 still waiting for AccessShareLock on relation 1054128 of database 16111 after 9499.033 ms |
| − | LOG: skipping [[vacuum]] of "your_test" --- [[lock not available]] | + | 2023-07-10 10:01:39 UTC [520415]: LOG: skipping [[vacuum]] of "your_test" --- [[lock not available]] |
== Related == | == Related == | ||
Latest revision as of 10:32, 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)
2023-07-10 09:59:58 UTC [519304]: LOG: process 519114 still waiting for AccessShareLock on relation 1054128 of database 16111 after 9499.033 ms
2023-07-10 10:01:39 UTC [520415]: LOG: skipping vacuum of "your_test" --- lock not available
Related[edit]
AccessShareLock
See also[edit]
Advertising:
