From: Matthias Apitz <guru@unixarea.de>
To: pgsql-general@postgresql.org
Subject: ERROR: deadlock detected
Date: Tue, 7 Feb 2023 12:46:47 +0100
Message-ID: <20230207114647.GA9@sh4-5.1blu.de> (raw)
We saw the following message in the file postgres-serverlog.error:
2023-01-24 17:16:16.578 CET [17468] ERROR: deadlock detected
2023-01-24 17:16:16.578 CET [17468] DETAIL: Process 17468 waits for ShareLock on transaction 90776649; blocked by process 17724.
Process 17724 waits for ShareLock on transaction 90776650; blocked by process 17468.
Process 17468: fetch hc_d03geb
Process 17724: fetch hc_d02ben
2023-01-24 17:16:16.578 CET [17468] HINT: See server log for query details.
2023-01-24 17:16:16.578 CET [17468] CONTEXT: while locking tuple (948,45) in relation "d03geb"
2023-01-24 17:16:16.578 CET [17468] STATEMENT: fetch hc_d03geb
There are no messages in the serverlog itself and in our application
log files. What can we do to get to more information (may be next time)?
The process numbers are internal ones of the PostgreSQL server and not
the Linux PID, correct?
Thanks
matthias
--
Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: guru@unixarea.de
Subject: Re: ERROR: deadlock detected
In-Reply-To: <20230207114647.GA9@sh4-5.1blu.de>
References: <20230207114647.GA9@sh4-5.1blu.de>
* 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