Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t4J8l-00HTFK-Q7 for pgsql-performance@arkaria.postgresql.org; Fri, 25 Oct 2024 12:10:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1t4J8j-00GgQT-4W for pgsql-performance@arkaria.postgresql.org; Fri, 25 Oct 2024 12:10:01 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t4J8i-00GgQK-Pq for pgsql-performance@lists.postgresql.org; Fri, 25 Oct 2024 12:10:01 +0000 Received: from mail-lj1-x231.google.com ([2a00:1450:4864:20::231]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t4J8h-002uZS-Mp for pgsql-performance@lists.postgresql.org; Fri, 25 Oct 2024 12:10:00 +0000 Received: by mail-lj1-x231.google.com with SMTP id 38308e7fff4ca-2fb57f97d75so17366051fa.2 for ; Fri, 25 Oct 2024 05:09:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1729858199; x=1730462999; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ZVCkbUOVB1XDNOeBSvLfqi8HKnOQudWXN+cHpgDI+Eg=; b=iumJDIQZBgnh10DIhJOWX1iwNdFuZyvBhwfDEQjz8CKXMP000uC1bEiXiViumBj6It N1WBEAP9PTCLIJV7nse5/9pmj06igqkusw9CJf2xcF1cLpkMwEAkE2siJ2o4dyIbPJXk AaloiwFK5gI8HB6XE5sm1yXf6Y0YPfvdAfE85w+45MsDFjJuACLawno/C2/WlxLMEORB 2ESBiLNsOIabgNVbLzN0etDIFxn3UU6jS1KOB0FbN3OC9SI+ZUWADV7W0MOwRHCnZYpl ys5zrMimqrlpoyJcSNnrm04yqm4NYg9zj2ROR6mcAm+BjNbZ0MsvCeW+6d50CctcmHNm BAjg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729858199; x=1730462999; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ZVCkbUOVB1XDNOeBSvLfqi8HKnOQudWXN+cHpgDI+Eg=; b=JUulF7B9Buy0f6ONWOxNY7vCZ23c9xBvxWC7YeAAnlXbHbR6Q613U+Kz/Hv+GNVr0n PyJbOzVmEeiVT6RZYs4ebq/8WFgJejMmiCcEHEnRMDylcBS1tRxTO8BOpJhy2etUegvE 83TSvtld3vAwxAsfgaO04fCXQ4TglbWHodOFFC9z6eeDnC8GUBh4eHpXhIpxIYTmkMMT ftCv5eqYxgx/hGgg/9cHRq74JmDh9BBdSzcDcU5c4prSoAVTyJMP/urD8j2dWl74cNyj FsoPr782C3JO2rwKh37FYigcZF49BKMunLp8KbGksiP71/ueERLxW9+5XdDiuGqtDqZ+ 3ZKA== X-Gm-Message-State: AOJu0YwZ9QSdLd3bGzg8v+liO+R7/R6wLY+lVfdRdVcn4SOz6jCjqZHF 6OXZcDGfBtz5b5Mqops1lRxCa0z2DyNypyHPnc2q1I9pFA0gQGJMNQnFYpWT+d53z/BsvNXoVvG l3FnpDE52AsHbGUBQEvbEIOJlJQ== X-Google-Smtp-Source: AGHT+IGh3rn2mGMvokJU3ofB6DVm6S+11B/c4MTVsW1vJWCHhjkKpV2ydHcVxWCMgCVCECTLDSklxF5SL9E4AntB+kk= X-Received: by 2002:a05:6512:3b9c:b0:539:f1ad:b7a6 with SMTP id 2adb3069b0e04-53b23e67ceemr3118729e87.37.1729858198388; Fri, 25 Oct 2024 05:09:58 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: SAMEER KUMAR Date: Fri, 25 Oct 2024 20:09:45 +0800 Message-ID: Subject: Re: lwlock:LockManager wait_events To: James Pang Cc: pgsql-performance@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000006d481006254bff89" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000006d481006254bff89 Content-Type: text/plain; charset="UTF-8" On Fri, 25 Oct 2024, 14:36 James Pang, 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 > --0000000000006d481006254bff89 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fri, 25 Oct 2024, 14:36 James Pang, <jamespang886@gmail.com> wrote:
experts,
=C2=A0 =C2= =A0 we faced into a lot of=C2=A0 lwlock:LockManager wait-events , all of th= ese queries=C2=A0are "select ..." ,=C2=A0 there are other several= session are doing DML, insert/update/delete on same table.=C2=A0 =C2=A0Did= these DML transactions holding "transactionid" and "tuple&q= uot; lock blocking=C2=A0"select" on lwlock:LockManager ?=C2=A0=C2= =A0


Which version of PostgreSQL?
Are these all same query or variant of same query (with dif= ferent parameters)?=C2=A0

What's the schema (you can redact column names) for the tables involv= ed in the select query which is blocked/waiting on lock_manager?=C2=A0

<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">

Thanks,<= /div>

James
--0000000000006d481006254bff89--