Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pPMRA-0008LZ-6P for pgsql-general@arkaria.postgresql.org; Tue, 07 Feb 2023 11:47:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pPMR9-00058a-2r for pgsql-general@arkaria.postgresql.org; Tue, 07 Feb 2023 11:46:59 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pPMR8-00055w-Oh for pgsql-general@lists.postgresql.org; Tue, 07 Feb 2023 11:46:58 +0000 Received: from ms-10.1blu.de ([178.254.4.101]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pPMR6-0000Fq-DW for pgsql-general@postgresql.org; Tue, 07 Feb 2023 11:46:58 +0000 Received: from [178.254.11.41] (helo=sh4-5.1blu.de) by ms-10.1blu.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pPMR5-0004E1-6Y for pgsql-general@postgresql.org; Tue, 07 Feb 2023 12:46:55 +0100 Date: Tue, 7 Feb 2023 12:46:47 +0100 From: Matthias Apitz To: pgsql-general@postgresql.org Subject: ERROR: deadlock detected Message-ID: <20230207114647.GA9@sh4-5.1blu.de> Reply-To: Matthias Apitz MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Operating-System: FreeBSD 12.0-CURRENT r314251 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. User-Agent: Mutt/1.9.4 (2018-02-28) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 178.254.11.41 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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