From: Holger Jakobs <holger@jakobs.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Deadlock
Date: Tue, 2 Apr 2024 18:45:21 +0200
Message-ID: <58661f82-620c-8116-efe7-23266578289c@jakobs.com> (raw)
In-Reply-To: <CAJk5Atb6CnsgAJUQ--UPgvRH-eZUhhL__P9-pz=XZsq=r29ShA@mail.gmail.com>
References: <CAJk5Atb6CnsgAJUQ--UPgvRH-eZUhhL__P9-pz=XZsq=r29ShA@mail.gmail.com>
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;
Attachments:
[image/png] TapMuhNyQVuzuVPA.png (551B, ../58661f82-620c-8116-efe7-23266578289c@jakobs.com/3-TapMuhNyQVuzuVPA.png)
download | view image
[application/pgp-signature] OpenPGP_signature (202B, ../58661f82-620c-8116-efe7-23266578289c@jakobs.com/4-OpenPGP_signature)
download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: holger@jakobs.com, pgsql-admin@lists.postgresql.org
Subject: Re: Deadlock
In-Reply-To: <58661f82-620c-8116-efe7-23266578289c@jakobs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox