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-hackers(at)lists(dot)postgresql(dot)org, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: backend crash on DELETE, reproducible locally
Date: 2018-11-06 21:03:35
Message-ID: 2432.1541538215@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:
>>> Hm, what are the data types of those columns?

> scheduletemplate_id bigint NOT NULL,
> period_day smallint NOT NULL,
> timerange timerange NOT NULL,

OK, so here's a minimal reproducer:

drop table schedulecard;

create table schedulecard (
scheduletemplate_id bigint NOT NULL,
period_day smallint NOT NULL
);

CREATE INDEX schedulecard_overlap_idx
ON schedulecard USING gist
(scheduletemplate_id, (period_day::integer % 7));

insert into schedulecard values(12, 1);

update schedulecard set period_day = period_day + 7;

Interestingly, it doesn't crash if I change the index type to btree,
which I was not expecting because the crashing code seems pretty
independent of the index type.

Haven't traced further than that yet.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2018-11-06 21:04:23 Re: Idle query that's not "<IDLE>"?
Previous Message Ron 2018-11-06 20:59:34 Re: Idle query that's not "<IDLE>"?

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2018-11-06 21:04:07 Re: pread() and pwrite()
Previous Message Ondřej Bouda 2018-11-06 20:36:08 Re: backend crash on DELETE, reproducible locally