maria:bb-10.2-sysprg

Branch merges

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related charm recipes

da26e2e... by Vladislav Vaintroub on 2021-03-25

Cleanup - reduce duplicate code, in SSL IO error handling.

5a79807... by Sergei Golubchik on 2021-03-24

MDEV-25242 Server crashes in check_grant upon invoking function with userstat enabled

use check_grant(..., number_of_tables=1, ...) if you only need
to check privileges for one table

cdb86fa... by Vladislav Vaintroub on 2021-03-24

MDEV-23740 postfix - potentially uninitialized variable passed to vio_socket_io_wait.

Thanks to Daniel Black for reporting.

c4807c1... by Sergei Golubchik on 2021-03-23

MDEV-24879 Client crash on undefined charsetsdir

3dae564... by Daniele Sciascia <email address hidden> on 2021-03-22

Follow up fixes for making @@wsrep_provider read-only

* Remove usage of wsrep_provider variable in galera_ist_restart_joiner
* Rename galera_load_provider.inc and galera_unload_provider.inc to
  galera_stop_replication.inc and galera_start_replication.inc. Their
  original names were no longer reflecting what these include files do.

followup for ce3a2a688db

Reviewed-by: Jan Lindström <email address hidden>

9e57bd2... by Alexey Bychko <email address hidden> on 2021-03-23

fixed typo in postinst script

8f7a6cd... by Igor Babaev on 2021-03-23

MDEV-24767 Wrong result when forced BNLH is used for join supported
           by compound index

This typo bug may lead to wrong result sets for equi-join queries where
the join operation is supported by a compound index such that the order of
its components differs from the order of the corresponding columns in
the table the index belongs to. The bug manifests itself only when usage
of the BNLH algorithm is forced.

The fix for the bug was provided by Chu Huaxing.

56274bd... by Marko Mäkelä on 2021-03-22

MDEV-23076 Misleading "InnoDB: using atomic writes"

As suggested by Vladislav Vaintroub, let us remove misleading
and malformatted startup messages.

Even if the global variable srv_use_atomic_writes were set, we would
still invoke my_test_if_atomic_write() to check if writes are atomic
with a particular page size.

When using the default innodb_page_size=16k, page writes should be
atomic on NTFS when using ROW_FORMAT=COMPRESSED and KEY_BLOCK_SIZE<=4.

Disabling srv_use_atomic_writes when innodb_file_per_table=OFF does
not make sense, because that is a dynamic parameter.

We also correct the documentation string of innodb_use_atomic_writes
and remove the duplicate variable innobase_use_atomic_writes.

0f8caad... by Marko Mäkelä on 2021-03-22

MDEV-22653: Remove the useless parameter innodb_simulate_comp_failures

The debug parameter innodb_simulate_comp_failures injected compression
failures for ROW_FORMAT=COMPRESSED tables, breaking the pre-existing
logic that I had implemented in the InnoDB Plugin for MySQL 5.1 to prevent
compressed page overflows. A much better check is already achieved by
defining UNIV_ZIP_COPY at the compilation time.
(Only UNIV_ZIP_DEBUG is part of cmake -DWITH_INNODB_EXTRA_DEBUG=ON.)

0e96570... by Dmitry Shulga <email address hidden> on 2021-03-22

Added missed ' -- ' between the end of the lldb command options and the beginning of the arguments.