maria:bb-10.8-midenok

Last commit made on 2022-02-19
Get this branch:
git clone -b bb-10.8-midenok https://git.launchpad.net/maria

Branch merges

Branch information

Name:
bb-10.8-midenok
Repository:
lp:maria

Recent commits

627654d... by midenok

TABLE::referenced_by_foreign_table()

d4f46e3... by midenok

Cleanup: check_native_partitioned() removed

We should not add native partitioning in future.

c60844b... by midenok

MDEV-27328 Change of SYSTEM_TIME partitioning options is not possible without data copy

When we need to add/remove or change LIMIT, INTERVAL, AUTO (10.8 and
more) we have to recreate partitioning from scratch. Such operations
should be done fast. To remove options like LIMIT or INTERVAL one
should write:

alter table t1 partition by system_time;

The command checks whether it is new or existing SYSTEM_TIME
partitioning. And in the case of new it behaves as CREATE would do:
adds default number of partitions (2). If SYSTEM_TIME partitioning
already existed it just changes its options: removes unspecified ones
and adds/changes those specified explicitly. In case when partitions
list was supplied it behaves as usual: does full repartitioning.

To sum up, ALTER for SYSTEM_TIME partitioning does full repartitioning
when:

  - INTERVAL was added or changed;
  - partition list or partition number was specified;

Otherwise it does fast alter table.

Cleaned up dead condition in set_up_default_partitions().

4b14874... by Marko Mäkelä

Merge 10.7 into 10.8

a90e116... by THIRUNARAYANAN BALATHANDAYUTHAPANI

MDEV-27312 LeakSanitizer error in trx_mod_table_time_t::start_bulk_insert

  - InnoDB fails to apply the bulk insert operation for the stats
table during DDL. During create table, InnoDB does dict_stats_save()
and freshly insert into innodb_table_stats and innodb_index_stats
table.

03ed2e9... by THIRUNARAYANAN BALATHANDAYUTHAPANI

MDEV-27318 Assertion `data_size < srv_sort_buf_size' failed in row_merge_bulk_buf_add

 InnoDB fails to add the tuple size which is greater than
innodb_sort_buffer_size. InnoDB should write the field
which are greater than 2000 bytes into the temporary file
and place the offset, length and make it as a new tuple.
InnoDB should buffer the newly created tuple without any
problem during bulk index

a23f3ee... by Marko Mäkelä

Merge 10.6 into 10.7

ba5ef63... by Marko Mäkelä

MDEV-27476 heap-use-after-free in buf_pool_t::is_block_field()

This follows up commit 017d1b867b12ff36b3b871c3d57719907a905659.
In commit aaef2e1d8c843d1e40b1ce0c5199c3abb3c5da28 (MDEV-27058)
some more problematic debug assertions were added.

btr_search_update_block_hash_info(), trx_purge_truncate_history():
Use simpler assertions to check that an uncompressed page is present.

0261eac... by Marko Mäkelä

Merge 10.5 into 10.6

017d1b8... by Marko Mäkelä

MDEV-27476 heap-use-after-free in buf_pool_t::is_block_field()

mtr_t::modify(): Remove a debug assertion that had been added
in commit 05fa4558e0e82302ece981deabce764491464eb2 (MDEV-22110).
The function buf_pool_t::is_uncompressed() is only safe to invoke
while holding a buf_pool.page_hash latch so that buf_pool_t::resize()
cannot concurrently invoke free() on any chunks.