Aleksey Midenkov 97aa07abf5 MDEV-21147 Assertion `marked_for_read()' upon UPDATE on versioned table via view ...

"write set" for replication finally got its correct place
(mark_columns_per_binlog_row_image()). When done generally in
mark_columns_needed_for_update() it affects optimization
algorithm. used_key_is_modified, query_plan.using_io_buffer are
wrongly set and that leads to wrong prepare_for_keyread() which limits
read_set.

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

7.4 KiB

Raw Blame History

View Raw