So it's not a postgresql issue. It's from the application side correct?
On Thu, 15 Aug, 2024, 8:56 am David G. Johnston, <david.g.johnston@xxxxxxxxx> wrote:
On Wednesday, August 14, 2024, Wasim Devale <wasimd60@xxxxxxxxx> wrote:Hi please help me with the below email.---------- Forwarded message ---------
From: Wasim Devale <wasimd60@xxxxxxxxx>
Date: Wed, 14 Aug, 2024, 11:09 am
Subject: Dead lock after the migration from CentOS 7 to RHEL 9
To: Pgsql-admin <pgsql-admin@xxxxxxxxxxxxxxxxxxxx>, pgsql-admin <pgsql-admin@xxxxxxxxxxxxxx>Hi All
I am facing this issue while reindexing after migration. I analysed the application holding the particular table. I stopped the application and reindexed it. It went well then again I am facing this issue below.ERROR: deadlock detected
DETAIL: Process 2197043 waits for AccessExclusiveLock on relation 10384355 of database 10163711; blocked by process 1889236.
Process 1889236 waits for RowExclusiveLock on relation 10168609 of database 10163711; blocked by process 2197043.
HINT: See server log for query details.
How are we supposed to help; you have the indicated log files, and application code, not us. It’s a bug in your code. And you haven’t asked any question that could be answered.David J.
