Re: Deadlock - Mailing list pgsql-admin

From Holger Jakobs
Subject Re: Deadlock
Date
Msg-id 58661f82-620c-8116-efe7-23266578289c@jakobs.com
Whole thread Raw
In response to [MASSMAIL]Deadlock  (Rajesh Kumar <rajeshkumar.dba09@gmail.com>)
Responses Re: Deadlock
List pgsql-admin
Am 02.04.24 um 18:40 schrieb Rajesh Kumar:
Hi

If I receive an alert for deadlock, what should I do? Like what analysis should I do? No way to find a root cause?
Under pg_locks, what I can analyse? 

If you receive an error with a deadlock, the current transaction is dead. You have to decide whether to try again.

Within the error message you find a hint which other (not aborted) transaction was involved in the deadlock. So you have all the information you need to find the culprit.

Regards,

Holger

--

Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012

chat with me on Signal messenger

Attachment

pgsql-admin by date:

Previous
From: Rajesh Kumar
Date:
Subject: [MASSMAIL]Deadlock
Next
From: Rajesh Kumar
Date:
Subject: Re: Deadlock