MIME-Version: 1.0
From: James Pang <jamespang886@gmail.com>
Date: Fri, 25 Oct 2024 14:36:26 +0800
Message-ID: 
 <CAHgTRfesRFm1BuG_5guvdSCof2qoHGZvaa1YEkim97EMALaWgQ@mail.gmail.com>
Subject: lwlock:LockManager wait_events
To: pgsql-performance@lists.postgresql.org
Content-Type: multipart/alternative; boundary="00000000000043872f06254757b0"
Archived-At: 
 <https://www.postgresql.org/message-id/CAHgTRfesRFm1BuG_5guvdSCof2qoHGZvaa1YEkim97EMALaWgQ%40mail.gmail.com>
Precedence: bulk

--00000000000043872f06254757b0
Content-Type: text/plain; charset="UTF-8"

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 ?

Thanks,

James

--00000000000043872f06254757b0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">experts,<div>=C2=A0 =C2=A0 we faced into a lot of=C2=A0 lw=
lock:LockManager wait-events , all of these queries=C2=A0are &quot;select .=
..&quot; ,=C2=A0 there are other several session are doing DML, insert/upda=
te/delete on same table.=C2=A0 =C2=A0Did these DML transactions holding &qu=
ot;transactionid&quot; and &quot;tuple&quot; lock blocking=C2=A0&quot;selec=
t&quot; on lwlock:LockManager ?=C2=A0=C2=A0</div><div><br></div><div>Thanks=
,</div><div><br></div><div>James</div></div>

--00000000000043872f06254757b0--