MariaDB

maria:bb-10.4-MDEV-24964

  1. Git
  2. lp:maria
  3. bb-10.4-MDEV-24964
Last commit made on 2021-02-24
Get this branch:
git clone -b bb-10.4-MDEV-24964 https://git.launchpad.net/maria

Branch merges

Branch information

Name:
bb-10.4-MDEV-24964
Repository:
lp:maria

Recent commits

9ff63bf... by Jan Lindström

MDEV-24964 : Heap-buffer-overflow on wsrep_schema.cc ::remove_fragments

Problem was that we used heap allocated key using too small
array. Fixed by using dynamic memory allocation using actual
needed size.

2628fa2... by Daniel Black

MDEV-20857: perf schema conflict name filename_hash

filename_hash is a function from libiberty.a from the system
but also an expored name in the perf schema static library.

We'll use a different name.

ad0f0d2... by Vicențiu Ciorbaru

Merge branch '10.3' into 10.4

13f0e1e... by Vicențiu Ciorbaru

Merge branch '10.2' into 10.3

9e259d5... by Vicențiu Ciorbaru

Remove race condition during `make dist`

Introduced by 85828b8f22e7f4dfa6a5d4b0a1ab9e133e7feea7

This is running 2 git processes in parallel, which, if unlucky can cause
either of them to fail with "File already exists" error.

3c9d03e... by Marko Mäkelä

Merge 10.3 into 10.4

245d33d... by Sergei Golubchik

Merge branch 'github/10.4' into 10.4

8b77e6c... by Robert Bindar

MDEV-24114 SHOW CREATE USER doesnt display correct password expiry status

Given PASSWORD EXPIRE and PASSWORD EXPIRE [NEVER|INTERVAL x DAY] are
two different mechanisms, SHOW CREATE USER should display all the
information required to restore the state of an account which
includes both a manual expired state and an automatic policy.

The solution proposed here keeps a CREATE USER ... PASSWORD EXPIRE
statement and adds an aditional
ALTER USER .. PASSWORD EXPIRE [NEVER|INTERVAL x DAY] when necessary

This way a tool can restore almost the complete state of an account
as it was before a dump. The only information left still is the
value of the password_last_changed column from mysql.global_priv

69bf55f... by Marko Mäkelä

Merge 10.2 into 10.3

787c475... by THIRUNARAYANAN BALATHANDAYUTHAPANI

MDEV-24913 Assertion !recv_no_log_write in log_write_up_to()

- The commit 5fd3c7471e3e0673b50d309567c9747d36f09412(MDEV-24709)
resets the recv_no_ibuf_operations in
recv_recovery_from_checkpoint_start(), but InnoDB fails to reset
the variable recv_no_log_write() during that time and that leads
to the assert failure.