aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJochen Neumeister <joneum@FreeBSD.org>2023-04-11 16:50:30 +0000
committerJochen Neumeister <joneum@FreeBSD.org>2023-04-11 16:52:41 +0000
commite6137eac54ef1bc1e721b5064dda40e60ac1bf1b (patch)
tree98ff1478dc6782ca02b80b2ee2caf80d23b9de21
parent4e0d1b3b53fcb3f69d0c1370241ab2d6b7c58208 (diff)
downloadports-e6137eac54ef1bc1e721b5064dda40e60ac1bf1b.tar.gz
ports-e6137eac54ef1bc1e721b5064dda40e60ac1bf1b.zip
databases/mysql57-*: Update to 5.7.41
Bugs Fixed Replication: Issuing STOP SLAVE SQL_THREAD while the SQL thread was handling a transaction caused replication to stop immediately, instead of waiting 60 seconds for the event group to complete before shutting down the SQL thread as expected. The root cause of this issue was due to the internal variable storing the last event start time not being reset after the SQL thread was restarted. We fix this by resetting the variable holding the last event start time whenever the SQL thread is started. (Bug #33646899) Replication: The relay_log_space_limit system variable is a 64-bit value, but its valid maximum was specified internally as that of a 32-bit value. (Bug #106323, Bug #33799840) Some remote connections to the server were not handled correctly. This issue arose as the result of a previous fix for an issue with require_secure_transport. (Bug #34857411) References: This issue is a regression of: Bug #34094706. The linked OpenLDAP library for MySQL Server (Enterprise edition) was updated to version 2.5.13. (Bug #34815046) The bundled zlib library has been upgraded to zlib 1.2.13; zlib 1.2.13 is now the minimum zlib version supported. (Bug #34711762, Bug #34711758) Stack overruns could be erroneously reported when using the thread pool under heavy load. The race condition causing this in the thread pool has been avoided with an additional thread group ID check. (Bug #34414959) Data and GTIDs backed up by mysqldump were inconsistent when the options --single-transaction and --set-gtid-purged=ON were both used. This was because GTID_EXECUTED was fetched at the end of the dump, at which point the GTIDs on the server could have increased already. With this fix, a FLUSH TABLES WITH READ LOCK is performed at the beginning of the dump, and GTID_EXECUTED fetched immediately after, to ensure that its value is consistent with the snapshot taken by mysqldump. Full Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-41.html Sponsored by: Netzkommune GmbH
-rw-r--r--databases/mysql57-server/Makefile2
-rw-r--r--databases/mysql57-server/distinfo6
-rw-r--r--databases/mysql57-server/pkg-plist1
3 files changed, 5 insertions, 4 deletions
diff --git a/databases/mysql57-server/Makefile b/databases/mysql57-server/Makefile
index 4daecc0e0af2..5bab38bd22e5 100644
--- a/databases/mysql57-server/Makefile
+++ b/databases/mysql57-server/Makefile
@@ -1,5 +1,5 @@
PORTNAME?= mysql
-PORTVERSION= 5.7.40
+PORTVERSION= 5.7.41
PORTREVISION?= 0
CATEGORIES= databases
MASTER_SITES= MYSQL/MySQL-5.7
diff --git a/databases/mysql57-server/distinfo b/databases/mysql57-server/distinfo
index b033d6a2b46f..18bfbcbb9a6c 100644
--- a/databases/mysql57-server/distinfo
+++ b/databases/mysql57-server/distinfo
@@ -1,3 +1,3 @@
-TIMESTAMP = 1666961092
-SHA256 (mysql-boost-5.7.40.tar.gz) = e2a93d90e5773286efb71cb34cab0d51cd70d35e71c24c71eaa5df45f4b2de87
-SIZE (mysql-boost-5.7.40.tar.gz) = 53255386
+TIMESTAMP = 1681024896
+SHA256 (mysql-boost-5.7.41.tar.gz) = d5735e172fbd235d22d2c7eec084c51e7a1648d9e28c78b54e0c8b8d46751cb9
+SIZE (mysql-boost-5.7.41.tar.gz) = 53266489
diff --git a/databases/mysql57-server/pkg-plist b/databases/mysql57-server/pkg-plist
index 2dd6957e703e..a573dc16145d 100644
--- a/databases/mysql57-server/pkg-plist
+++ b/databases/mysql57-server/pkg-plist
@@ -70,6 +70,7 @@ lib/mysql/plugin/test_udf_services.so
lib/mysql/plugin/validate_password.so
lib/mysql/plugin/version_token.so
libexec/mysqld
+share/info/mysql.info
share/man/man1/my_print_defaults.1.gz
share/man/man1/myisam_ftdump.1.gz
share/man/man1/myisamchk.1.gz