and partition_info::set_show_version_string - they were
already broken and impossible to maintain

unused freshly initialized record should be trashed
with TRASH_ALLOC, not TRASH_FREE

remove redundant method

also, return different values for different errors in my_addr_resolve()

MDEV-11075: Power - runtime detection of optimized instructions

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

        The weird logic of json_contains was implemented.

WL#7682 in MySQL 5.7 introduced the possibility to create light-weight
temporary tables in InnoDB. These are called 'intrinsic temporary tables'
in InnoDB, and in MySQL 5.7, they can be created by the optimizer for
sorting or buffering data in query processing.

In MariaDB 10.2, the optimizer temporary tables cannot be created in
InnoDB, so we should remove the dead code and related data structures.

This was originally part of MDEV-11487.

Adjust some results and error codes.

        Support for '**' in json path expressions added.

Merge branch '10.2-MDEV-9872-crc32-generic-message' of https://github.com/grooverdan/mariadb-server into grooverdan-10.2-MDEV-9872-crc32-generic-message

MDEV-11075: changing to algorithm innodb from crc32

With innodb compressed pages formerly as crc32 changing to the
innodb checksum, optimize for speed by only calcuating the big
endian variant of crc32 after checking that the little endian
doesn't validate the page.
Signed-off-by: Daniel Black <daniel.black@au.ibm.com>

MDEV-11422 rpl.rpl_parallel_optimistic_nobinlog failed in buildbot with "InnoDB: Killing connection failed Deadlock"

innobase_kill_query(): Remove the bogus warning message
(for the valid outcome err==DB_DEADLOCK) that was added in

commit fec844ac
Author: Jan Lindström <jan.lindstrom@mariadb.com>
Date:   Tue Sep 6 09:43:16 2016 +0300

    Merge InnoDB 5.7 from mysql-5.7.14.

Also, remove some redundant variables and add a debug assertion for
enforcing the proper outcome of lock_trx_handle_wait().

buffer pool size

The reason for the exception is previous overflow in multiplication of
two 32bit integers (product was 0 rather than expected 8GB, due
to truncation)

        When the json was just a scalar value, json_extract tried
        to parse after the value ended.

        Test case added.

        Test case added.