Do not push conditions from where into materialized inner tables
of outer joins: this is not valid.

Problem was that test assumes locks to be granted on first-come-first-served (FCFS)
policy. However, in 10.2 we use by default Variance-Aware-Transaction-Scheduling
(VATS) algorithm. Test failure fixed by setting lock wait policy to FCFS.

In a general case the conditions with outer fields cannot
be pushed into materialized views / derived tables.
However if the outer field in the condition refers to a
single row table then the condition may be pushable.
In this case a special care should be taken for outer
fields when pushing the condition into a materialized view /
derived table.

        The rest of mysql/json functions implemented.
        CAST AS JSON implemented.

- added missing backslash
- removed duplicate definition of UT_LOW_PRIORITY_CPU/UT_RESUME_PRIORITY_CPU
- removed duplicate UT_RESUME_PRIORITY_CPU call

If a recursive CTE referred to a materialized view/derived table then
the query that used this CTE returned a bogus error message.

If mysqld crashed during the test suite run and gdb is available,
a stack trace will be printed automatically.

Code calling mtflush threads to exit was too late.

When we enter here wait_lock could be already gone i.e. NULL, that
should be allowed.

This is not a fix, this is instrumentation to find the bug.

During total-order replication, Query_log_event's checksum_alg
should be explicitly set to the current binlog_checksum as it
is not set for DML queries.
Note: wsrep_replicate_myisam enables replication of DMLs on
MyISAM tables using TOI.

See https://github.com/MariaDB/server/pull/235
I submit this code under the BSD-new license.

thd->variables.option_bits need to be restored after
plugin_thdvar_init() during post initialization of
wsrep threads.

Postfix: The pre-initialization of wsrep threads is not needed
for mysqldump sst method.

When a BF thread attempts to abort a victim thread's transaction,
the victim thread is not locked and thus its not safe to rely on
its data structures like htons registered for the trx.

So, instead of getting the registered htons from victim, innodb's
hton can be looked up directly from installed_htons[] and used to
abort the transaction. (Same technique is used in older versions)

Perform a post initialization of plugin-related variables
of wsrep threads after their global counterparts have been
initialized.

The crash is caused due to a race condition where wsrep
startup threads invoke ha_maria::implicit_commit() method
while maria_hton is partially initialized. The fix is to
skip this method if plugins are uninitialized.

MDEV-9820 Added server variable compression_default, which if 1/ON sets compres…

Do not include the suite into the default list until the tests are stable

MDEV-11195: Correct enablement of NUMA in innodb/xtradb

Added server variable compression_default, which if 1/ON sets compression on for all new InnoDB/XtraDB tables by default by setting PAGE_COMPRESSED=1

The .rdiff applied ok locally with my copy of patch, but failed with
"misordered hunks" on a test host. Maybe that host has a more strict
version of `patch`.

With "WL#6047 - Do not allocate trx id for read-only transactions"
m_prebuilt->trx->id is always 0 for read-only transactions. This makes
it useless as an index for fuzzy counters.

Use server thread id instead similarly to MySQL.

Conflicts:
	sql/share/errmsg-utf8.txt

BINLOG statement output by mysqlbinlog actually has the base64 of the
non-compressed event. So remove my previous incorrect review change,
which allowed compressed event types for BINLOG statement.

Also add a couple test cases for this, running mysqlbinlog | mysql.