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 1seRA5-00772C-Bu for pgsql-admin@arkaria.postgresql.org; Thu, 15 Aug 2024 03:28:29 +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 1seRA4-00E9L2-0t for pgsql-admin@arkaria.postgresql.org; Thu, 15 Aug 2024 03:28:28 +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 1seRA3-00E9Kt-Li for pgsql-admin@lists.postgresql.org; Thu, 15 Aug 2024 03:28:27 +0000 Received: from mail-lj1-x235.google.com ([2a00:1450:4864:20::235]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1seRA1-004v15-I8 for pgsql-admin@lists.postgresql.org; Thu, 15 Aug 2024 03:28:27 +0000 Received: by mail-lj1-x235.google.com with SMTP id 38308e7fff4ca-2f035ae0fd1so5921621fa.2 for ; Wed, 14 Aug 2024 20:28:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723692504; x=1724297304; 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=+5rXrdRVMIN3DASiUbPt9azUDiYCiwqDGBl/5Iw/axA=; b=mp3JjBnuHyA3XONhlDeBLz73U6PZlCVuGHp4Tgx+obU2/hZEGsbEmIOA2+TDouB4YH dZwXmfAbN5XS6IGQuDBYpsD3LpnRbnAcxkaSV8KSdzQ7OJ6MuDLxrDNJ81KKu9o6w7cn vXSeYFsfuXoXQpQCLVOeiLGNWSRujZ/tdoqtE8SCmoHj25bX/MBGz9ErsIaw72kSM98P ohx4mkVj+DcklaXLBnmofyQqOphNd/YVAT7MqSZDbMoAHV2LTC1Vc4R+8jhPAJAHSXTY OYyqAhOXY7Ww6WLO4j1caf04LWhBjZGK0NAniinKhCqvrF7vmYh73R6RCZ1nGRHMnNMf o2QQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723692504; x=1724297304; 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=+5rXrdRVMIN3DASiUbPt9azUDiYCiwqDGBl/5Iw/axA=; b=ArTeXwxylEOxtBLVPRRLXkeIbC6/UregQA1y+8AwYR3MTX+FGnaCNjNc++UMhPk79X BVVvCxTfuNe3xuYQYcX8CppiARtp0Ds7XiDy0qLXEK6Wmup2wsWZyFRLp5IOYzRLJFek ffjlk3H4QRK8fH1RiHtyccFwNFRKl1k5M73FqxRFeWBsoQpnOnrIBqfWqO4WR/JmA1Ze Z7RiMua/tJGeVGuv+cHvUPsKyHwremfCWwLTDDBGRd0qpRsbf3VqJC6/XpmVWdyj0ynz tS1c6G/37DJl6dnEPnsLsqu+LztLXoqPmfceQxUUEk/pGJo5kE/idFFJo4e7M1FA/5cT kTZA== X-Forwarded-Encrypted: i=1; AJvYcCXGteJhadLR9c4yWCVcIYdQUu0dnRFExCd820lywu4iCp/yZVS5Xj7sgd6lKdLPvufyq1Z+kG4u4mobLQ==@lists.postgresql.org X-Gm-Message-State: AOJu0YzRPCnZF84d8U0UzKrurk5wKHpgTWfh8ClW1kbOV3KibAunEN5Z UP19KuFWGWlRi5Gjft0ehy+l22PLnUH3EP9h4dEhQuWCEZMAdK/t5m3yxUKSc/oAh90yQD+RlBA 1qRumdYJcwA40vzX6FvBEAWYdZeU= X-Google-Smtp-Source: AGHT+IGyxUujLRz0ga9umF+/j7QM1JP+Sqm05ojUB/0tQOkpTRvSxgcrX6LBGwFZ7WXnB4eGzavLgvCV5MrimnbYYXM= X-Received: by 2002:a05:6512:b0a:b0:52c:c9bb:2ba4 with SMTP id 2adb3069b0e04-532edba8e9dmr3205991e87.46.1723692503801; Wed, 14 Aug 2024 20:28:23 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Wasim Devale Date: Thu, 15 Aug 2024 08:58:11 +0530 Message-ID: Subject: Re: Dead lock after the migration from CentOS 7 to RHEL 9 To: "David G. Johnston" Cc: Muhammad Waqas , Pgsql-admin , pgsql-admin Content-Type: multipart/alternative; boundary="000000000000642b82061fb06fd2" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000642b82061fb06fd2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable So it's not a postgresql issue. It's from the application side correct? On Thu, 15 Aug, 2024, 8:56=E2=80=AFam David G. Johnston, wrote: > On Wednesday, August 14, 2024, Wasim Devale wrote: > >> Hi please help me with the below email. >> >> ---------- Forwarded message --------- >> From: Wasim Devale >> Date: Wed, 14 Aug, 2024, 11:09=E2=80=AFam >> Subject: Dead lock after the migration from CentOS 7 to RHEL 9 >> To: Pgsql-admin , pgsql-admin < >> pgsql-admin@postgresql.org> >> >> >> Hi All >> >> I am facing this issue while reindexing after migration. I analysed the >> application holding the particular table. I stopped the application and >> reindexed it. It went well then again I am facing this issue below. >> >> ERROR: deadlock detected >> >> DETAIL: Process 2197043 waits for AccessExclusiveLock on relation >> 10384355 of database 10163711; blocked by process 1889236. >> >> Process 1889236 waits for RowExclusiveLock on relation 10168609 of >> database 10163711; blocked by process 2197043. >> >> HINT: See server log for query details. >> > > How are we supposed to help; you have the indicated log files, and > application code, not us. It=E2=80=99s a bug in your code. And you haven= =E2=80=99t asked > any question that could be answered. > > David J. > > --000000000000642b82061fb06fd2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

So it's not a postgresql issue. It's from the applic= ation side correct?


On Thu= , 15 Aug, 2024, 8:56=E2=80=AFam David G. Johnston, <david.g.johnston@gmail.com> wrote:
On Wednesday, August 14, 2024, Wasim Deval= e <wasimd60@gmail.com> wrote:
<= div dir=3D"auto">
Hi please help me with the below=C2=A0email.

<= div class=3D"gmail_quote">

Hi = All

I am facing this issue while reindexing after migration. I analy= sed the application holding the particular table. I stopped the application= and reindexed it. It went well then again I am facing this issue below.

ERROR: deadlock detected

DETAIL: Process 219704= 3 waits for AccessExclusiveLock on relation 10384355 of database 10163711; = blocked by process 1889236.

Process 1889236 waits for RowExclusiveLoc= k on relation 10168609 of database 10163711; blocked by process 2197043.

HINT: See server log for query details.


How are we supposed to help; you ha= ve the indicated log files, and application code, not us. It=E2=80=99s a bu= g in your code.=C2=A0 And you haven=E2=80=99t asked any question that could= be answered.

David J.

--000000000000642b82061fb06fd2--