maria:bb-10.5-monty

Last commit made on 2019-06-26
Get this branch:
git clone -b bb-10.5-monty https://git.launchpad.net/maria

Branch merges

Branch information

Name:
bb-10.5-monty
Repository:
lp:maria

Recent commits

79cd2f5... by Monty <email address hidden> on 2019-06-26

Added type conversion to fix compilation error on windows

e133aa1... by Monty <email address hidden> on 2019-06-26

Added testcase for MDEV-19585

MDEV-19585 Assertion with S3 table and flush_tables

1a41fc7... by Monty <email address hidden> on 2019-06-26

Merge remote-tracking branch 'origin/10.4' into 10.5

8e2a24b... by Monty <email address hidden> on 2019-06-26

Added s3_protocol_version=auto

0765d82... by Monty <email address hidden> on 2019-06-26

Updated to latest libmarias3 to fix some compatiblity issues

f489434... by Monty <email address hidden> on 2019-06-26

MDEV-19575 Fixed assert in ma_pagecache

There was a bug in the page cache that didn't take into account that
another thread could be waiting for a page to be read by read_big_block().
Fixed by releasing all waiters in read_big_block()

f44c687... by Monty <email address hidden> on 2019-06-26

S3: Don't do discover in mysql database (makes boot faster and safer)

9ca5176... by Monty <email address hidden> on 2019-06-26

BUILD scripts: Don't build with-plugin-test_sql_discovery staticly

5c5ea59... by Vlad Lesin on 2019-05-28

MDEV-19867: fix mysqldump to by default not copy S3 tables

There are two options when coping S3 tables with mysqldump
(there is startup option --copy_s3_tables, boolean, default no)
1) Ignore all tables with engine S3, as the data is already safe in S3 and any
computer where you restore the backup will automatically discover the S3 table.
2) Copy the table as a normal table with the following 2 changes:
- Change ENGINE=S3 to ENGINE=ARIA;
- After copy add to log 'ALTER TABLE table_name ENGINE=S3'

bb702c2... by Monty <email address hidden> on 2019-06-26

Limit minium aria_block_size to 4096

MDEV-19585 Assertion with S3 table and flush_tables

The limit has to be increased so that MariaDB can create system tables.
It should not have any notable impact on performance.

There should not be any notable performance differences between 1K and 4K,
especially for temporary tables. In most cases using bigger blocks is also
faster (with the possible exception of doing key reads of not fixed length
keys).