Re: lwlock:LockManager wait_events
kyle Hailey <kylelf@gmail.com>
From: kyle Hailey <kylelf@gmail.com>
To: SAMEER KUMAR <sameer.kasi200x@gmail.com>
Cc: James Pang <jamespang886@gmail.com>,
pgsql-performance@lists.postgresql.org
Date: 2025-02-08T19:41:18Z
Lists: pgsql-performance
late to the game here but this might be of interest: https://ardentperf.com/2024/03/03/postgres-indexes-partitioning-and-lwlocklockmanager-scalability/ On Fri, Oct 25, 2024 at 5:10 AM SAMEER KUMAR <sameer.kasi200x@gmail.com> wrote: > > > On Fri, 25 Oct 2024, 14:36 James Pang, <jamespang886@gmail.com> wrote: > >> experts, >> we faced into a lot of lwlock:LockManager wait-events , all of these >> queries are "select ..." , there are other several session are doing DML, >> insert/update/delete on same table. Did these DML transactions holding >> "transactionid" and "tuple" lock blocking "select" on lwlock:LockManager ? >> > > > Which version of PostgreSQL? > Are these all same query or variant of same query (with different > parameters)? > > What's the schema (you can redact column names) for the tables involved in > the select query which is blocked/waiting on lock_manager? > > >> Thanks, >> >> James >> >