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 1gK7mj-0004eY-Qw for pgsql-general@arkaria.postgresql.org; Tue, 06 Nov 2018 20:17:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gK7mh-0000si-Lg for pgsql-general@arkaria.postgresql.org; Tue, 06 Nov 2018 20:17:11 +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 1gK7mh-0000rn-9j for pgsql-general@lists.postgresql.org; Tue, 06 Nov 2018 20:17:11 +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 1gK7me-0002hx-T2 for pgsql-general@lists.postgresql.org; Tue, 06 Nov 2018 20:17:10 +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 wA6KH5Ir000451; Tue, 6 Nov 2018 15:17:05 -0500 From: Tom Lane To: =?UTF-8?Q?Ond=c5=99ej_Bouda?= cc: Alvaro Herrera , pgsql-general@lists.postgresql.org Subject: Re: backend crash on DELETE, reproducible locally In-reply-to: <33d144b9-5208-8d32-7e95-94ed4d2931b8@email.cz> References: <20181106194553.dynhd2xuivo56ymd@alvherre.pgsql> <33d144b9-5208-8d32-7e95-94ed4d2931b8@email.cz> Comments: In-reply-to =?UTF-8?Q?Ond=c5=99ej_Bouda?= message dated "Tue, 06 Nov 2018 20:54:31 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <449.1541535425.1@sss.pgh.pa.us> Date: Tue, 06 Nov 2018 15:17:05 -0500 Message-ID: <450.1541535425@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk =?UTF-8?Q?Ond=c5=99ej_Bouda?= writes: > There are some simple btree indexes due to foreign keys, and this one, > which seems as the cause for the crashes: > CREATE INDEX schedulecard_overlap_idx > ON public.schedulecard USING gist > (scheduletemplate_id, (period_day::integer % 7), timerange) > TABLESPACE pg_default; > When I drop it, the UPDATE statement gets executed without any problems. > When I create the index again, the same UPDATE crashes the server. Hm, what are the data types of those columns? And I assume you've got btree_gist installed? regards, tom lane