Problem was that SEQUENCE::table was shared among threads, which caused
several threads to use the same object at the same time.

Conflicts:
	mysql-test/r/func_json.result
	mysql-test/r/win.result
	mysql-test/t/func_json.test
	mysql-test/t/win.test
	sql/share/errmsg-utf8.txt
	storage/rocksdb/ha_rocksdb.cc
	storage/rocksdb/mysql-test/rocksdb/r/tbl_opt_data_index_dir.result

- Support first_linear_tab() traversal for degenerate joins

The debug flag recv_no_log_write prohibits writes of redo log records for
modifying page data. The debug assertion was failing when fil_names_clear()
was writing the informative MLOG_FILE_NAME and MLOG_CHECKPOINT records
which do not modify any data.

log_reserve_and_open(), log_write_low(): Remove the debug assertion.

log_pad_current_log_block(), mtr_write_log(),
mtr_t::Command::prepare_write(): Add the debug assertion.

During InnoDB startup, change buffer merge operations are prohibited
before recv_apply_hashed_log_recs(true), which performs the last phase
of redo log apply. Before this call, ibuf_init_at_db_start() would be
invoked, and it could trigger the debug assertion.

ibuf_init_at_db_start(): Do not declare the mini-transaction as
"inside change buffer", because nothing is being written in the
mini-transaction. The purpose of this function is only to initialize
the memory data structures from the persistent data structures.

        Fixed the path comparison.

        Options handling implemented for ST_AsGeoJSON.

Also removed clang-3.9
Signed-off-by: Daniel Black <daniel.black@au.ibm.com>

It may produce test failures like this because of non-deterministic
cost calculations:

-1	SIMPLE	t1	#	col1	col1	259	NULL	#	Using where
+1	SIMPLE	t1	#	col1	NULL	NULL	NULL	#	Using where

        Implement the 'option' argument for the ST_GeomFromGeoJSON.

Functions:
check_routine_name()
check_string_byte_length()
check_string_char_length()
check_ident_length()

Include Hindi error messages to debian packages.

- This is more in line with MariaDB environment
- And help with rocksdb.bulk_load_errors test, too

Fixed plugins.locales failure.

This is an addition to original patch: activate hi_IN error messages.

Part #2.

So disable it there for now.

- Fix the bad merge in drop_table.test
- Remove the obsolete rocksdb_info_log_level=info_level option
  which caused warnings to be found in the error log.

It uses SHOW ENGINE TRANSACTION STATUS, which is not supported in MariaDB

See MDEV-12279, MariaDB is still not able to produce nice error messages
in this case.

(Could we just put the mark into bulk_load.inc ?)

Comment out a part of testcase that uses it.

This fixes result mismatches in rocksdb.issue111, rocksdb.hermitage,
rocksdb.rocksdb_locks