Aleksey Midenkov 498a96a478 MDEV-20441 ER_CRASHED_ON_USAGE upon update on versioned Aria table ...

Turn read cache off for update and multi-update for versioned
table. no_cache is reinited on each TABLE open because it is
applicable for specific algorithms.

As a side fix vers_insert_history_row() honors vers_write setting.

Aria with row_format=fixed uses IO_CACHE of type READ_CACHE for
sequential read in update loop. When history row is inserted inside
this loop the cache misses it and fails with error.

TODO:

Currently maria_extra() does not support SEQ_READ_APPEND. Probably it
might be possible to use this type of cache.

2019-12-02 11:48:37 +03:00

..

r

MDEV-20441 ER_CRASHED_ON_USAGE upon update on versioned Aria table

2019-12-02 11:48:37 +03:00

t

MDEV-20441 ER_CRASHED_ON_USAGE upon update on versioned Aria table

2019-12-02 11:48:37 +03:00

common_finish.inc

versioning test suite fixes

2019-10-10 00:20:34 +03:00

common.inc

versioning test suite fixes

2019-10-10 00:20:34 +03:00

common.opt

Tests: versioning suite fix when no test_versioning plugin

2019-07-09 10:01:54 +03:00

disabled.def

MDEV-14820 System versioning is applied incorrectly to CTEs

2018-05-12 10:16:45 +02:00

engines.combinations

MDEV-15458 Segfault in heap_scan() upon UPDATE after ADD SYSTEM VERSIONING

2019-05-17 13:53:22 +02:00

engines.inc

…

innodb.combinations

MDEV-17038 ALTER TABLE CHANGE COLUMN c1 c1 bigint NOT NULL - generates error if table uses SYSTEM VERSIONING

2018-11-01 16:42:06 +02:00

innodb.inc

MDEV-17038 ALTER TABLE CHANGE COLUMN c1 c1 bigint NOT NULL - generates error if table uses SYSTEM VERSIONING

2018-11-01 16:42:06 +02:00

key_type.combinations

versioning test suite fixes

2019-10-10 00:20:34 +03:00

key_type.inc

versioning test suite fixes

2019-10-10 00:20:34 +03:00

wait_system_clock.inc

…