From: | kyle Hailey <kylelf(at)gmail(dot)com> |
---|---|
To: | SAMEER KUMAR <sameer(dot)kasi200x(at)gmail(dot)com> |
Cc: | James Pang <jamespang886(at)gmail(dot)com>, pgsql-performance(at)lists(dot)postgresql(dot)org |
Subject: | Re: lwlock:LockManager wait_events |
Date: | 2025-02-08 19:41:18 |
Message-ID: | CADsdiQjTrkn8RNSu-exzRynyEt9N_1yAjw9L8nXSGDVS5QRuRA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
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(dot)kasi200x(at)gmail(dot)com>
wrote:
>
>
> 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 | 2025-02-09 20:56:54 | Re: Re: proposal: schema variables |
Previous Message | Jon Emord | 2025-02-07 16:16:27 | Re: Poor performance with row wise comparisons |