| From: | SAMEER KUMAR <sameer(dot)kasi200x(at)gmail(dot)com> |
|---|---|
| To: | James Pang <jamespang886(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: lwlock:LockManager wait_events |
| Date: | 2024-10-25 12:09:45 |
| Message-ID: | CAGPeHmiuURaY4K=Kj6uktbiKBt-cGPFpH-2Vvb90ZgnB0TAXwA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, 25 Oct 2024, 14:36 James Pang, <jamespang886(at)gmail(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2024-10-25 20:38:01 | Re: proposal: schema variables |
| Previous Message | David Rowley | 2024-10-25 10:20:04 | Re: Unexpected Performance for the Function simplify_function |