From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ondřej Bouda <obouda@email.cz>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: backend crash on DELETE, reproducible locally
Date: Tue, 06 Nov 2018 15:17:05 -0500
Message-ID: <450.1541535425@sss.pgh.pa.us> (raw)
In-Reply-To: <33d144b9-5208-8d32-7e95-94ed4d2931b8@email.cz>
References: <20181106194553.dynhd2xuivo56ymd@alvherre.pgsql>
<33d144b9-5208-8d32-7e95-94ed4d2931b8@email.cz>
=?UTF-8?Q?Ond=c5=99ej_Bouda?= <obouda@email.cz> 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
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 using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: tgl@sss.pgh.pa.us, obouda@email.cz, alvherre@2ndquadrant.com, pgsql-general@lists.postgresql.org
Subject: Re: backend crash on DELETE, reproducible locally
In-Reply-To: <450.1541535425@sss.pgh.pa.us>
* 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