| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Wasim Devale <wasimd60(at)gmail(dot)com> |
| Cc: | Muhammad Waqas <waqas(dot)m(at)bitnine(dot)net>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Dead lock after the migration from CentOS 7 to RHEL 9 |
| Date: | 2024-08-15 03:50:44 |
| Message-ID: | CAKFQuwYB3Af7e62rAFQQMi0G_he81ypqf5WtHvg9vHc-8276-Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wednesday, August 14, 2024, Wasim Devale <wasimd60(at)gmail(dot)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 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’m not of much help. I’m not inclined to
teach what a deadlock is - such knowledge is available on the internet.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wasim Devale | 2024-08-15 03:54:01 | Re: Dead lock after the migration from CentOS 7 to RHEL 9 |
| Previous Message | Scott Ribe | 2024-08-15 03:45:29 | Re: Dead lock after the migration from CentOS 7 to RHEL 9 |