|16:49||• Fixed ticket [16c9801c]: Segfault on DELETE with WHERE containing OR plus 3 other changes (artifact: 809d005f user: drh)|
|16:49||For DELETE operations, make sure that seeks on the main table are not deferred, since if they are and none of the indexes reference columns of the table, the seek might never occur until the OP_Delete opcode, which is too late. Fix for ticket [16c9801ceba49]. (check-in: 93a2bace user: drh tags: trunk)|
|16:06||In the WHERE generator, when building code for a DELETE operation, make sure that seeks to the main table are not deferred. This is a better fix for the [16c9801ceba49] bug than the previous. (Closed-Leaf check-in: 150dd09e user: drh tags: ticket-16c9801ce)|
|16:05||• Ticket [16c9801c] Segfault on DELETE with WHERE containing OR status still Open with 3 other changes (artifact: 387d6abf user: drh)|
|14:33||• Ticket [16c9801c]: 3 changes (artifact: bbb174fc user: drh)|
|11:31||Do not scan indexes that have the integer primary key as their left-most column. This fixes the crash of ticket [16c9801ceba] but it seems like the wrong fix. More investigation needed. (check-in: 50312273 user: drh tags: ticket-16c9801ce)|
|03:56||• Ticket [16c9801c] Assertion fault on DELETE status still Open with 6 other changes (artifact: 35b41059 user: drh)|
|03:26||• New ticket [16c9801c]. (artifact: 79eb5be6 user: drh)|
|Title:||Segfault on DELETE with WHERE containing OR|
|Last Modified:||2016-05-06 16:49:58|
|Version Found In:||3.12.2|
drh added on 2016-05-06 03:26:38:
The following causes an assertion fault, or segfaults if asserts are disabled. The problem occurs on the DELETE statement.
CREATE TABLE t1(x INTEGER PRIMARY KEY, y TEXT); INSERT INTO t1(x,y) VALUES(1,'zebra'); CREATE INDEX t1x ON t1(x); DELETE FROM t1 WHERE x IS NULL OR x<2;
This problem was introduced in version 3.12.0 by check-in [96ea990942]. A simple work-around is to drop the redundant "t1x" index. As far as I can tell, this problem only comes up when there is an index on the INTEGER PRIMARY KEY, as illustrated by t1x above.
drh added on 2016-05-06 03:56:34:
Another problem is that the SELECT statement below does a full table scan:
CREATE TABLE t2(x INTEGER PRIMARY KEY, y TEXT); SELECT * FROM t2 WHERE x IS NULL;
If this optimization is fixed, the situation that causes the bug in this ticket would never come up, as far as I can tell.
drh added on 2016-05-06 14:33:25:
Another crashing example that does not use the degenerate index:
CREATE TABLE t1(x INTEGER PRIMARY KEY, y TEXT); INSERT INTO t1(x,y) VALUES(1,'zebra'); CREATE INDEX t1x ON t1(abs(x)); DELETE FROM t1 WHERE abs(x)=99 OR abs(x)<2;
These seem to be the requirements to cause the crash:
The OR clause uses the OP_Seek opcode to do a deferred seek of the main table. That deferred seek is resolved at the first OP_Column. But if none of the indexes ever reference a column (because they all only reference the integer primary key) then the seek does not occur prior to the OP_Delete.