MIME-Version: 1.0
References: 
 <CAB5fag444HCM8xONrKbg+rJ5odCdy=0vmianN2Si5K5mWRFKvQ@mail.gmail.com>
 <CAB5fag6QPm1OE7H6roywzovDxb9rT9Wx-MdeiuK=mDvx6NTwtw@mail.gmail.com>
 <CAKFQuwbHt_56dOP-Fjtaj2C9KVJN14-L9LrDUf5AeWyW21g7KQ@mail.gmail.com>
 <CAB5fag7hsyWJUv=KezM=10RZ8hs=3fDkR4vMmJvn-Fjv3O0oeA@mail.gmail.com>
 <CAKFQuwYyFBgKKtJwFAOOsd2NahG6g8ymFKy_KpqhcoHdb_Nd3g@mail.gmail.com>
In-Reply-To: 
 <CAKFQuwYyFBgKKtJwFAOOsd2NahG6g8ymFKy_KpqhcoHdb_Nd3g@mail.gmail.com>
From: Wasim Devale <wasimd60@gmail.com>
Date: Thu, 15 Aug 2024 09:08:31 +0530
Message-ID: 
 <CAB5fag47NNn4T1e-t7YkLkqQbdammAvgDeb423ThaY=VjkSTOQ@mail.gmail.com>
Subject: Re: Dead lock after the migration from CentOS 7 to RHEL 9
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Muhammad Waqas <waqas.m@bitnine.net>,
 Pgsql-admin <pgsql-admin@lists.postgresql.org>,
	pgsql-admin <pgsql-admin@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000561088061fb09440"
Archived-At: 
 <https://www.postgresql.org/message-id/CAB5fag47NNn4T1e-t7YkLkqQbdammAvgDeb423ThaY%3DVjkSTOQ%40mail.gmail.com>
Precedence: bulk

--000000000000561088061fb09440
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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.

Thanks for the immediate help.

Regards,
Wasim

On Thu, 15 Aug, 2024, 9:01=E2=80=AFam David G. Johnston, <david.g.johnston@=
gmail.com>
wrote:

> On Wednesday, August 14, 2024, Wasim Devale <wasimd60@gmail.com> wrote:
>
>> So it's not a postgresql issue. It's from the application side correct?
>>
>
> That=E2=80=99s the assumption.  The vast majority of locks happen because=
 the
> =E2=80=9Capplication=E2=80=9D executed SQL commands.
>
> David J.
>

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

<p dir=3D"ltr">Ok thanks for the insights.</p>
<p dir=3D"ltr">Do we need to do any config changes in the config file?</p>
<p dir=3D"ltr">We have also configured Datadog agent at operating system le=
vel that checks postgresql activity it&#39;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. </p>
<p dir=3D"ltr">Please through some insights on the above.</p>
<p dir=3D"ltr">Thanks for the immediate help.</p>
<p dir=3D"ltr">Regards,<br>
Wasim </p>
<br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu=
, 15 Aug, 2024, 9:01=E2=80=AFam David G. Johnston, &lt;<a href=3D"mailto:da=
vid.g.johnston@gmail.com">david.g.johnston@gmail.com</a>&gt; wrote:<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">On Wednesday, August 14, 2024, Wasim Deval=
e &lt;<a href=3D"mailto:wasimd60@gmail.com" target=3D"_blank" rel=3D"norefe=
rrer">wasimd60@gmail.com</a>&gt; wrote:<br><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><=
p dir=3D"ltr">So it&#39;s not a postgresql issue. It&#39;s from the applica=
tion side correct?</p></blockquote><div><br></div><div>That=E2=80=99s the a=
ssumption.=C2=A0 The vast majority of locks happen because the =E2=80=9Capp=
lication=E2=80=9D executed SQL commands.</div><div><br></div><div>David J.<=
/div>
</blockquote></div>

--000000000000561088061fb09440--