From: | Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com> |
---|---|
To: | Holger Jakobs <holger(at)jakobs(dot)com> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Deadlock |
Date: | 2024-04-02 17:09:58 |
Message-ID: | CAJk5AtbDMDD5HKP796qoNPzKqE4qWgnr-ySE7ErED6ph6ebdtw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Yes, I am trying to find out what message i should reply if I receive email
with deadlock notification.
I understand how deadlock occurs, hot to find them in logs, prevention of
deadlock(ex: oqueries in order) etc.
But since the deadlock_timeout is 1s, they don't probably hang around. So
post getting an alert, not sure what to respond to them
On Tue, 2 Apr 2024, 22:15 Holger Jakobs, <holger(at)jakobs(dot)com> wrote:
> 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>
>
Attachment | Content-Type | Size |
---|---|---|
![]() |
image/png | 551 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Holger Jakobs | 2024-04-02 17:42:11 | Re: Deadlock |
Previous Message | Holger Jakobs | 2024-04-02 16:45:21 | Re: Deadlock |