| From: | Wasim Devale <wasimd60(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(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:38:31 |
| Message-ID: | CAB5fag47NNn4T1e-t7YkLkqQbdammAvgDeb423ThaY=VjkSTOQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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 am David G. Johnston, <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Wednesday, August 14, 2024, Wasim Devale <wasimd60(at)gmail(dot)com> wrote:
>
>> So it's not a postgresql issue. It's from the application side correct?
>>
>
> That’s the assumption. The vast majority of locks happen because the
> “application” executed SQL commands.
>
> David J.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Ribe | 2024-08-15 03:45:29 | Re: Dead lock after the migration from CentOS 7 to RHEL 9 |
| Previous Message | David G. Johnston | 2024-08-15 03:31:16 | Re: Dead lock after the migration from CentOS 7 to RHEL 9 |