maria:bb-10.2-MDEV-22447

Last commit made on 2021-09-16
Get this branch:
git clone -b bb-10.2-MDEV-22447 https://git.launchpad.net/maria

Branch merges

Branch information

Name:
bb-10.2-MDEV-22447
Repository:
lp:maria

Recent commits

2f812e8... by Oleksandr "Sanja" Byelkin

MDEV-22447: SIGSEGV in Item::val_uint on EXPLAIN

take into account possible NULL

696de6d... by THIRUNARAYANAN BALATHANDAYUTHAPANI

MDEV-25702 Auxiliary FTS table evicts during optimize table

InnoDB could evict the fts auxiliary table in
row_fts_merge_insert(). So bulk insert could be
dealing with garbage FTS auxiliary table.Patch
should delay closing the table in row_fts_merge_insert().

f345172... by Vladislav Vaintroub

MDEV-26527 speedup appveyor build - 10.2

3504f70... by Vladislav Vaintroub

Bison 3.7 - fix "conversion from 'ptrdiff_t' to 'ulong', possible loss of data"

879e21b... by Vladislav Vaintroub

Define minbuild target for 10.2

7e6b033... by Vladislav Vaintroub

Fix MYSQL_MAINTAINER_MODE=ERR, on Windows, with Ninja , in 10.2

A conversion warning 4267 that we want to disable(prior to 10.3),
was suppressed with cmake VS generator for C++ and C, despite being set
only for CXX flags.

The fix is to disable the warning in C flags, too. In 10.2, this warning
is noisy, in 10.3 it is fixed.

ac064c2... by Marko Mäkelä

Fix an occasional timeout in innodb.alter_partitioned

d09426f... by Marko Mäkelä

MDEV-26537 InnoDB corrupts files due to incorrect st_blksize calculation

The st_blksize returned by fstat(2) is not documented to be
a power of 2, like we assumed in
commit 58252fff15acfe7c7b0452a87e202e3f8e454e19 (MDEV-26040).
While on Linux, the st_blksize appears to report the file system
block size (which hopefully is not smaller than the sector size
of the underlying block device), on FreeBSD we observed
st_blksize values that might have been something similar to st_size.

Also IBM AIX was affected by this. A simple test case would
lead to a crash when using the minimum innodb_buffer_pool_size=5m
on both FreeBSD and AIX:

seq -f 'create table t%g engine=innodb select * from seq_1_to_200000;' \
1 100|mysql test&
seq -f 'create table u%g engine=innodb select * from seq_1_to_200000;' \
1 100|mysql test&

We will fix this by not trusting st_blksize at all, and assuming that
the smallest allowed write size (for O_DIRECT) is 4096 bytes. We hope
that no storage systems with larger block size exist. Anything larger
than 4096 bytes should be unlikely, given that it is the minimum
virtual memory page size of many contemporary processors.

MariaDB Server on Microsoft Windows was not affected by this.

While the 512-byte sector size of the venerable Seagate ST-225 is still
in widespread use, the minimum innodb_page_size is 4096 bytes, and
innodb_log_file_size can be set in integer multiples of 65536 bytes.

The only occasion where InnoDB uses smaller data file block sizes than
4096 bytes is with ROW_FORMAT=COMPRESSED tables with KEY_BLOCK_SIZE=1
or KEY_BLOCK_SIZE=2 (or innodb_page_size=4096). For such tables,
we will from now on preallocate space in integer multiples of 4096 bytes
and let regular writes extend the file by 1024, 2048, or 3072 bytes.

The view INFORMATION_SCHEMA.INNODB_SYS_TABLESPACES.FS_BLOCK_SIZE
should report the raw st_blksize.

For page_compressed tables, the function fil_space_get_block_size()
will map to 512 any st_blksize value that is larger than 4096.

os_file_set_size(): Assume that the file system block size is 4096 bytes,
and only support extending files to integer multiples of 4096 bytes.

fil_space_extend_must_retry(): Round down the preallocation size to
an integer multiple of 4096 bytes.

1c378f1... by Vladislav Vaintroub

Speedup build of the MSI package

c7184c4... by Sergei Golubchik

fix main.truncate failures in --embedded