Date: Fri, 17 Jan 2020 14:38:40 +0000 (UTC) From: Jochen Neumeister <joneum@FreeBSD.org> To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-branches@freebsd.org Subject: svn commit: r523299 - branches/2020Q1/databases/mysql56-server Message-ID: <202001171438.00HEceCd061301@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: joneum Date: Fri Jan 17 14:38:39 2020 New Revision: 523299 URL: https://svnweb.freebsd.org/changeset/ports/523299 Log: MFH: r523297 databases/mysql56-{client, server}: Update to latest release 5.6.47 Bugs Fixed: - Replication: When GTIDs are enabled on a replication master and slave, and the slave connects to the master with the MASTER_AUTO_POSITION=1 option set, the master must send the slave all the transactions that the slave has not already received, committed, or both. If any of the transactions that should be sent by the master have been already purged from the master's binary log, the master sends the error ER_MASTER_HAS_PURGED_REQUIRED_GTIDS (1789) to the slave, and replication does not start. The message provided for the error ER_MASTER_HAS_PURGED_REQUIRED_GTIDS has been changed to provide advice on the correct action in this situation, which is for the slave to replicate the missing transactions from another source, or for the slave to be replaced by a new slave created from a more recent backup. The message advises that the master's binary log expiration period can be revised to avoid the situation in future. In addition, the master now identifies the GTIDs of the purged transactions and supplies them in its error log in the warning message ER_FOUND_MISSING_GTIDS (11809), so that you do not need to calculate the missing GTIDs manually. - With multiple sessions executing concurrent INSERT ... ON DUPLICATE KEY UPDATE statements into a table with an AUTO_INCREMENT column but not specifying the AUTO_INCREMENT value, inserts could fail with a unique index violation. - A SELECT using a WHERE condition of the form A AND (B OR C [OR ...]) resulting in an impossible range led to an unplanned exit of the server. - An incomplete connection packet could cause clients not to properly initialize the authentication plugin name. Approved by: mmokhi (maintainer, implicit) Security: a6cf65ad-37d2-11ea-a1c7-b499baebfeaf Sponsored by: Netzkommune GmbH Approved by: ports-secteam (with hat) Modified: branches/2020Q1/databases/mysql56-server/Makefile branches/2020Q1/databases/mysql56-server/distinfo Directory Properties: branches/2020Q1/ (props changed) Modified: branches/2020Q1/databases/mysql56-server/Makefile ============================================================================== --- branches/2020Q1/databases/mysql56-server/Makefile Fri Jan 17 14:37:31 2020 (r523298) +++ branches/2020Q1/databases/mysql56-server/Makefile Fri Jan 17 14:38:39 2020 (r523299) @@ -2,7 +2,7 @@ # $FreeBSD$ PORTNAME?= mysql -PORTVERSION= 5.6.46 +PORTVERSION= 5.6.47 PORTREVISION?= 0 CATEGORIES= databases MASTER_SITES= MYSQL/MySQL-5.6 Modified: branches/2020Q1/databases/mysql56-server/distinfo ============================================================================== --- branches/2020Q1/databases/mysql56-server/distinfo Fri Jan 17 14:37:31 2020 (r523298) +++ branches/2020Q1/databases/mysql56-server/distinfo Fri Jan 17 14:38:39 2020 (r523299) @@ -1,3 +1,3 @@ -TIMESTAMP = 1577785560 -SHA256 (mysql-5.6.46.tar.gz) = 12e1fbabf2086e6175359767ca89fa8a58f9274fcad40434aa6a56e582d65f49 -SIZE (mysql-5.6.46.tar.gz) = 32395002 +TIMESTAMP = 1579257087 +SHA256 (mysql-5.6.47.tar.gz) = 0919096705784c62af831bb607e99345083edd76967c8c65966728742a9127fe +SIZE (mysql-5.6.47.tar.gz) = 32388152
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202001171438.00HEceCd061301>