Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gK7MP-0003MG-A5 for pgsql-general@arkaria.postgresql.org; Tue, 06 Nov 2018 19:50:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gK7MN-0007EA-PN for pgsql-general@arkaria.postgresql.org; Tue, 06 Nov 2018 19:49:59 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gK7MN-0007DH-Ds for pgsql-general@lists.postgresql.org; Tue, 06 Nov 2018 19:49:59 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gK7MK-0001yi-Nm for pgsql-general@lists.postgresql.org; Tue, 06 Nov 2018 19:49:58 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id wA6JniAL031912; Tue, 6 Nov 2018 14:49:44 -0500 From: Tom Lane To: =?UTF-8?Q?Ond=c5=99ej_Bouda?= cc: Alvaro Herrera , =?UTF-8?Q?Ond=c5=99ej_Bouda?= , pgsql-general@lists.postgresql.org, Karsten Hilbert Subject: Re: backend crash on DELETE, reproducible locally In-reply-to: <8e260d7c-13e8-b398-14dd-2e079ff7e833@email.cz> References: <20181106185255.776mstcyehnc63ty@alvherre.pgsql> <8e260d7c-13e8-b398-14dd-2e079ff7e833@email.cz> Comments: In-reply-to =?UTF-8?Q?Ond=c5=99ej_Bouda?= message dated "Tue, 06 Nov 2018 20:37:58 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <31910.1541533784.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Tue, 06 Nov 2018 14:49:44 -0500 Message-ID: <31911.1541533784@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk =3D?UTF-8?Q?Ond=3Dc5=3D99ej_Bouda?=3D writes: > I thought triggers should be suspected. However, even when all the three= = > triggers have been disabled (ALTER TABLE DISABLE TRIGGER), the UPDATE = > crashed the server. Foreign-key triggers too? > What else could I try? A stack trace would be really helpful. https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_= backend regards, tom lane