Re: backend crash on DELETE, reproducible locally

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ondřej Bouda <obouda(at)email(dot)cz>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: backend crash on DELETE, reproducible locally
Date: 2018-11-06 20:17:05
Message-ID: 450.1541535425@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

=?UTF-8?Q?Ond=c5=99ej_Bouda?= <obouda(at)email(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ondřej Bouda 2018-11-06 20:19:31 Re: backend crash on DELETE, reproducible locally
Previous Message Tom Lane 2018-11-06 20:14:08 Re: backend crash on DELETE, reproducible locally

Browse pgsql-hackers by date

  From Date Subject
Next Message Ondřej Bouda 2018-11-06 20:19:31 Re: backend crash on DELETE, reproducible locally
Previous Message Tom Lane 2018-11-06 20:14:08 Re: backend crash on DELETE, reproducible locally