Re: Deadlock

From: Holger Jakobs <holger(at)jakobs(dot)com>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Deadlock
Date: 2024-04-02 16:45:21
Message-ID: 58661f82-620c-8116-efe7-23266578289c@jakobs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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
<https://signal.me/#eu/GpIP259bBne_JiBYJFvbZCLYJELhB-92nJfncACL1LUeBOphfXFFgLYYVXv_AGhg>

In response to

  • Deadlock at 2024-04-02 16:40:57 from Rajesh Kumar

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Rajesh Kumar 2024-04-02 17:09:58 Re: Deadlock
Previous Message Rajesh Kumar 2024-04-02 16:40:57 Deadlock