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 1seRVi-007B5y-Hd for pgsql-admin@arkaria.postgresql.org; Thu, 15 Aug 2024 03:50:50 +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 1seRVg-00ENcG-Da for pgsql-admin@arkaria.postgresql.org; Thu, 15 Aug 2024 03:50:48 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1seRVf-00ENc7-Tu for pgsql-admin@lists.postgresql.org; Thu, 15 Aug 2024 03:50:47 +0000 Received: from mail-oa1-x2a.google.com ([2001:4860:4864:20::2a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1seRVd-004noA-EE for pgsql-admin@postgresql.org; Thu, 15 Aug 2024 03:50:46 +0000 Received: by mail-oa1-x2a.google.com with SMTP id 586e51a60fabf-2689f74963bso443644fac.0 for ; Wed, 14 Aug 2024 20:50:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723693845; x=1724298645; darn=postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=dQtrhbTrUxvuz+n9a1zih4vCTzbh1qixUsYmcPfHRf4=; b=h7oBOUNXsK7TC1rCgac/+uOJkJI64BpuGRzGBps70rjGNGcCqNoShHHmCx5pZQ2T7x u0uAxJN5c5DQkYHVe14wi91WpLIKmuGN9aZj8+lyd0tC0YG3qGIggl/Op7Jin7SgsnHM PcvTCrku/RdQZGUl1obMZuOinJy2RzR0/gTzlrNwNO177apDE5nN/gUiflEJVvmzmJeC RFG7ncuXc0c+D+26/ESVicPMudjwSbHQsmTytYVpyWcrK4IaERb8ppclxhqRKpO+vjXh XS9TI33SE3qnWJr/s6FA9opYlZxXkVm6VIh4D2Gi1xdxYtwXrG/6cLigUYW7kEb7P+sT kQ7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723693845; x=1724298645; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=dQtrhbTrUxvuz+n9a1zih4vCTzbh1qixUsYmcPfHRf4=; b=GZ6mWEYPCg7Fu+n10ASb/HRk/GdcPuyisVmNcyAPBV0IJepc23NU7CJYYLzaTERTBC 43uOlWPWRAflwJCjEf6+mTWHLTihgIgf8ClCjL89o/tvL8bnUIE4xhZuC+5K1jbdFvU2 5UwYFeOTuQuiO+8Twd5TrSSihLNXAd6HUng6vsLm1Ugs+qBEncXb5Juj/PQR0zpnpFEU D3mbZukE33qdR11U/nck8syu7ejhMvnURxTaj5WGDeDjYEzFbN9ZIAwhqU6JdCWtufuv ULBLp5soVSyUD8XIjzwt5QdTtIlq44ZmohR5n3WmRyvlvDOGogJVNrlJ/1SPsCxvVrsW lrNg== X-Forwarded-Encrypted: i=1; AJvYcCVCQcseYzFvuXT58TtZH9FPpNAYrwud5iLjh6xO1jYADMBmIkUppriqqDLOgjoSF8z6dcWH69BZBVcII8yoQwgFKrukpcdkeSpASg== X-Gm-Message-State: AOJu0YxWdaOzGEoFQCHDDGOsR4jn+TsQhuMaywuFVzyrjNJg+s9qKiO4 QdGu7fnHLqUBn5r/sBSDB/DGfbQkJXY527lWawYVU52Dnncj+Em0gzSfBDb1jlSOxoRp1O9rQqd SwLS6Fh/HGHptkbtCEZyzmfcvrQL1fSYI X-Google-Smtp-Source: AGHT+IF0ZSFW4wWnfoOQ83XJHCOhF0FZLBqqdv26LNap+P/hsOsKd9HV/QFTAOFksIFr5Du4gkOiNIOjU+eBIA156Cs= X-Received: by 2002:a05:6870:5389:b0:260:eb3a:1b2 with SMTP id 586e51a60fabf-26fe59d80d6mr5769221fac.7.1723693844833; Wed, 14 Aug 2024 20:50:44 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a8a:d02:0:b0:557:c384:fb61 with HTTP; Wed, 14 Aug 2024 20:50:44 -0700 (PDT) In-Reply-To: References: From: "David G. Johnston" Date: Wed, 14 Aug 2024 20:50:44 -0700 Message-ID: Subject: Re: Dead lock after the migration from CentOS 7 to RHEL 9 To: Wasim Devale Cc: Muhammad Waqas , Pgsql-admin , pgsql-admin Content-Type: multipart/alternative; boundary="00000000000052afa5061fb0bfd9" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000052afa5061fb0bfd9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wednesday, August 14, 2024, Wasim Devale wrote: > Ok thanks for the insights. > > Do we need to do any config changes in the config file? > > We have also configured Datadog agent at operating system level that > checks postgresql activity it's has the pgpouncer.d config file that is > unchanged after the migration. This might be the possible reason that it = is > throughing dead lock error. > > Please through some insights on the above. > Sounds like you need to read up on what a deadlock is, and then go figure out what combination of SQL commands in your environment is causing it. Only then does it make sense to reason through possible solutions. Until you can show some SQL commands I=E2=80=99m not of much help. I=E2=80=99m n= ot inclined to teach what a deadlock is - such knowledge is available on the internet. David J. --00000000000052afa5061fb0bfd9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wednesday, August 14, 2024, Wasim Devale <wasimd60@gmail.com> wrote:

Ok thanks for the insights.

Do we need to do any config changes in the config file?

We have also configured Datadog agent at operating system le= vel that checks postgresql activity it's has the pgpouncer.d config fil= e that is unchanged after the migration. This might be the possible reason = that it is throughing dead lock error.

Please through some insights on the above.

<= div>
Sounds like you need to read up on what a deadlock is, a= nd then go figure out what combination of SQL commands in your environment = is causing it. Only then does it make sense to reason through possible solu= tions.=C2=A0 Until you can show some SQL commands I=E2=80=99m not of much h= elp.=C2=A0 I=E2=80=99m not inclined to teach what a deadlock is - such know= ledge is available on the internet.

David J.
=

--00000000000052afa5061fb0bfd9--