Download mysql server 5.61/17/2024 InnoDB: The page_zip_verify_checksum function returned false for a valid compressed page.InnoDB: Opening a foreign key-referenced table with foreign_key_checks enabled resulted in an error when the table or database name contained special characters.InnoDB: Importing a tablespace with a full-text index resulted in an assertion when attempting to rebuild the index.To adopt this change in MySQL, the key length used in vio/viosslfactories.c for creating Diffie-Hellman keys has been increased from 512 to 2,048 bits. OpenSSL has provided a detailed explanation at. Security-related: Due to the LogJam issue ( ), OpenSSL has changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up.validate_password_dictionary_file_last_parsed indicates when the dictionary file was last read, and validate_password_dictionary_file_words_count indicates how many words it contains. In addition, two new status variables are available. Now validate_password_dictionary_file can be set at runtime and assigning a value causes the named file to be read without a restart. Functionality Added/Changed: Previously, changes to the validate_password plugin dictionary file (named by the validate_password_dictionary_file system variable) while the server was running required a restart for the server to recognize the changes.To enable configuring digest length separately for the Performance Schema, its digest length is now controlled by the new performance_schema_max_digest_length system variable. Increasing the max_digest_length value has little impact on total memory requirements for those functions, but can increase Performance Schema memory requirements significantly. However, whereas the Performance Schema may need to maintain many digest values, other server functions such as MySQL Enterprise Firewall need only one digest per session. Functionality Added/Changed: Previously, the max_digest_length system variable controlled the maximum digest length for all server functions that computed statement digests.The new logic allows STOP SLAVE to complete faster in case some worker queues contain multiple transactions. Then, it waits for all workers to complete transactions older than that. This logic has been changed so that STOP SLAVE first finds the newest transaction that was committed by any worker thread. In previous MySQL versions, STOP SLAVE waited for all workers to process their entire queue. Functionality Added/Changed: Replication: When using a multi-threaded slave, each worker thread has its own queue of transactions to process.(including 3 potentially crashing bug fixes, and 1 performance-related fix) Here are the ones of note: Out of those other 36 bugs, 13 are InnoDB, 1 Partitioning, 3 Replication, and 19 misc. Or perhaps manually change the path location, each time open a connection that uses the Port to the other MySQL version (and remember to change it back after?).įor this reason, I Removed MySQL 5.7 completely, and will hence keep all cloud (and my local) servers at 5.6 for the time being - a Project for another day.MySQL 5.6.26 was recently released (it is the latest MySQL 5.6, is GA), and is available for download here.įor this release, there are 3 “Functionality Added or Changed” items, 1 “Security Fix”, and 36 other bug fixes. Since Workbench only allows a single mysqldump.exe file, to be used no matter which version of my local MySQL server is running. So when I upgrade (any/some/all of) my cloud servers to version 5.7, this looks to be another challenge to overcome. However, I have no idea how to make this work if you have two versions of MySQL on your machine, say MySQL 5.6 and 5.7, or 8.0. Paste in the file path for the appropriate version of mysqldump.exe (including the file name!) (version 8.0 was installed in C:\Program Files\MySQL\MySQL Workbench 8.0 CE)Įdit -> Preferences -> Administration -> Path to mysqldump Tool Found the version 5.6.41 (matching the MySQL version I'm running)Ĭlicked back to the General tab, to see the folder path that that version of mysqldump.exe was installed inĬ:\Program Files\MySQL\MySQL Server 5.6\bin, in my case.Right-clicked each mysqldump.exe it found -> Properties -> Details tab.From Windows Explorer, I searched my machine for all versions of mysqldump.exe.There seems to be no easy way to force lower version of MySQL Workbench to be installed instead (On my previous machine, before workbench 8.0, did NOT have this conflict when installed).įind the version of mysqldump.exe that matches the version of MySQL you're using: For compatibility, I needed MySQL 5.6.41 on my Windows 10 machine, so I used the 5.6.41 MySQL installer to install "All" (My Workbench, MySQL, connectors, etc).Įven though I used the installer for version 5.6.41, it installed Workbench 8.0, as well as version 8.0 of the various connectors, etc.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |