Due to a typo, the wrong grant_table was used when fetching privileges
for roles.
Signed-off-by: Vicențiu Ciorbaru <vicentiu@mariadb.org>

MDEV-9278 - Debian: the Lintian complains about "shlib-calls-exit" in ha_spider.so

Handlersocket handles errors in a way that it aborts program execution. In most
cases it is done via abort(). One exception was host/service resolution failure,
which was aborted with exit().

As a workaround replaced this exit() with abort() for symmetry with other error
handling.

Previous fix using wait condition did not work because of MDEV-9867, so
we have to use conditional sleep instead. Sleep will only happen if the test
is executed after another one which also ran buffer pool dump without
server restart between two tests

Fixed calculating pointer to memory allocated for names in numeric format in unpacking procedure.

10.0 part of the fix

update main.delayed test after 38b89a61
ALTER TABLE ... COMMENT is no longer blocking,
use a different ALTER TABLE variant.

Fixed more cases for MDEV-6282

don't strcpy a string to itself

s/Execute/Query/ to account for --ps-protocol

typo. the code was not matching the comment

fix a buffer overflow in extension_based_table_discovery
(that only happens in debug builds)

Remove Linuxism. 

Works fine with a POSIX-compat shell

don't crash in debug builds. issue an error message on corrupt event

5.5 part of the fix

don't allocate all the stack, leave some stack for
function calls.

To test I added the following line:
  alloca_size = available_stack_size() - X
at X=4096 or less mysqld crashed, at 8192 mtr test passed.

remove erroneous free() call

Update sponsors

It could have happened that one of previous tests already executed
buffer pool dump and set the status variable value, so when it's been
checked, the check passes too early, before the dump starts and
the dump file is created. See more detailed explanation in MDEV-9713.

Fixed by waiting for the current time to change in case it equals
to the timestamp in the status variable, and then checking that
the status variable not only matches the expected pattern, but also
differs from the previous value, whatever it was.

In row_search_for_mysql function on XtraDB there was a old logic
where null bytes were inited. This caused server to think that
key value is null and continue on incorrect path.

Logrotate script assumed an error if mysqladmin failed to connect to server
and there's mysqld process exists. However there can be non-system instance of
mysqld running (e.g. in docker) making this assumption wrong.

Check pid file existance instead.

Update AskMonty and Atlassian references to MariaDB

Fix spelling: occurred, execute, which etc

There was a race between end_slave() and cleanup code at the end of
handle_slave_sql(). This could cause access to master_info_index and
global_rpl_thread_pool after they had been freed.

Fix by skipping that cleanup if server shutdown is in progress, as is done
in other parts of the code as well (the cleanup, which stops worker threads
that are not needed anymore, is redundant anyway when the server is shutting
down).

MDEV-9643: Don't emit any "deb-systemd-helper not found" warnings

The test created a file in location relative to the datadir
(a few levels above datadir).
The file was created by MariaDB server (via INTO OUTFILE), and
later removed by mysqltest (via remove_file). The problem is that
when the vardir is a symlink, MariaDB server and mysqltest can
resolve such paths differently. MariaDB server would return back
to where the symlink is located, while mysqltest would go above
the real directory. For example, if the test is run with --mem,
and /bld/5.5/mysql-test/var points at /dev/shm/var_auto_X, then
SELECT INTO OUTFILE created a file in /bld/5.5/mysql-test , but
remove_file would look for it in /dev/shm/.

The test is re-written so that all paths are resolved in perl,
the logic itself hasn't changed.

Index access becomes range every once in a while. Masked the value in addition
to other already masked columns

Debian tests are run in 2017, update the test to
use 2027 as a "future".

on FreeBSD 10 jemalloc is in libc, no separate libjemalloc is needed

this simplifies merging of MySQL and TokuDB