Skip to content

Tags: williamjava/mysql-server

Tags

mysql-cluster-7.5.4

Toggle mysql-cluster-7.5.4's commit message
Bug #24512715 AUTH_SEC.MYSQL_SSL_RSA_SETUP FAILS CONSISTENTLY ON HUDSON

Fix provided by YASSL. Upgrading YASSL to version 2.4.0.

(cherry picked from commit 840ca33cf4f61677c125a86b0b09aef6db3578bc)
(cherry picked from commit cf62be88efed6cc68eb9817665ac3563e83485e3)

mysql-cluster-7.4.13

Toggle mysql-cluster-7.4.13's commit message
Default datadir should not be changed for existing GA

The DATADIR_DEB setting isn't directly used by most server installations, as the packages provide
their own config files, but it's used by cluster, which has GA released based on 5.6, so the value
should not be changed here.

mysql-cluster-7.3.15

Toggle mysql-cluster-7.3.15's commit message
Default datadir should not be changed for existing GA

The DATADIR_DEB setting isn't directly used by most server installations, as the packages provide
their own config files, but it's used by cluster, which has GA released based on 5.6, so the value
should not be changed here.

(cherry picked from commit f1a56982f8d90990894983ced755112ab6cdb6d9)

mysql-cluster-7.2.26

Toggle mysql-cluster-7.2.26's commit message
Raising the Server version after merging in 5.5.53

mysql-5.6.34

Toggle mysql-5.6.34's commit message
Bug#24761774	PACKAGE UPGRADE FROM 5.6.33 TO 34 FAILING DUE TO SECURE-…

…FILE-PRIV PROBLEMS

Added creation of missing directory to server postinst

(cherry picked from commit e23c9bd1a18e4914b0371be049a2af8ee01e6e02)

mysql-5.7.16

Toggle mysql-5.7.16's commit message
Merge branch 'mysql-5.6' into mysql-5.7

(cherry picked from commit 710bafee9de1c11577242d694f74f5fa38df3a88)

mysql-5.5.53

Toggle mysql-5.5.53's commit message
Bug #24740291: YASSL UPDATE TO 2.4.2

mysql-5.6.33

Toggle mysql-5.6.33's commit message
Merge branch 'mysql-5.5' into mysql-5.6

(cherry picked from commit fa1aafe9819cb2d9389968f95f91f00f58997df4)

mysql-5.5.52

Toggle mysql-5.5.52's commit message
Bug#24464380 PRIVILEGE ESCALATION USING MYSQLD_SAFE

Post push fix: Solaris 10 /bin/sh don't understand $().

mysql-8.0.0

Toggle mysql-8.0.0's commit message
WL#6392 : Upgrade to Transactional Data Dictionary

With the implementation of the new data dictionary, the metadata will
be stored in the InnoDB tables. For the users to upgrade from the older
MySQL version(5.7) to mysql-8.0, dictionary tables should be created and
populated in old data directory from various metadata sources.

When the Mysql-8.0 server comes up, it detects for the presence of
dictionary tables.  If dictionary tables are not present,
they will be created in old data directory and populated
with the metadata. Then the server will proceed with normal start.

If dictionary tables are present, server will proceed with normal startup.

Upgrade Steps for Users
------------------------

1. Do a pre requisite check on 5.7 data directory.
2. Do a slow shutdown of mysql-5.7 server. Slow shutdown involves setting
   global variable 'innodb_fast_shutdown' to zero before server shutdown.
3. Start mysql-8.0 server on 5.7 data directory.
   mysql-8.0 server will detect if Dictionary tables are present or not.
   If dictionary tables are not present,  they will be created in old data
   directory. Metadata will be populated in dictionary tables.
   Then server will proceed with normal start.
4. Execute mysql_upgrade client tool.
5. Shutdown and start server again with normal configuration. (Recommended)

Reviewed-by: Nisha Gopalakrishnan <nisha.gopalakrishnan@oracle.com>
Reviewed-by: Thayumanavar Sachithanantham <thayumanavar.x.sachithanantha@oracle.com>
Reviewed-by: Dmitry Lenev <dmitry.lenev@oracle.com>