maria:bb-10.3-MDEV-15058-2

Last commit made on 2018-06-25
Get this branch:
git clone -b bb-10.3-MDEV-15058-2 https://git.launchpad.net/maria

Branch merges

Branch information

Name:
bb-10.3-MDEV-15058-2
Repository:
lp:maria

Recent commits

8aecd14... by Marko Mäkelä

MDEV-15058: Allocate buf_pool statically

buf_pool_t::create(): Replaces buf_pool_init().

buf_pool_t::close(): Replaces buf_pool_free().

FIXME: Do not add buf_pool_t::is_initialised()

375df6f... by Marko Mäkelä

MDEV-15058: Remove multiple buffer pool instances

This is work in progress.
FIXME: Clean up the page cleaner data structures further.
FIXME: Use more atomic memory operations; use mutexes less frequently.

This also removes a MariaDB/InnoDB dependency on libnuma.

page_cleaner_t::is_requested, page_cleaner_t::is_started: Remove.

buf_flush_page_cleaner: Renamed from buf_flush_page_cleaner_coordinator.

buf_flush_page_cleaner_worker: Remove.

1abd877... by Alexander Barkov

MDEV-8049 name_const() is not consistent about its signess

bcc2100... by Alexander Barkov

MDEV-16471 mysqldump throws "Variable 'sql_mode' can't be set to the value of 'NULL' (1231)"

9dc81f7... by Eugene

MDEV-16330 Allow instant change of WITH SYSTEM VERSIONING column attribute

Changing columns WITH/WITHOUT SYSTEM VERSIONING doens't require to read data at
all. Thus it should be an instant operation.

Patch also fixes a bug when ALTER_COLUMN_UNVERSIONED wasn't passed to InnoDB
to change its internal structures.

change_field_versioning_try(): apply WITH/WITHOUT SYSTEM VERSIONING
change in SYS_COLUMNS for one field.

change_fields_versioning_try(): apply WITH/WITHOUT SYSTEM VERSIONING
change in SYS_COLUMNS for every changed field in a table.

change_fields_versioning_cache(): update cache for versioning property
of columns.

ff09512... by Alexander Barkov

MDEV-16489 when lead() returns null on a datetime field, the result is treated as the literal string '[NULL]'

9c53cbd... by Alexander Barkov

MDEV-15941 Explicit cursor FOR loop does not close the cursor

b534a7b... by Oleksandr "Sanja" Byelkin

Merge branch '10.3' into bb-10.3-fix_len_dec

083279f... by Oleksandr "Sanja" Byelkin

Merge commit '6b8802e8dd5467556a024d807a1df23940b00895' into bb-10.3-fix_len_dec

956b296... by Igor Babaev

MDEV-16420 View stop working after upgrade from 10.1.15 to 10.3.7

This bug happened for queries that used a materialized view that
renamed columns of the specifying query in an inner table of
an outer join. For such a query name resolution for a column
belonging the view could fail if the underlying column was
non-nullable.
When creating the defintion of the the temporary table for
the materialized view used in the inner part of an outer join
the definition of the non-nullable columns are created by the
function create_tmp_field_from_item() that names the columns
according to the names of the underlying columns. So these names
should be changed for the view column names.

This bug cannot be reproduced in 10.2 because there setup_fields()
called when preparing joins in the view specification effectively
renames the underlying columns in the function find_field_in_view().
In 10.3 this renaming was removed as improper
(see Monty's commit b478276b04d4dd122e2ed4d4e2cd7eb69c0fb2d2).