Postgres Pro
Downloads
Home   >   mailing lists

Re: Dead lock after the migration from CentOS 7 to RHEL 9 - Mailing list pgsql-admin

From Wasim Devale
Subject Re: Dead lock after the migration from CentOS 7 to RHEL 9
Date
Msg-id CAB5fag7hsyWJUv=KezM=10RZ8hs=3fDkR4vMmJvn-Fjv3O0oeA@mail.gmail.com
Whole thread Raw
In response to Re: Dead lock after the migration from CentOS 7 to RHEL 9  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: Dead lock after the migration from CentOS 7 to RHEL 9
List pgsql-admin
Tree view

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@gmail.com> wrote:
On Wednesday, August 14, 2024, Wasim Devale <wasimd60@gmail.com> wrote:
Hi please help me with the below email.

---------- Forwarded message ---------
From: Wasim Devale <wasimd60@gmail.com>
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@lists.postgresql.org>, pgsql-admin <pgsql-admin@postgresql.org>


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.

pgsql-admin by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Dead lock after the migration from CentOS 7 to RHEL 9
Next
From: "David G. Johnston"
Date:
Subject: Re: Dead lock after the migration from CentOS 7 to RHEL 9