# LWLock: LockManager

> Waiting to read or update information about "heavyweight" locks
---

<div class="event-kicker">PostgreSQL wait event dossier</div>
<div class="event-identity">
  <span>Class<strong>LWLock</strong></span>
  <span>Event<strong><code>LockManager</code></strong></span>
  <span>Versions<strong>PG 13-18</strong></span>
  <span>Evidence<strong>3 source location(s)</strong></span>
</div>

## Official description {#official-description}

Waiting to read or update information about "heavyweight" locks

| PG 13 | PG 14 | PG 15 | PG 16 | PG 17 | PG 18 |
| :---: | :---: | :---: | :---: | :---: | :---: |
| ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |

## Trigger mechanism {#mechanism}

Heavyweight lock bookkeeping is stored in shared hash tables partitioned by LockHashPartitionLock. Acquiring, granting, releasing, or inspecting many heavyweight locks can contend on the partition even when no SQL-level lock conflict exists.

## Normal or trouble? {#normal-vs-trouble}

- <span class="severity-normal">**Normal:**</span> Small bursts accompany ordinary relation and transaction lock traffic.
- <span class="severity-watch">**Investigate:**</span> A sustained share often follows lock fan-out: very large transactions, many partitions, DDL churn, or thousands of waiting lock requests.

## Diagnostic SQL {#diagnostic-sql}

```sql {title="Sessions waiting on LWLock/LockManager"}
SELECT pid, backend_type, usename, datname, application_name,
       state, now() - query_start AS query_age,
       now() - xact_start AS xact_age,
       wait_event_type, wait_event,
       pg_blocking_pids(pid) AS blocking_pids,
       left(query, 160) AS query
FROM pg_stat_activity
WHERE wait_event_type = 'LWLock'
  AND wait_event = 'LockManager'
ORDER BY query_age DESC NULLS LAST;
```

```sql {title="Current LWLock cohort"}
SELECT wait_event, count(*) AS waiting_sessions,
       count(*) FILTER (WHERE state = 'active') AS active_waiters,
       max(now() - query_start) AS oldest_query
FROM pg_stat_activity
WHERE wait_event_type = 'LWLock'
GROUP BY wait_event
ORDER BY waiting_sessions DESC, wait_event;
```

```sql {title="Lock and relation context for these sessions"}
SELECT a.pid, l.locktype, l.mode, l.granted, l.fastpath,
       d.datname, n.nspname, c.relname,
       l.page, l.tuple, l.virtualxid, l.transactionid,
       l.classid, l.objid, l.objsubid
FROM pg_stat_activity AS a
LEFT JOIN pg_locks AS l ON l.pid = a.pid
LEFT JOIN pg_database AS d ON d.oid = l.database
LEFT JOIN pg_class AS c
  ON c.oid = l.relation
 AND l.database = (
       SELECT oid FROM pg_database WHERE datname = current_database()
     )
LEFT JOIN pg_namespace AS n ON n.oid = c.relnamespace
WHERE a.wait_event_type = 'LWLock'
  AND a.wait_event = 'LockManager'
ORDER BY a.pid, l.granted, l.locktype, l.mode;
```

## Response {#response}

1. Count pg_locks rows per PID and inspect the blocking tree.
2. Identify statements touching many relations or partitions.
3. Shorten transactions and reduce lock fan-out; raise max_locks_per_transaction only for genuine capacity errors.

## Source evidence {#source}

- [PostgreSQL 18.6 · src/backend/storage/ipc/ipci.c:117](https://github.com/postgres/postgres/blob/REL_18_6/src/backend/storage/ipc/ipci.c#L117) — `LockManager`
- [PostgreSQL 18.6 · src/backend/storage/lmgr/lwlock.c:739](https://github.com/postgres/postgres/blob/REL_18_6/src/backend/storage/lmgr/lwlock.c#L739) — `pgstat_report_wait_start`
- [PostgreSQL 18.6 · src/backend/utils/activity/wait_event_names.txt:378](https://github.com/postgres/postgres/blob/REL_18_6/src/backend/utils/activity/wait_event_names.txt#L378) — `LockManager`

## Related controls and signals {#related}

- **GUCs:** [[guc:max_locks_per_transaction]](/guc/max-locks-per-transaction/) · [[guc:max_connections]](/guc/max-connections/)
- **Metrics:** [[metric:waiting_sessions]](/metric/waiting-sessions/) · [[metric:wait_event_share]](/metric/wait-event-share/) · [[metric:locks_per_backend]](/metric/locks-per-backend/) · [[metric:blocked_sessions]](/metric/blocked-sessions/)

## Typical incident pattern {#incident}

A deployment runs DDL across thousands of partitions while application sessions acquire relation locks, creating internal lock-table contention before a clear blocker is visible.

---

Backlinks:

- [LWLock](/lwlock/)