public inbox for [email protected]
help / color / mirror / Atom feedFrom: SAMEER KUMAR <[email protected]>
To: James Pang <[email protected]>
Cc: [email protected]
Subject: Re: lwlock:LockManager wait_events
Date: Fri, 25 Oct 2024 20:09:45 +0800
Message-ID: <CAGPeHmiuURaY4K=Kj6uktbiKBt-cGPFpH-2Vvb90ZgnB0TAXwA@mail.gmail.com> (raw)
In-Reply-To: <CAHgTRfesRFm1BuG_5guvdSCof2qoHGZvaa1YEkim97EMALaWgQ@mail.gmail.com>
References: <CAHgTRfesRFm1BuG_5guvdSCof2qoHGZvaa1YEkim97EMALaWgQ@mail.gmail.com>
On Fri, 25 Oct 2024, 14:36 James Pang, <[email protected]> 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
>
view thread (5+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: lwlock:LockManager wait_events
In-Reply-To: <CAGPeHmiuURaY4K=Kj6uktbiKBt-cGPFpH-2Vvb90ZgnB0TAXwA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox