databases/mysql80-{client, server}: Update to latest release 8.0.33

Bugs Fixed

NDB Cluster: Occasional temporary errors which could occur when

opening a table from the NDB dictionary while repeatedly performing
concurrent schema operations were not retried. (Bug #34843889)

NDB Cluster: During iteration, ordered index scans retain a cursor

position within each concurrently scanned ordered index fragment.
Ordered index fragments are modified and balanced as a result of
committing DML transactions, which can require scan cursors to be moved
within the tree. When running with query threads configured
(AutomaticThreadConfig set to 1), multiple threads can access the same
index fragment tree structure, and the scans of multiple threads can
have their cursors present in the same structure.

The current issue arose due to an assumption in the logic for moving

scan cursors when committing DML operations that all scan cursors
belonged to the LDM thread owning the index fragment, which did not
allow for the possibility that such fragments might belong to query
threads. (Bug #33379702)

References: See also: Bug #32257063.

InnoDB: Dead code removal. (Bug #35036850, Bug #109873)

InnoDB: Error messages related to innodb_doublewrite moved to the

error log. (Bug #34883045, Bug #109330)

InnoDB: Prevent online DDL operations from accessing out-of-bounds

memory. (Bug #34750489, Bug #108925)

InnoDB: ALTER TABLE ... AUTO_INCREMENT could be set to less than MAX

+ 1 and not forced to MAX + 1. (Bug #33419246, Bug #105092)

InnoDB: Innodb_data_pending_fsyncs could show extremely high

inaccurate values because of a variable overflow. (Bug #30133150)

Partitioning: Some IN() queries on partitioned tables were not

always handled correctly. (Bug #34801284)

References: This issue is a regression of: Bug #32311183.

Partitioning: Queries using the INDEX_MERGE optimizer hint was not

handled correctly in all cases. (Bug #34797257)

Replication: XA transactions whose XIDs contained null bytes could

not be recovered. (Bug #34918985)

Replication: When binlog_order_commits was set equal to 1, for any

two transactions and for any sub-step of the commit phase, the
transaction that was written to the binary log first did not always
execute the sub-step first, as expected. (Bug #34703698)

Replication: Some binary log events were not always handled

correctly. (Bug #34617506)

Replication: The binary log recovery process did not report all

possible error states. (Bug #33658850)

Replication: Following CHANGE REPLICATION SOURCE TO

SOURCE_CONNECTION_AUTO_FAILOVER=1, failover generated a number of
misleading warnings in the log that implied there were problems when in
fact conditions were those expected for such a failover. These log
messages have been updated accordingly. (Bug #32135376)

Replication: When a transaction failed, as a side effect, extraneous

error messages relating the replication data repositories were written
to the log. Now in such cases, we suppress such error messages, which
are not directly related to the issue of the failed transaction or its
cause. (Bug #19820134)

Replication: Setting binlog_order_commits to OFF could lead to a

missed GTID in the next binary log file's Previous_gtids event.

Our thanks to Yewei Xu and the Tencent team for the contribution.

(Bug #109485, Bug #34930969)

Replication: Corrected the SQL statements suggested in the error

message text for ER_RPL_REPLICA_ERROR_RUNNING_QUERY.

Our thanks to Dan McCombs for the contribution. (Bug #109154, Bug

Replication: A hash scan builds a hash of changes, scans the target

table or index, and applies any matching change for the current entry.
In the build phase, it uses only the before image, and skips any after
image. Problems arose in some cases because generated columns were
computed for the (skipped) after image, leading to replication errors.
This is fixed by not computing generated columns any longer for
seek-only calls such as hash scans.

Our thanks to dc huang for the contribution. (Bug #107366, Bug

Replication: In certain rare cases, it was possible to set

gtid_mode=OFF for one session while another session, after
WAIT_FOR_EXECUTED_GTID_SET() was issued by a user in this second
session, was still waiting for the next GTID set from the first session.
This could result in the second session waiting indefinitely for the
function to return. (Bug #99921, Bug #31505993)

Group Replication: Accessing the Performance Schema

replication_group_communication_information and
replication_group_member_stats tables in parallel sometimes caused
subsequent group replication operations to hang. (Bug #34870181)

Group Replication: In certain cases, the group replication secondary

node unexpectedly shut down while purging the relay log. (Bug #34397106)

Group Replication: When shutting down the Group Replication plugin,

the order in which the associated events were reported the error log
sometimes led to confusion. To remove any doubts, we now make sure that
Plugin group_replication reported: 'Plugin 'group_replication' has been
stopped. is in fact the last log message relating to the shutdown,
written only when all other events associated with shutting down the
plugin have been logged. (Bug #109345, Bug #34887491)

Microsoft Windows: The authentication_fido_client plugin stopped

responding during the authentication process if it was unable to find a
FIDO device on the Windows client host. (Bug #34918044)

In certain cases, CONVERT(utf8mb3_column USING UTF16) was rejected

with the error Cannot convert string '\x--...' from binary to utf16.
(Bug #35129361)

When joining two tables on a string column, and the column from one

of the tables has an additional predicate comparing it with a temporal
literal, constant propagation in some cases incorrectly caused the join
condition to be modified such that it used temporal rather than string
semantics when comparing the strings. This caused incorrect results to
be returned from the join. (Bug #35115909)

Error messages returned after calling the mysql_reset_connection() C

API function in a prepared statement did not identify the function name
properly. (Bug #35107280)

Fixed a regression in a previous fix for an issue with windowing

functions.

Our thanks to Dmitry Lenev for the contribution. (Bug #35061924)

References: This issue is a regression of: Bug #34572136.

When replacing subqueries in transforms, the internal flag showing

whether a given query block contains any subqueries (PROP_SUBQUERY) was
not updated afterwards. (Bug #35060385)

A client setting the character set to an impermissible client

character set (ucs2, utf16, utf16le, or utf32) could cause unexpected
behavior when the client used an authentication plugin. (Bug #35054579)

Changelog:
https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-33.html

Sponsored by: Netzkommune GmbH