![[BACK]](/icons/back.gif){kind=icon}
Up to [cvs.NetBSD.org] / pkgsrc / databases / mysql80-client
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
mysql80-client: fix macOS build (NetBSD still builds).
databases/mysql80-{client|server}: Update to 8.0.39
Changelog:
Changes in MySQL 8.0.39 (2024-07-23, General Availability)
Bugs Fixed
* InnoDB: In some cases, following the creation of a very large number of
tables (8001 or more), the server could not be restarted successfully. (Bug
#36808732)
References: This issue is a regression of: Bug #33398681.
* InnoDB: Improved tablespace file scan performance at startup. (Bug #110402,
Bug #35200385)
* Group Replication: Running a CREATE TABLE ... SELECT statement on a source
coming from an asynchronous channel to Group Replication led to errors on
the replica. (Bug #36784284)
Changes in MySQL 8.0.38 (2024-07-01, General Availability)
Important
This release is no longer available for download. It was removed due to a
critical issue that could stop the server from restarting following the
creation of a very large number of tables (8001, or more). Please upgrade to
MySQL 8.0.39 instead.
* Audit Log Notes
* C API Notes
* Compilation Notes
* Connection Management Notes
* Data Dictionary Notes
* Pluggable Authentication
* Thread Pool Notes
* Bugs Fixed
Audit Log Notes
* Audit log pruning did not function after removing or renaming a file from
the audit log. Now pruning continues in such cases, but with a warning
printed in the error log stating that it was not possible to delete the
missing audit log file. (Bug #35902913)
C API Notes
* C API applications stalled while receiving results for server side prepared
statements.
Compilation Notes
* Upgraded the bundled googletest and googlemock sources to version 1.14.0.
(Bug #36562482)
* Added a missing dependency on GenError. (Bug #36551721)
* It is now possible on Linux systems to build MySQL using a bundled tcmalloc
library that is provided with the source by specifying -DWITH_TCMALLOC=
BUNDLED. This is supported on Linux only. (Bug #36313839)
* The bundled tcmalloc() is now used when building MySQL on Enterprise Linux
8. (Bug #114844, Bug #35674008)
* Linux aarch64 platform binaries are now built using patchelf --page-size=
65536 for compatibility with systems using either 4k or 64k for the page
size. (Bug #114233, Bug #36393794)
Connection Management Notes
* The conn_delay/Waiting in connection_control plugin stage was not reset
after a delay introduced by the connection control plugin which resulted in
incorrect monitoring information. (Bug #35205358)
Data Dictionary Notes
* Attempting to upgrade a MyISAM table containing a mix of regular columns
and generated columns from MySQL 5.7 to 8.0 or later led to table
corruption. (Bug #105301, Bug #33503328)
Pluggable Authentication
* The deprecation warning issued when authenticating with the
mysql_native_password plugin is now issued only once. (Bug #35792948)
Thread Pool Notes
* Connecting to a thread group that had no connection handler threads
stalled. We fix this by making sure that connection handler threads
terminate only if there is at least one connection thread left. (Bug #
36550125)
Bugs Fixed
* InnoDB: MySQL unexpectedly halted on an UPDATE after an ALTER TABLE
operation. (Bug #36571091)
References: This issue is a regression of: Bug #35183686.
* InnoDB: The log index size calculation now accounts for column order
changes. (Bug #36526369)
References: This issue is a regression of: Bug #35183686.
* InnoDB: File system operations performed by InnoDB now consistently fsync
the parent directory when performing directory altering tasks. (Bug #
36174938)
* InnoDB: In debug builds, setting the innodb_interpreter_output debug
variable would cause the server to unexpectedly halt. This is now a
read-only variable. (Bug #36041032)
* InnoDB: For tables created with an index on a column that was too wide for
the redundant row format (allowed before MySQL 5.7.35), an in-place upgrade
silently imported the table but it was not accessible, which interfered
with making backups. Now all operations that involve using the invalid
index are rejected with ER_INDEX_CORRUPT until the index is dropped. An
ER_IB_INDEX_PART_TOO_LONG error is also reported in the error log. (Bug #
35869747)
References: See also: Bug #34826861.
* InnoDB: An InnoDB assertion error referencing an invalid column index was
triggered when the column index was valid. (Bug #34800754)
* InnoDB: With an empty XA transaction, shutting the server down after an XA
START would cause the server to halt unexpectedly. (Bug #32416819)
* InnoDB: Shutting down the replication applier or binlog applier while
processing an empty XA transaction caused the system to unexpectedly halt.
(Bug #32416819)
* InnoDB: Removed unnecessary heap usage in the Validate_files::check()
function.
Our thanks to Huaxiong Song for the contribution. (Bug #115041, Bug #
36626203)
* InnoDB: If a partition table was read with innodb_parallel_read_threads=1,
read performance greatly decreased from any table after 256 reads. InnoDB
behaved as if it reached the maximum capacity of parallel read threads
despite not using any.
Our thanks to Ke Yu for the contribution. (Bug #114154, Bug #36347408)
* InnoDB: The result from a spatial index containing a column with a spatial
reference identifier (SRID) attribute was empty. In addition, using FORCE
INDEX to force a covering index scan on a spatial index led to an
assertion. (Bug #112676, Bug #114200, Bug #35894664, Bug #36361834)
* InnoDB: Fixed performance issues related to querying the data_lock and
data_lock_waits tables when thousands of read-only transactions were
present. (Bug #109539, Bug #34951273)
* Replication: If a source contained a stored, generated column populated by
a JSON function and binlog_row_image was set to MINIMAL, any subsequent
update or deletion on the underlying column failed with the following
error:
Invalid JSON text in argument 1 to function json_extract: 'The document is empty.'
The replica attempted to re-evaluate the generated column and failed with
that error because the underlying column was unavailable. As of this
release, stored, generated columns are not re-evaluated when the underlying
columns are unavailable. (Bug #36515172)
* Replication: When running GTID-based replication with relay_log_space_limit
enabled, a restart of the auto positioning protocol sometimes resulted in
an infinite loop, leading to a deadlock in replication. This was because
relay_log_space_limit was not honoured, not only for transactions whose
size exceed this limit, but when the replica could not purge previous logs
as well.
To fix this issue, we make the following changes:
o The receiver respects relay_log_space_limit as set by the user, unless
a transaction received by the receiver cannot fit into the purged relay
log. Before queueing the received transaction, receiver now checks
whether scheduling a full transaction is possible. If not, the receiver
performs the following actions:
# Sets the flag indicating that receiver is waiting
# Rotates the relay log
# Waits until it is notified that relay log purge was executed and
that the applier has purged all available relay logs; after this,
the receiver may queue a transaction without checking the limit
again
o Before moving to the next file, the coordinator checks whether the
receiver is waiting for available relay log space. If so, the
coordinator forcibly purges the applied logs, including the current
relay log file. To purge the current relay log file safely, the
coordinator must do the following:
# Synchronize all of its workers before moving to the next file
# Forcibly update group positions, which is necessary to allow
current purging of the relay log
# Update the variable read by the receiver which contains relay log
filename to which applier was moved
These operations are allowed because we know that receiver waits at a
transaction boundary and rotates the relay log before waiting.
(Bug #36507020)
* Replication: Worker jobs now contain information about the relay log file
which initiated the transaction, instead of using the default defined by
relay_log. (Bug #36395631)
* Replication: Handling an incident while transactions were being committed
to the binary log caused MySQL to wait indefinitely. (Bug #35671897)
* Group Replication: Removed a memory leak from /xcom/gcs_xcom_networking.cc.
(Bug #36532199)
* Group Replication: Under certain circumstances, if a primary's host
experienced network inactivity of 20 seconds or more, the secondaries could
stop unexpectedly. (Bug #36306144)
* Group Replication: Under certain circumstances, if garbage collection
occurred just before a relay log rotation, it could cause the applier to
stop applying new transactions on the secondary members.
This was caused by garbage collection incrementing the relay log's
last_committed and sequence_number, creating a gap in the recorded
sequence_number after the log rotation. The applier was unaffected if the
gap occurred anywhere else in the relay log.
As of this release, only last_committed is updated during garbage
collection. (Bug #36280130, Bug #36446250)
* JSON: Added missing checks for error handling to NULLIF(), COALESCE(), and
the shift (>>) operator. (Bug #113668, Bug #35513196, Bug #36198403)
References: See also: Bug #31358416.
* MySQL NDB ClusterJ: Running the ClusterJ test suite resulted in an error
message saying a number of threads did not exist. That was due to some
wrong handling of threads and connections, which was corrected by this
patch. (Bug #36086735)
* Averages of certain numbers were not always computed correctly. (Bug #
36563773)
* The following files in strings contained incorrect license information:
o mb_wc.h
o ctype-uca.cc
o ctype-ucs2.cc
o ctype-utf8.cc
o dtoa.cc
o strxmov.cc
o strxnmov.cc
(Bug #36506181)
* In certain unusual cases, the UpdateXML() function did not process all of
its arguments correctly. (Bug #36479091)
* Explaining a query which used FORCE INDEX on a spatial index containing a
column with SRID attributes led to an unplanned exit. (Bug #36418426)
* When incrementing the reference count for an expression, underlying
expressions within this expression are not looked at. While removing an
expression, after decrementing the reference count, even the underlying
expressions were examined, which led to unintentional deletion of the
underlying expressions. This issue manifested in Item_ref::real_item() as
well as in an assert in sql/item.h. We fix this by not looking at the
underlying expression unless the current expression contains the only
remaining reference. (Bug #36204344, Bug #36356279)
* Under certain conditions, EXPLAIN FORMAT=JSON FOR CONNECTION sometimes led
to an unplanned exit. (Bug #36189820)
* Under certain conditions, a race condition could result in the amount of
RAM used by TABLE_HANDLES increasing to a maximum of 9GB. (Bug #36170903)
* Some CREATE USER statements were not handled correctly. (Bug #36022885)
* For a SELECT with ORDER BY and LIMIT, the optimizer first chose a full
table scan with a very expensive cost, then performed another check and
used the perform_order_index type of path, but this was not reflected by
the cost in the optimizer plan. (Bug #35930969)
* Client connections were not alway terminated correctly during shutdown.
(Bug #35854919)
* All internal ACL bitmask variables are now explicitly 32 bits (uint32_t).
(Bug #35507223)
* It was not possible to add a functional index on FIND_IN_SET(). (Bug #
35352161)
* Running two concurrent OPTIMIZE TABLE statements on the same table with
fulltext indexes and innodb_optimize_fulltext_only enabled sometimes caused
the server to exit. (Bug #34929814)
* Removed a memory leak observed while running authentication_kerberos under
Valgrind. (Bug #34482788, Bug #36570929)
* The gen_range() function as implemented by the (deprecated) data masking
plugin did not always return the correct result.
This issue affected the data masking plugin only, and did not affect the
data masking component which supersedes it. (Bug #34163992)
* Fixed an erroneous comment in include/my_command.h.
Our thanks to Sho Nakazono for the contribution. (Bug #114507, Bug #
36455468)
* It was possible for a deterministic stored function to return an incorrect
result when the function used JOIN ON inside the return statement. If the
query needed to be reprepared due to a table metadata caused by, for
example, FLUSH TABLES between two executions, the ON clause was sometimes
lost. (Bug #114235, Bug #36379879)
* The PROCESSLIST_INFO column of THREADS was not updated when executing a
prepared statement.
Thanks to Daniel Lenski and Amazon for the contribution. (Bug #104121, Bug
#33057164)
Changes in MySQL 8.0.37 (2024-04-30, General Availability)
* Audit Log Notes
* Character Set Support
* Compilation Notes
* Component Notes
* Optimizer Notes
* Performance Schema Notes
* Functionality Added or Changed
* Bugs Fixed
Audit Log Notes
* MySQL now calls plugin->deinit() with a valid plugin struct as an argument
regardless of the plugin's type.
Our thanks to Martin Alderete for the contribution.
Character Set Support
* When the character_set_server system variable was set using SET PERSIST or
SET GLOBAL, it did not take effect for new client sessions or for a client
establishing a connection to the server after the server was restarted. The
only workaround was to set the corresponding command-line option when
starting the server.
To fix this, we now make sure that, at the time of server restart, the
configuration data is read in the correct order so that the variable
setting takes effect as expected. (Bug #35529604)
Compilation Notes
* Warnings for unused variables are turned into compilation errors when
compiling with -DMYSQL_MAINTAINER_MODE=1. To avoid this use
-DMYSQL_MAINTAINER_MODE=0 to disable such errors. (Bug #113662, Bug #
36198423)
* Improved the cycle timer for the s390x architecture.
Our thanks to Jonathan Albrecht for the contribution. (Bug #112845, Bug #
35949958)
Component Notes
* The values for component options set using the --loose prefix were not read
when the component was installed. (Bug #28341329)
Optimizer Notes
* The multi-range read (MRR) optimization did not perform as well as in
previous releases. (Bug #113711, Bug #36220640)
Performance Schema Notes
* User variables assigned decimal values were rounded up in the
user_variables_by_thread table. (Bug #35781732)
* Executing SELECT * from performance_schema.data_locks on a server under
heavy load could cause MySQL to consume too much memory and close
unexpectedly.
As of this release, memory used executing such a query is now instrumented
with memory/performance_schema/data_container, enabling you to observe
memory consumption. (Bug #35240825)
* Executing SELECT * from performance_schema.data_locks on a server under
heavy load could cause a deadlock in InnoDB. (Bug #35068461)
References: See also: Bug #35240825.
Functionality Added or Changed
* Important Change; Group Replication: When issued with
group_replication_consistency set to BEFORE_ON_PRIMARY_FAILOVER, the MySQL
KILL statement now ignores any consistency guarantees, with any interrupted
transactions now being rolled back.
* Important Change: For platforms on which OpenSSL libraries are bundled, the
linked OpenSSL library for MySQL Server has been updated to version 3.0.13.
Issues fixed in OpenSSL version 3.0.13 are described at https://
www.openssl.org/news/cl30.txt. (Bug #36261675)
* Packaging: Added support for Fedora 40 and Ubuntu 24.04.
* Microsoft Windows: MySQL Windows binary files (.exe and .dll files) now
display additional information when their properties are viewed. (Bug #
36379291)
* clone plugin version requirements were relaxed to allow cloning between
different point releases in the same series. In other words, only the major
and minor version numbers must match when previously the release number
also had to match.
For example, cloning of MySQL 8.0.37 to (a future) MySQL 8.0.42, or the
reverse, is supported. Previous restrictions still apply to versions older
than 8.0.37, for example, so cloning of MySQL 8.0.36 to any other MySQL
release (or from a different MySQL release to 8.0.36) remains unsupported.
(Bug #36293529, WL #15989)
Bugs Fixed
* Important Change: The Robin Hood hashing library has been replaced with
unordered_dense. (Bug #36158022)
* InnoDB; Microsoft Windows: Improved redo log performance on Windows by
opening redo log files in overlapped mode. (Bug #36154818)
References: This issue is a regression of: Bug #12527.
* InnoDB: The log writer calls functions that temporarily release
log.writer_mutex; when innodb_log_writer_threads=OFF, this potentially led
to other threads writing to the redo log in between these times. (Bug #
36425219)
* InnoDB: Some FTS operations on tables with FTS indexes led to inconsistent
results. For example, if the server terminated while synchronizing the FTS
cache or when synchronization occurred concurrently with another FTS
operation.
Our thanks to Yin Peng and the Tencent team for the contribution. (Bug #
36347647)
* InnoDB: When creating an index on a table containing data, valgrind
occasionally reported reads of uninitialized memory from
ddl::Builder::bulk_add_row(). (Bug #36342792)
* InnoDB: On Windows, keeping a file open without a shared write lock and
attempting to acquire the fil_shard mutex caused a deadlock with another
thread that had acquired the fil_shard mutex and was attempting to access
the same file. (Bug #36159317)
References: See also: Bug #32808809.
* InnoDB: Fixed a potential redo log rotation issue that could emit a "Found
existing redo log files, but at least one is missing" error during
recovery. (Bug #36124625)
* InnoDB: Improved os_innodb_umask handling, and made it read-only. (Bug #
35932118)
References: This issue is a regression of: Bug #29472125.
* InnoDB: Found and fixed an assertion failure related to full-text indexes.
(Bug #35836581)
* InnoDB: Improved buffer handling during the tablespace deletion process, a
situation that could have potentially caused an assertion failure. (Bug #
35676106, Bug #36343647)
* InnoDB: If a MySQL table in a system schema had an INSTANT ADD column that
was added before 8.0.29 (they are not allowed as of that version), and
after MySQL was upgraded to a version greater than 8.0.29, DMLs on these
tables would result in the server unexpectedly closing.
Our thanks to Richard Dang for the contribution. (Bug #35625510, Bug #
35981565, Bug #36180360)
* InnoDB: The redo log would potentially not log a column order change with
instant DDL, which could cause an incorrect log replay during recovery.
(Bug #35183686)
* InnoDB: Results for SHOW ENGINE INNODB STATUS showed an invalid value
(NULL) as the first result. (Bug #113819, Bug #36118112)
References: This issue is a regression of: Bug #34992157.
* InnoDB: With innodb_parallel_read_threads set to a value greater than 1,
InnoDB unnecessarily disabled read-ahead heuristics which resulted in
stalls when pages were not already in the buffer pool. (Bug #113482, Bug #
36142806)
* InnoDB: Running a query that used a unique hash index with the TempTable
storage engine could take significantly more time compared to running the
query with the MEMORY engine.
Our thanks to xiaoyang chen for the contribution. (Bug #113178, Bug #
36037224, Bug #36224958)
* InnoDB: In debug builds, there was an assertion failure in InnoDB's
background when a transaction it wanted to acquire an MDL lock on was no
longer active.
This fix is based on a patch from Genze Wu with Alibaba, thank you for the
contribution. (Bug #112424, Bug #35835864)
References: This issue is a regression of: Bug #33700835.
* InnoDB: With innodb_parallel_read_threads set to a value greater than 1,
InnoDB would unnecessarily request asynchronous reads which required more
synchronization during I/O completion and created a bottleneck due to the
limited number of available threads (innodb_read_io_threads) for handling I
/O operations. Now this performs synchronous instead of asynchronous reads.
(Bug #112137, Bug #35740866)
* InnoDB: A trx would unexpectedly halt after encountering an incorrect trx->
in_innodb value.
Our thanks to Shaohua Wang for the contribution. (Bug #110652, Bug #
35277407)
* InnoDB: SELECT ... GROUP BY queries were at least twice as slow with the
TempTable engine than the Memory engine. (Bug #107700, Bug #34338001)
* InnoDB: MySQL no longer ignores the optimizer hint to use a secondary index
scan, which instead forced a clustered (parallel) index scan. (Bug #100597,
Bug #112767, Bug #31791868, Bug #35952353)
* Group Replication: Problems arose when members M1 and M2 were in a group,
with M1 using u1 as its recovery user and M2 using u2 as its own recovery
user, and both users u1 and u2 existing on M1 and M2 with all necessary
privileges, and when a new member M3 joined the group using u2 as its
recovery user. M3 knew only of user u2, but did not know of user u1,
leading START GROUP REPLICATION on M2 to be rejected since M1 was unable to
connect to M2. This also generated a new view_id listing the group members
as M1 and M2, but M1 nevertheless continued trying to connect to M3, with
M1 logging Error in establishing mysql connection and M3 logging Access
denied errors for the connection attempts from M1.
By design, XCom stores the last three known configurations, including
references to physical connections shared among all past and present
configurations. This is done to facilitate quick reconnections by nodes
rejoining the group, explicitly or implicitly, and that were already
present in any of those configurations.
A side effect of this was that we might keep attempting to connect to a
node that was currently not in the group. To solve this problem, we inhibit
error logging if the node is not in the current configuration, in order to
avoid false negatives which might lead a DBA or an operator to think
mistakenly that there is a problem in the system. (Bug #36210988)
References: See also: Bug #32592027.
* Group Replication: Improved handling of GTID sets. (Bug #36093405)
* Group Replication: Two cases were found in which a member exited the group
and moved to the ERROR state, but did not honor the action specified by
group_replication_exit_state_action; these are listed here:
o When an error occurred while enabling super_read_only
o When member join recovery was not possible, due to missing binary logs
and clone groups on group members
Example: When the value of group_replication_exit_state_action was
OFFLINE_MODE and one of these events took place, offline mode was not
enabled as expected. (Bug #36076308)
* Group Replication: After successfully setting a new primary,
group_replication_set_as_primary() in some cases waited indefinitely for
the operation to complete. (Bug #36059098)
* JSON: JOIN and GROUP BY handled some JSON column values differently. (Bug #
101048, Bug #31969607)
* MySQL NDB ClusterJ: The setLimits() method can now be chained to
deletePersistentAll() to limit the number of items to delete. See the
description of deletePersistentAll() for details. (Bug #36049906)
* Updated BuildRequire rules to align with versions now required for CMake
and Bison. (Bug #36343254)
* SET GLOBAL offline_mode=ON did not always perform correctly when issued
under high loads. (Bug #36275182)
References: See also: Bug #36405894.
* Upgraded curl to version 8.6.0. (Bug #36267545)
* mysqldump did not always interpret the server version correctly. (Bug #
36248967)
References: See also: Bug #36405879.
* Condition pushdown to a view was rejected with a collation mismatch if the
view was created with a different character set than the character set used
when querying the view. (Bug #36246859)
* Use of the deprecated exec_program() command has been replaced by
execute_process() to provide compatibility with CMake 3.28.1 and later.
(Bug #36220656)
* Upgraded the protobuf library to version 25.1. (Bug #36108397)
* For building Enterprise Linux RPMs, the build scripts now point to a newer
strip command (under /opt/rh/gcc-toolset-12), and they now check that the
corresponding dwz tool is available. Previously this was only implemented
for EL8. (Bug #36090069)
* We now look for gcc-ar and gcc-ranlib when building on Oracle Linux with
link-time optimization. (Bug #36089900)
* The server sometimes terminated unexpectedly in response to a specific
query. (Bug #35957627)
* Improved view and trigger definer handling by view and table DDL. (Bug #
35942937)
* The server did not always return metadata to the client correctly for
certain queries. (Bug #35904044)
* When running queries against a table with a multi-value index, the server
sometimes exited unexpectedly, often while executing a complex SELECT query
which used this index. (Bug #35789759)
* Improved code in sql/item_subselect.cc. (Bug #35733778, Bug #35738531, Bug
#35779012)
* CREATE USER IF EXISTS was not always logged correctly. (Bug #35530823)
* The server did not disallow subqueries in partition expressions properly.
These are invalid, and should cause a syntax error. (Bug #35476172)
* Some RANK() ... OVER() queries raised an assertion in sql/sql_executor.cc.
(Bug #35228083)
* When successive ALTER TABLE ... ALGORITHM=COPY statements were issued
within 10 seconds of one another, the n_rows value became 0. (Bug #
35127747)
* Updated the URL used for downloading the Boost C++ libraries. (Bug #113576,
Bug #36164514)
* The fix for a previous issue, first addressed in MySQL 8.0.30, was
incomplete.
Our thanks to Hao Lu for the contribution. (Bug #113174, Bug #36035044)
References: This issue is a regression of: Bug #110801, Bug #35328028.
* On s390x, we now compile the FMA test with -O2 to avoid overoptimization.
Our thanks to Jonathan Albrecht for the contribution. (Bug #113096, Bug #
36016140)
* Although s390x is a big-endian platform, the little-endian ICU data
directory was used for compiling.
Our thanks to Jonathan Albrecht for the contribution. (Bug #113095, Bug #
36016141)
* Incorrect results were sometimes obtained from a query that used a group by
loose index scan. (Bug #112541, Bug #35854362)
* An assertion failed in debug builds when inserting data with a zero-length
column, such as CHAR(0) or BINARY(0), into a table. Now, a less strict
assertion more accurately fails only if it detects that a non-zero number
of bytes copied from a source is identical to the target. (Bug #111450, Bug
#35507763)
* A VALUES statement in a correlated lateral or (other) dependent subquery
yielded an incorrect result. (Bug #109252, Bug #110076, Bug #34852090, Bug
#35087820)
* IN should return NULL not only if the expression on the left hand side is
NULL, but when no match is found in the list and one of the expressions in
the list is NULL as well. In some cases, it was found that adding rows to a
table caused a subsequent prepared SELECT NULL IN (SELECT ...) query to
return a different result when the result should have remained the same.
(Bug #94857, Bug #29602835)
mysql80: updated to 8.0.36 Changes in MySQL 8.0.36 Audit Log Notes In some cases, calling audit_log_read( audit_log_read_bookmark() ) led to an Out of memory error. Compilation Notes Microsoft Windows: MySQL did not compile correctly using Visual Studio 2022. Improved the -DWITH_ZLIB=system check. For compiling on Linux, changed the no-error=deprecated-declarations flag to no-deprecated-declarations for the OpenSSL 3 library. Our thanks to karry zhang for the contribution. Optimizer Notes The hashing algorithm employed yielded poor performance when using a HASH field to check for uniqueness. Packaging Notes Important Change: The GnuPG build key (A8D3785C) used to sign MySQL downloadable packages has been updated. The previous GnuPG build key (3A79BD29) expired on 2023-12-14. For information about verifying the integrity and authenticity of MySQL downloadable packages using GnuPG signature checking, or to obtain a copy of our public GnuPG build key, see Signature Checking Using GnuPG. Due to the GnuPG key update, systems configured to use repo.mysql.com may report a signature verification error when upgrading to MySQL 8.0.36 and higher or to MySQL 8.3.0 and higher using apt or yum. Use one of the following methods to resolve this issue: Manually reinstall the MySQL APT or YUM repository setup package from https://dev.mysql.com/downloads/. Download the MySQL GnuPG public key and add it your system GPG keyring. Performance Schema Notes When executing a stored program, the Performance Schema instrumentation caused some unnecessary overhead. As of this release, all stored procedure micro instructions (statement/sp/%), except statement/sp/stmt, are disabled by default. The performance of the Performance Schema statement instrumentation has been improved. Specifically, collecting MESSAGE_TEXT data is now more efficient. Pluggable Authentication Beginning with this release, the behavior of the AUTHENTICATION_PAM_LOG environment variable used in debugging the PAM authentication plugin is changed as follows: Setting AUTHENTICATION_PAM_LOG to an arbitrary value (except as noted in the next item) no longer includes passwords in its diagnostic messages. To include passwords in the diagnostic messages, set AUTHENTICATION_PAM_LOG=PAM_LOG_WITH_SECRET_INFO. For more information, see PAM Authentication Debugging. Functionality Added or Changed Important Change: For platforms on which OpenSSL libraries are bundled, the linked OpenSSL library for MySQL Server has been updated to version 3.0.12. Issues fixed in OpenSSL version 3.0.12 are described at https://www.openssl.org/news/cl30.txt. Bugs Fixed InnoDB: The hash function used by the adaptive hash index (AHI) was improved to increase performance. InnoDB: If change buffer entries are present during startup, a disabled innodb_validate_tablespace_paths option will no longer be enforced and instead the MySQL server will proceed to validate all tablespaces. Otherwise, secondary indexes could end up corrupted. InnoDB: During concurrent DDL and DML operations, DDL could fail if the online log grew too large. Buffer handling was improved to prevent this issue. Replication: An issue with calculating the current number of bytes used for Log_event events in Performance Schema memory instrumentation made it appear as though the sql/replica_sql thread on the replica grew endlessly and never decreased in size. Replication: Stopping replication while replicating CREATE TABLE AS SELECT caused the server to exit. Group Replication: A forced START GROUP_REPLICATION while a replication channel was in an error state could lead to an unplanned server exit. For building Enterprise Linux 8 RPMs, the build scripts now point to a newer strip command (under /opt/rh/gcc-toolset-12), and they now check that the corresponding dwz tool is available. In some cases, calling a loadable function installed by an improperly initialized plugin caused an unplanned shutdown. Found and fixed an assertion failure at handler::ha_index_end() in handler.cc. When the MYSQL_FIREWALL plugin was configured to use a custom schema, but failed to initialize properly during the server startup, subsequent errors and failures could occur. Some nested queries with GROUP BY were not handled correctly. References: This issue is a regression of: In limited cases, passing data to the MD5() encryption function could halt the server. Some subselects from views were not always handled correctly. While performing an operation such as the bulk renaming of many tables, simultaneously executing a data definition statement similar to CREATE TABLE ... SELECT could stop the server unexpectedly. UPDATE HISTOGRAM did not behave as expected in all cases. UPDATE HISTOGRAM did not behave as expected in all cases. EXPLAIN ANALYZE did not always produce the expected result. An error occurred during subquery resolution. References: This issue is a regression of: Refreshing of used table information is now postponed to the start of the next execution, just after tables have been opened, and we know that all table objects are in a proper state. Some HAVING queries did not produce expected results. Some recursive CTEs did not function as expected. Some queries using OVER (PARTITION ...) were not always executed successfully. Some subqueries with ROLLUP were not always handled correctly. Removed the CPACK_COMPONENT_GROUP_INFO_DISPLAY_NAME configuration option from the Windows installation MSI interface. Now the INFO_BIN and INFO_SRC files are always installed. Some queries using windowing functions were not always handled correctly. In debug builds, a case-altered column name could cause the server to exit. MySQL Server installation packages contained two copies of the INFO_SRC file. A SELECT statement within a prepared statement unexpectedly returned different results on successive executions. References: This issue is a regression of: Some SELECT DISTINCT queries were not always handled correctly. Removed an assertion failure in sql/field.cc. Sme queries having the form SELECT AVG(...) OVER (PARTITION BY ...) were not always handled correctly. Upgrading MySQL using an official MySQL Yum or SUSE repository always enables the MySQL service. Now it enables the service only after installing, and preserves (and does not edit) the existing value while upgrading. For a query with a derived condition pushdown where a column in the condition needs to be replaced, a matching item could not found, even when known to be present, when the replacement item was wrapped in a ROLLUP while the matching item was not. References: This issue is a regression of: Performing an arithmetic operation on the result over a window function in a stored procedure gave the correct result the first time the procedure was executed, but returned an incorrect result on all subsequent invocations. References: See also: MySQL did not build correctly using the musl version of libc. Our thanks to Sam James for the contribution. In some cases, selecting from a view leaked a small amount of memory.
mysql-client: fix zlib library name in pkg-config file Bump PKGREVISION.
mysql80*: SunOS build and install fixes.
mysql80: updated to 8.0.33
8.0.33
Functionality Added or Changed
Important Change: For platforms on which OpenSSL libraries are bundled, the linked OpenSSL library for MySQL Server has been updated to version 1.1.1t. Issues fixed in OpenSSL version 1.1.1t are described at https://www.openssl.org/news/cl111.txt.
Replication: As part of ongoing work to change old terminology used in MySQL products, the terms “master”, “slave”, and “MTS” have been replaced in error messages relating to MySQL Replication by “source”, “replica”, and “MTA”, respectively. This includes all error messages listed in messages_to_clients.txt and messages_to_error_log.txt relating to replication; the present task does not perform this replacement for messages used in other contexts.
See the MySQL 8.0 Error Message Reference, for more information.
Replication: mysqlbinlog --start-position now accepts values up to 18446744073709551615, unless the --read-from-remote-server or --read-from-remote-source option is also used, in which case the maximum is 4294967295.
Binary packages that include curl rather than linking to the system curl library have been upgraded to use curl 7.88.1.
The use of a generated column with DEFAULT(col_name) to specify the default value for a named column is not permitted and now emits an error message.
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.
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.
InnoDB: Dead code removal.
InnoDB: Error messages related to innodb_doublewrite moved to the error log.
InnoDB: Prevent online DDL operations from accessing out-of-bounds memory.
InnoDB: ALTER TABLE ... AUTO_INCREMENT could be set to less than MAX + 1 and not forced to MAX + 1.
InnoDB: Innodb_data_pending_fsyncs could show extremely high inaccurate values because of a variable overflow.
Partitioning: Some IN() queries on partitioned tables were not always handled correctly.
Partitioning: Queries using the INDEX_MERGE optimizer hint was not handled correctly in all cases.
Replication: XA transactions whose XIDs contained null bytes could not be recovered.
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.
Replication: The binary log recovery process did not report all possible error states.
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.
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.
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.
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.
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.
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.
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.
Group Replication: In certain cases, the group replication secondary node unexpectedly shut down while purging the relay log.
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.
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.
In certain cases, CONVERT(utf8mb3_column USING UTF16) was rejected with the error Cannot convert string '\x--...' from binary to utf16.
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.
Error messages returned after calling the mysql_reset_connection() C API function in a prepared statement did not identify the function name properly.
Fixed a regression in a previous fix for an issue with windowing functions.
Our thanks to Dmitry Lenev for the contribution.
When replacing subqueries in transforms, the internal flag showing whether a given query block contains any subqueries (PROP_SUBQUERY) was not updated afterwards.
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.
EXPLAIN ANALYZE displayed 0 when the average number of rows was less than 1. To fix this, we now format numbers in the output of EXPLAIN ANALYZE and EXPLAIN FORMAT=TREE such that numbers in the range 0.001-999999.5 are printed as decimal numbers, and numbers outside this range are printed using engineering notation (for example: 1.23e+9, 934e-6). In addition, trailing zeroes are no longer printed, and numbers less than 1e-12 are printed as 0.
This helps ensure consistent precision regardless of the number's value and improve readability, while producing minimal rounding errors.
The NTILE() function did not work correctly in all cases.
Some joins on views did not perform correctly.
Transforming a correlated scalar subquery to a derived table led to a wrong result for InnoDB tables when the subquery included duplicate predicates. An example of a query which could be affected by this issue is shown here:
SELECT * FROM t1
WHERE (
SELECT t2.a FROM t2
WHERE t2.a = t1.a AND t2.a = t1.a
) > 0;
Fixed an assert in sql/item_strfunc.cc that could potentially lead to issues with the SPACE() function.
Using ROW_COUNT() as the length argument to LPAD() or RPAD() did not perform as expected.
A query with a window function having an expression with a CASE function in its ORDER BY clause could lead to a server exit.
The fix for a previous issue introduced an assertion in debug builds when optimizing a HAVING clause.
When using mysqld_multi, the system that obscures "--password" usage as "--password=*****" would also match "--password-history" and "--password-require-current" definitions as "--password", but now explicitly checks for "--password=" instead.
In some cases, calling the mysql_bind_param() C API function could cause the server to become unresponsive.
The authentication_oci_client plugin was unable to open a valid configuration file if any of its entries contained an equals sign character separated by spaces (for example, key_file = /home/user/.oci/oci_api_key.pem). Now, both 'key=value' and 'key = value' entry formats are supported.
Incorrect results were returned when the result of an INTERSECT or EXCEPT operation was joined with another table. This issue affected these operations in such cases when used with either DISTINCT or ALL.
When preparing a view query, the operation used the system character set (instead of the character set stored in data dictionary) and then reported an invalid character-string error.
Prepared statements that operate on derived tables, including views, could stop unexpectedly due to problems with the code for reopening tables after an error.
Removed an assertion raised in certain cases by the RANDOM_BYTES() function in debug builds.
There was an issue in how persisted variables were set on startup, causing certain variables not to get properly set to their persisted value.
The MAKETIME() function did not perform correctly in all cases.
Some functions with multiple arguments did not produce the expected results.
A table reference in an ORDER BY outside the parenthesized query block in which the table was used, and which query block had no LIMIT or ORDER BY of its own, raised an error.
A left join with an impossible condition as part of an ON clause was not optimized as in MySQL 5.7, so that in MySQL 8.0, the query executed more quickly without the impossible condition than with it. An example of such a query, impossible condition included, is SELECT * FROM t1 JOIN t2 ON t1.c1=t2.c1 AND 1=2.
When a user defined function was part of a derived table that was merged into the outer query block, or was part of a subquery converted to a semi-join, knowledge of whether this UDF was deterministic (or not) was lost during processing.
With JSON logging enabled and an event subclass specified in the audit log filter definition, an empty item ("" : { }) was appended to the end of the logged event.
Some subqueries did not execute properly.
After the asymmetric_encrypt() component function in a SELECT query encountered a NULL field to decrypt, it could return NULL values for other non-NULL encrypted fields.
The server did not always shut down cleanly after uninstalling the audit log plugin.
Certain antijoins were not handled correctly by the server.
When the MySQL 5.7 Optimizer has 2 choices for an index to filter rows, one primary and one secondary, it picks a range scan on the secondary index because the range scan uses more key parts. MySQL 8.0 did not use this logic, instead choosing the primary index to filter rows with WHERE clause filtering. Primary key use is not suitable in such cases due to the presence of LIMIT, and due to the nature of data distribution. The secondary index was not considered while resolving order by due to constant elimination. This resulted in much different query plans in MySQL 5.7 and MySQL 8.0 for the same query.
We solve this issue in MySQL 8.0 by skipping the constant key parts of the index during order-by evaluation only if the query is constant-optimized, which can be done at this time, but not during LIMIT analysis.
The MySQL data dictionary caches failed lookups of se_private_id values (IDs which are not found), which speeds up execution of code specific to InnoDB, relying on the fact that InnoDB does not reuse these IDs. This assumption does not necessarily hold for other storage engines, most notably NDB, where this problem was resolved previously by not using this cache.
We extend the previous fix made for NDB so that the cache lookup is now employed only when the table uses the InnoDB storage engine.
Unexpected results were seen in some queries using DENSE_RANK(), possibly with the addition of WITH ROLLUP.
Fixed an assert raised in sql/sql_tmp_table.cc following work done previously to reimplement ROLLUP processing.
Some CTEs that did not use any tables were not always handled correctly.
Accessing rows from a window frame of a window function call present only in the query's ORDER BY list raised an error.
PERCENT_RANK() used with ORDER BY column did not return the correct result.
The --exclude-tables and --include-tables mysqlpump options did not handle views.
Changed the MySQL systemd service unit configuration from After=network-online.target to Wants=network-online.target to ensure that all configured network devices are available and have an IP address assigned before the service is started.
AVG(...) OVER (ROWS BETWEEN 1 FOLLOWING AND UNBOUNDED FOLLOWING) did not return the correct result.
A query of the form SELECT 1 FROM t1 WHERE NOT EXISTS (VALUES ROW(1), ROW(2)) caused an assert in debug builds when the subquery_to_derived optimizer switch was enabled.
mysqlimport did not escape reserved word table names when used with the --delete option.
When cloning a condition to push down to a derived table, characters in strings representing conditions were converted to utfmb4 correctly only for values less than 128 (the ASCII subset), and code points outside the ASCII subset were converted to invalid characters, causing the resulting character strings to become invalid. For derived tables without UNION, this led to problems when a column name from the derived table used characters outside the ASCII subset, and was used in the WHERE condition. For derived tables with UNION, it created problems when a character outside the ASCII subset was present in a WHERE condition.
We fix these issues by initializing the string used for representing the condition in such cases to the connection character set.
Using --single-transaction with mysqldump version 8.0.32 required either the RELOAD or FLUSH_TABLES privilege. This requirement now applies only when both gtid_mode=ON (default OFF) and with --set-gtid-purged = ON|AUTO (default AUTO).
Fixed a number of issues present in the internal documentation for the scramble generator algorithm in sha256_scramble_generator.cc and sha2_password_common.cc.
Our thanks to Niklas Keller for the contribution.
CREATE USER IF NOT EXISTS added a password history entry even when the user already existed and the password was not updated. This caused a subsequent ALTER USER statement to be rejected.
Many joins using eq_ref access did not perform as well as in previous versions. This issue was first reported in MySQL 8.0.29.
A hash outer join sometimes incorrectly matched NULL with a decimal zero or an empty string that used a non-padding collation, leading to erroneous results.
An object used internally by ALTER INSTANCE RELOAD TLS was not freed until the number of readers reached 0, under the assumption is that the number of readers should reach 0 fairly frequently. The read lock held during an SSL handshake is generally an expensive operation, with network calls, so when roundtrips between the client and the server took excessively long, the lock was held for a relatively long amount of time. This meant that, when changing the value of this object and there were a sufficient number of incoming SSL connections being made, the number of readers might not reach 0 in a reasonable length of time, leaving the thread holding the lock using 100% of the CPU until the lock was released.
We fix this by adding a wait after setting the pointer to this object to a new value, but before releasing the old object.
Our thanks to Sinisa Milivojevic for the contribution.
If mysqldump or mysqlpump could not convert a field's default value to UTF-8 (for instance, if the field was of type BINARY and the default value did not coincide with valid UTF-8), the operation produced results that were not valid to import. Further, using the --hex-blob option did not resolve the issue. We now convert the default value to the system character set. If this fails, the server sends the value as hexadecimal instead to make it more human-readable.
A connection using the C API (libmysqlclient) client library could fail with the FUTURE crypto policy.
While cloning a temporary table for a common table expression which used shared materialization, the cloned temp table was not marked as using hash deduplication, leading to wrong results. We now set the hash field for the cloned temporary table correctly, and update the hidden field count to take this into account.
CREATE EVENT and ALTER EVENT assumed that all values passed to them (other than in a DO clause) resolved as scalars without actually checking the values. This led to assertions when any such values actually rows.
We now perform an explicit check for the number of columns when resolving such items, and report an error when one produces a row and not a scalar value.
A view reference whose underlying field is a constant is not marked as constant when the reference is part of an inner table of an outer join. It was found that, when pushing a condition down to a derived table, the reference was stripped off and only the underlying field was cloned, which made it a constant, and led to wrong results.
To fix this problem, we ensure that we do not push such a condition down to the derived table by adding a check to see first whether the table used by the condition matches the derived table or is a constant expression; only when it is one or the other of these do we actually push the condition down.
mysql80: Build fix for NetBSD 9
mysql80-client: Fix a Linuxism.
mysql80: Update to 8.0.31. Includes a number of pkgsrc cleanups, removing nonsense that has been cargo-culted since the MySQL 3.23.x days(!). Stop shipping mysql-test, it's absolutely huge and unnecessary. Add XXX to undocumented patches that we should probably just drop, and make others easier to maintain. Upstream changes are far too numerous to include here, so here are the links to the corresponding release notes for each since 8.0.24: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-31.html https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-30.html https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-29.html https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-28.html https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-27.html https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-26.html https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-25.html Tested on SmartOS, I'll monitor bulk build reports for any fallout on other platforms (it takes ages to build).
databases: Replace RMD160 checksums with BLAKE2s checksums All checksums have been double-checked against existing RMD160 and SHA512 hashes The following distfiles could not be fetched (some may be only fetched conditionally): ./databases/cstore/distinfo D6.data.ros.gz ./databases/cstore/distinfo cstore0.2.tar.gz ./databases/cstore/distinfo data4.tar.gz
databases: Remove SHA1 distfile hashes
Pullup ticket #6472 - requested by nia databases/mysql80-client: NetBSD build fix Revisions pulled up: - databases/mysql80-client/distinfo 1.3 - databases/mysql80-client/patches/patch-sql_join__optimizer_bit__utils.h 1.1 --- Module Name: pkgsrc Committed By: nia Date: Sun Jun 27 06:41:56 UTC 2021 Modified Files: pkgsrc/databases/mysql80-client: distinfo Added Files: pkgsrc/databases/mysql80-client/patches: patch-sql_join__optimizer_bit__utils.h Log Message: mysql80: use __builtin_ffsll where ffsll is missing mysql80 uses some inline asm on x86_64, but falls back to the function on non-x86_64. netbsd does not have a ffsll function. helps build on non-x86_64.
mysql80: use __builtin_ffsll where ffsll is missing mysql80 uses some inline asm on x86_64, but falls back to the function on non-x86_64. netbsd does not have a ffsll function. helps build on non-x86_64.
mysql80: Fix build on NetBSD 9.x - Disable kqueue when EVFILT_USER is detected as missing by CMake. - Use Linux procfs when F_GETPATH is missing. - Define ppoll to pollts.
import mysql80-client and mysql80-server packages from pkgsrc wip package is experimental right now - it was confirmed working on NetBSD and compile on macOS only for now 8.0 brings many improvements over 5.7, following is shortened list, more details are available on https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html - transactional data dictionary - atomic DDL - integrated upgrade procedure - security and account management improvements - resource groups and threads (thread affinity needs some work for NetBSD) - table encryption management - loads of innodb enhancements - default character set utf8mb4 - JSON enhancements - CTE, Window functions - lateral derived tables - reworked regular experssion support - internal temporary tables - HASH JOIN optimization - EXPLAIN ANALYZE - time zone support for TIMESTAMP and DATETIME - optimizer hints for FORCE INDEX, IGNORE INDEX - XML enhancements - single preparation of statements - single RIGHT JOIN as LEFT JOIN handling - derived condition pushdown optimization Number of features were also deprecated, check the release notes for that