Re: backend crash on DELETE, reproducible locally

From: Ondřej Bouda <obouda(at)email(dot)cz>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: backend crash on DELETE, reproducible locally
Date: 2018-11-06 19:54:31
Message-ID: 33d144b9-5208-8d32-7e95-94ed4d2931b8@email.cz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Dne 6.11.2018 v 20:45 Alvaro Herrera napsal(a):
> What indexes are there in this table? Indexes on expressions are
> particularly suspect.

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.

Regards,
Ondřej Bouda

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2018-11-06 20:14:08 Re: backend crash on DELETE, reproducible locally
Previous Message Tom Lane 2018-11-06 19:49:44 Re: backend crash on DELETE, reproducible locally

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Gierth 2018-11-06 20:05:26 Re: Optimizing nested ConvertRowtypeExpr execution
Previous Message Tom Lane 2018-11-06 19:49:44 Re: backend crash on DELETE, reproducible locally