Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sFWAA-0031yI-EW for pgsql-bugs@arkaria.postgresql.org; Fri, 07 Jun 2024 09:45:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sFWA7-00AiMv-QH for pgsql-bugs@arkaria.postgresql.org; Fri, 07 Jun 2024 09:45:32 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sFWA7-00AiMm-Cq for pgsql-bugs@lists.postgresql.org; Fri, 07 Jun 2024 09:45:32 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sFWA4-0008gO-Dc for pgsql-bugs@lists.postgresql.org; Fri, 07 Jun 2024 09:45:30 +0000 Received: from [172.30.2.66] (unknown [172.30.2.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: d.koval@postgrespro.ru) by mail.postgrespro.ru (Postfix/587) with ESMTPSA id 8A6DBE20E33; Fri, 7 Jun 2024 12:45:25 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1717753525; bh=gnbuwQpj0QfyTNk2zoj26005k3grBKBQfeHa0K7XAcM=; h=Message-ID:Date:User-Agent:Subject:To:References:From:In-Reply-To: From; b=eNDyc7tGgMJMFRIJTVaG3S+1sbLE0KZufjgrjz6jmVNXgUdUNS8Ki44H463QK4R11 bNGf39jNpNSb4CbqxhJU4zbj4aWnwv0CMBuk3sspgmlkIauzcw5WuQ56rw3E/HHROn tKD0MMRQ4Ra1bCNwYrRs1XvBazce4WRofztAzie/NPCjpzsUkoesi6u3AFZJKA+/Fp loNK3fsCxeie7sdHop2nDgcuJLrTy/bF4R+2l1pPyLodlqicqgc/loLcS5oMEMguZ1 a9iQfHwm7s7GgFnUDGPjsvMq45TCUq82enk6VXL3juj3PSOCBJp5RldFWW3lvUtaxV I/Kwtaoc1ntKg== Message-ID: <2e10e3ff-2f59-429d-9db3-1611daa7a6b5@postgrespro.ru> Date: Fri, 7 Jun 2024 12:45:26 +0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: BUG #18498: Locking a table from a trigger (with using two sessions) causes a deadlock: the bug or the feature? To: David Rowley , pgsql-bugs@lists.postgresql.org References: <18498-b95f3ee4c156de45@postgresql.org> Content-Language: en-US From: Dmitry Koval In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-KSMG-AntiPhishing: NotDetected, bases: 2024/06/07 08:12:00 X-KSMG-AntiSpam-Interceptor-Info: not scanned X-KSMG-AntiSpam-Status: not scanned, disabled by settings X-KSMG-AntiVirus: Kaspersky Secure Mail Gateway, version 2.1.0.7854, bases: 2024/06/07 04:07:00 #25486014 X-KSMG-AntiVirus-Status: NotDetected, skipped X-KSMG-LinksScanning: not scanned, disabled by settings X-KSMG-Message-Action: skipped X-KSMG-Rule-ID: 1 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk David, thanks for the detailed explanation! I missed the fact that there were two different locks. Issue resolved. -- With best regards, Dmitry Koval Postgres Professional: http://postgrespro.com