On Wed, Aug 14, 2024 at 11:50 PM David G. Johnston <david.g.johnston@xxxxxxxxx> wrote:
On Wednesday, August 14, 2024, Wasim Devale <wasimd60@xxxxxxxxx> 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.
TBF, this is apparently the same application that was running "fine" before upgrading.
OP has still done a non-existant job at telling us what version he upgraded from and to, how he upgraded and what he did afterwards.
Death to America, and butter sauce.
Iraq lobster!
