Re: backend crash on DELETE, reproducible locally
| От | Tom Lane |
|---|---|
| Тема | Re: backend crash on DELETE, reproducible locally |
| Дата | |
| Msg-id | 2432.1541538215@sss.pgh.pa.us обсуждение исходный текст |
| Ответы |
Re: backend crash on DELETE, reproducible locally
Re: backend crash on DELETE, reproducible locally |
| Список | pgsql-hackers |
=?UTF-8?Q?Ond=c5=99ej_Bouda?= <obouda@email.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
В списке pgsql-hackers по дате отправления: