diff -Nru mysql-5.5-5.5.35+dfsg/BUILD/cleanup mysql-5.5-5.5.43/BUILD/cleanup --- mysql-5.5-5.5.35+dfsg/BUILD/cleanup 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/BUILD/cleanup 2015-02-27 08:30:34.000000000 +0000 @@ -1,7 +1,7 @@ #! /bin/sh # Copyright (C) 2003 MySQL AB -# +# Use is subject to license terms # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; version 2 of the License. diff -Nru mysql-5.5-5.5.35+dfsg/BUILD/compile-alpha mysql-5.5-5.5.43/BUILD/compile-alpha --- mysql-5.5-5.5.35+dfsg/BUILD/compile-alpha 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/BUILD/compile-alpha 2015-02-27 08:30:34.000000000 +0000 @@ -1,7 +1,7 @@ #! /bin/sh # Copyright (C) 2000, 2002 MySQL AB -# +# Use is subject to license terms # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; version 2 of the License. diff -Nru mysql-5.5-5.5.35+dfsg/BUILD/compile-amd64-debug-max-no-ndb mysql-5.5-5.5.43/BUILD/compile-amd64-debug-max-no-ndb --- mysql-5.5-5.5.35+dfsg/BUILD/compile-amd64-debug-max-no-ndb 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/BUILD/compile-amd64-debug-max-no-ndb 2015-02-27 08:30:34.000000000 +0000 @@ -1,7 +1,7 @@ #! /bin/sh # Copyright (C) 2005, 2006 MySQL AB -# +# Use is subject to license terms # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU Library General Public # License as published by the Free Software Foundation; version 2 diff -Nru mysql-5.5-5.5.35+dfsg/BUILD/compile-amd64-gcov mysql-5.5-5.5.43/BUILD/compile-amd64-gcov --- mysql-5.5-5.5.35+dfsg/BUILD/compile-amd64-gcov 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/BUILD/compile-amd64-gcov 2015-02-27 08:30:34.000000000 +0000 @@ -1,7 +1,7 @@ #! /bin/sh # Copyright (C) 2007 MySQL AB -# +# Use is subject to license terms # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; version 2 of the License. diff -Nru mysql-5.5-5.5.35+dfsg/BUILD/compile-amd64-gprof mysql-5.5-5.5.43/BUILD/compile-amd64-gprof --- mysql-5.5-5.5.35+dfsg/BUILD/compile-amd64-gprof 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/BUILD/compile-amd64-gprof 2015-02-27 08:30:34.000000000 +0000 @@ -1,7 +1,7 @@ #! /bin/sh # Copyright (C) 2007 MySQL AB -# +# Use is subject to license terms # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; version 2 of the License. diff -Nru mysql-5.5-5.5.35+dfsg/BUILD/compile-amd64-max-sci mysql-5.5-5.5.43/BUILD/compile-amd64-max-sci --- mysql-5.5-5.5.35+dfsg/BUILD/compile-amd64-max-sci 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/BUILD/compile-amd64-max-sci 2015-02-27 08:30:34.000000000 +0000 @@ -1,7 +1,7 @@ #! /bin/sh # Copyright (C) 2007 MySQL AB -# +# Use is subject to license terms # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; version 2 of the License. diff -Nru mysql-5.5-5.5.35+dfsg/BUILD/compile-pentium64 mysql-5.5-5.5.43/BUILD/compile-pentium64 --- mysql-5.5-5.5.35+dfsg/BUILD/compile-pentium64 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/BUILD/compile-pentium64 2015-02-27 08:30:34.000000000 +0000 @@ -1,6 +1,7 @@ #! /bin/sh # Copyright (C) 2006, 2007 MySQL AB +# Use is subject to license terms # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU Library General Public diff -Nru mysql-5.5-5.5.35+dfsg/BUILD/compile-pentium64-gcov mysql-5.5-5.5.43/BUILD/compile-pentium64-gcov --- mysql-5.5-5.5.35+dfsg/BUILD/compile-pentium64-gcov 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/BUILD/compile-pentium64-gcov 2015-02-27 08:30:34.000000000 +0000 @@ -1,6 +1,7 @@ #! /bin/sh # Copyright (C) 2007 MySQL AB +# Use is subject to license terms # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/BUILD/compile-pentium64-gprof mysql-5.5-5.5.43/BUILD/compile-pentium64-gprof --- mysql-5.5-5.5.35+dfsg/BUILD/compile-pentium64-gprof 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/BUILD/compile-pentium64-gprof 2015-02-27 08:30:34.000000000 +0000 @@ -1,6 +1,7 @@ #! /bin/sh # Copyright (C) 2007 MySQL AB +# Use is subject to license terms # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/BUILD/compile-pentium64-max mysql-5.5-5.5.43/BUILD/compile-pentium64-max --- mysql-5.5-5.5.35+dfsg/BUILD/compile-pentium64-max 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/BUILD/compile-pentium64-max 2015-02-27 08:30:34.000000000 +0000 @@ -1,6 +1,7 @@ #! /bin/sh # Copyright (C) 2007 MySQL AB +# Use is subject to license terms # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU Library General Public diff -Nru mysql-5.5-5.5.35+dfsg/BUILD/compile-pentium64-max-sci mysql-5.5-5.5.43/BUILD/compile-pentium64-max-sci --- mysql-5.5-5.5.35+dfsg/BUILD/compile-pentium64-max-sci 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/BUILD/compile-pentium64-max-sci 2015-02-27 08:30:34.000000000 +0000 @@ -1,7 +1,8 @@ #! /bin/sh # Copyright (C) 2007 MySQL AB -# +# Use is subject to license terms +# # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; version 2 of the License. diff -Nru mysql-5.5-5.5.35+dfsg/BUILD/compile-pentium-cybozu mysql-5.5-5.5.43/BUILD/compile-pentium-cybozu --- mysql-5.5-5.5.35+dfsg/BUILD/compile-pentium-cybozu 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/BUILD/compile-pentium-cybozu 2015-02-27 08:30:34.000000000 +0000 @@ -1,7 +1,7 @@ #! /bin/sh # Copyright (C) 2005 MySQL AB -# +# Use is subject to license terms # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; version 2 of the License. diff -Nru mysql-5.5-5.5.35+dfsg/BUILD/compile-pentium-gcov mysql-5.5-5.5.43/BUILD/compile-pentium-gcov --- mysql-5.5-5.5.35+dfsg/BUILD/compile-pentium-gcov 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/BUILD/compile-pentium-gcov 2015-02-27 08:30:34.000000000 +0000 @@ -1,7 +1,7 @@ #! /bin/sh # Copyright (C) 2000, 2007 MySQL AB -# +# Use is subject to license terms # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; version 2 of the License. diff -Nru mysql-5.5-5.5.35+dfsg/BUILD/compile-pentium-gprof mysql-5.5-5.5.43/BUILD/compile-pentium-gprof --- mysql-5.5-5.5.35+dfsg/BUILD/compile-pentium-gprof 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/BUILD/compile-pentium-gprof 2015-02-27 08:30:34.000000000 +0000 @@ -1,7 +1,7 @@ #! /bin/sh # Copyright (C) 2001, 2007 MySQL AB -# +# Use is subject to license terms # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; version 2 of the License. diff -Nru mysql-5.5-5.5.35+dfsg/BUILD/compile-pentium-icc mysql-5.5-5.5.43/BUILD/compile-pentium-icc --- mysql-5.5-5.5.35+dfsg/BUILD/compile-pentium-icc 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/BUILD/compile-pentium-icc 2015-02-27 08:30:34.000000000 +0000 @@ -1,7 +1,8 @@ #! /bin/sh # Copyright (C) 2005 MySQL AB -# +# Use is subject to license terms +# # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; version 2 of the License. diff -Nru mysql-5.5-5.5.35+dfsg/BUILD/compile-pentium-icc-yassl mysql-5.5-5.5.43/BUILD/compile-pentium-icc-yassl --- mysql-5.5-5.5.35+dfsg/BUILD/compile-pentium-icc-yassl 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/BUILD/compile-pentium-icc-yassl 2015-02-27 08:30:34.000000000 +0000 @@ -1,7 +1,8 @@ #! /bin/sh # Copyright (C) 2005 MySQL AB -# +# Use is subject to license terms +# # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; version 2 of the License. diff -Nru mysql-5.5-5.5.35+dfsg/BUILD/compile-pentium-myodbc mysql-5.5-5.5.43/BUILD/compile-pentium-myodbc --- mysql-5.5-5.5.35+dfsg/BUILD/compile-pentium-myodbc 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/BUILD/compile-pentium-myodbc 2015-02-27 08:30:34.000000000 +0000 @@ -1,7 +1,8 @@ #! /bin/sh # Copyright (C) 2000 MySQL AB -# +# Use is subject to license terms +# # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; version 2 of the License. diff -Nru mysql-5.5-5.5.35+dfsg/BUILD/compile-ppc mysql-5.5-5.5.43/BUILD/compile-ppc --- mysql-5.5-5.5.35+dfsg/BUILD/compile-ppc 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/BUILD/compile-ppc 2015-02-27 08:30:34.000000000 +0000 @@ -1,7 +1,8 @@ #! /bin/sh # Copyright (C) 2004 MySQL AB -# +# Use is subject to license terms +# # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; version 2 of the License. diff -Nru mysql-5.5-5.5.35+dfsg/BUILD/compile-solaris-amd64 mysql-5.5-5.5.43/BUILD/compile-solaris-amd64 --- mysql-5.5-5.5.35+dfsg/BUILD/compile-solaris-amd64 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/BUILD/compile-solaris-amd64 2015-02-27 08:30:34.000000000 +0000 @@ -1,6 +1,7 @@ #!/usr/bin/bash # Copyright (C) 2007 MySQL AB +# Use is subject to license terms # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU Library General Public diff -Nru mysql-5.5-5.5.35+dfsg/BUILD/compile-solaris-amd64-debug mysql-5.5-5.5.43/BUILD/compile-solaris-amd64-debug --- mysql-5.5-5.5.35+dfsg/BUILD/compile-solaris-amd64-debug 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/BUILD/compile-solaris-amd64-debug 2015-02-27 08:30:34.000000000 +0000 @@ -1,7 +1,8 @@ #! /bin/sh # Copyright (C) 2007 MySQL AB -# +# Use is subject to license terms +# # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; version 2 of the License. diff -Nru mysql-5.5-5.5.35+dfsg/client/CMakeLists.txt mysql-5.5-5.5.43/client/CMakeLists.txt --- mysql-5.5-5.5.35+dfsg/client/CMakeLists.txt 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/client/CMakeLists.txt 2015-02-27 08:30:34.000000000 +0000 @@ -35,6 +35,12 @@ MYSQL_ADD_EXECUTABLE(mysqltest mysqltest.cc COMPONENT Test) SET_SOURCE_FILES_PROPERTIES(mysqltest.cc PROPERTIES COMPILE_FLAGS "-DTHREADS") +# mysqltest has unused result errors, so we skip Werror +CHECK_C_COMPILER_FLAG("-Werror" HAVE_WERROR_FLAG) +IF(HAVE_WERROR_FLAG) + INCLUDE(${MYSQL_CMAKE_SCRIPT_DIR}/compile_flags.cmake) + ADD_COMPILE_FLAGS(mysqltest.cc COMPILE_FLAGS "-Wno-error") +ENDIF() TARGET_LINK_LIBRARIES(mysqltest mysqlclient regex) diff -Nru mysql-5.5-5.5.35+dfsg/client/mysqladmin.cc mysql-5.5-5.5.43/client/mysqladmin.cc --- mysql-5.5-5.5.35+dfsg/client/mysqladmin.cc 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/client/mysqladmin.cc 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2000, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -71,6 +71,7 @@ char *argument); static my_bool sql_connect(MYSQL *mysql, uint wait); static int execute_commands(MYSQL *mysql,int argc, char **argv); +static char **mask_password(int argc, char ***argv); static int drop_db(MYSQL *mysql,const char *db); extern "C" sig_handler endprog(int signal_number); static void nice_time(ulong sec,char *buff); @@ -304,9 +305,9 @@ int main(int argc,char *argv[]) { - int error= 0, ho_error; + int error= 0, ho_error, temp_argc; MYSQL mysql; - char **commands, **save_argv; + char **commands, **save_argv, **temp_argv; MY_INIT(argv[0]); mysql_init(&mysql); @@ -318,6 +319,9 @@ free_defaults(save_argv); exit(ho_error); } + temp_argv= mask_password(argc, &argv); + temp_argc= argc; + if (debug_info_flag) my_end_arg= MY_CHECK_ERROR | MY_GIVE_INFO; if (debug_check_flag) @@ -328,7 +332,7 @@ usage(); exit(1); } - commands = argv; + commands = temp_argv; if (tty_password) opt_password = get_tty_password(NullS); @@ -476,6 +480,13 @@ my_free(shared_memory_base_name); #endif free_defaults(save_argv); + temp_argc--; + while(temp_argc >= 0) + { + my_free(temp_argv[temp_argc]); + temp_argc--; + } + my_free(temp_argv); my_end(my_end_arg); exit(error ? 1 : 0); return 0; @@ -1089,6 +1100,47 @@ return 0; } +/** + @brief Masking the password if it is passed as command line argument. + + @details It works in Linux and changes cmdline in ps and /proc/pid/cmdline, + but it won't work for history file of shell. + The command line arguments are copied to another array and the + password in the argv is masked. This function is called just after + "handle_options" because in "handle_options", the agrv pointers + are altered which makes freeing of dynamically allocated memory + difficult. The password masking is done before all other operations + in order to minimise the time frame of password visibility via cmdline. + + @param argc command line options (count) + @param argv command line options (values) + + @return temp_argv copy of argv +*/ + +static char **mask_password(int argc, char ***argv) +{ + char **temp_argv; + temp_argv= (char **)(my_malloc(sizeof(char *) * argc, MYF(MY_WME))); + argc--; + while (argc > 0) + { + temp_argv[argc]= my_strdup((*argv)[argc], MYF(MY_FAE)); + if (find_type((*argv)[argc - 1],&command_typelib, FIND_TYPE_BASIC) == ADMIN_PASSWORD || + find_type((*argv)[argc - 1],&command_typelib, FIND_TYPE_BASIC) == ADMIN_OLD_PASSWORD) + { + char *start= (*argv)[argc]; + while (*start) + *start++= 'x'; + start= (*argv)[argc]; + if (*start) + start[1]= 0; /* Cut length of argument */ + } + argc--; + } + temp_argv[argc]= my_strdup((*argv)[argc], MYF(MY_FAE)); + return(temp_argv); +} static void print_version(void) { diff -Nru mysql-5.5-5.5.35+dfsg/client/mysqlbinlog.cc mysql-5.5-5.5.43/client/mysqlbinlog.cc --- mysql-5.5-5.5.35+dfsg/client/mysqlbinlog.cc 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/client/mysqlbinlog.cc 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -2102,6 +2102,7 @@ DBUG_PROCESS(argv[0]); my_init_time(); // for time functions + tzset(); // set tzname if (load_defaults("my", load_default_groups, &argc, &argv)) exit(1); diff -Nru mysql-5.5-5.5.35+dfsg/client/mysql.cc mysql-5.5-5.5.43/client/mysql.cc --- mysql-5.5-5.5.35+dfsg/client/mysql.cc 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/client/mysql.cc 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -1176,9 +1176,9 @@ put_info("Welcome to the MySQL monitor. Commands end with ; or \\g.", INFO_INFO); - sprintf((char*) glob_buffer.ptr(), - "Your MySQL connection id is %lu\nServer version: %s\n", - mysql_thread_id(&mysql), server_version_string(&mysql)); + snprintf((char*) glob_buffer.ptr(), glob_buffer.alloced_length(), + "Your MySQL connection id is %lu\nServer version: %s\n", + mysql_thread_id(&mysql), server_version_string(&mysql)); put_info((char*) glob_buffer.ptr(),INFO_INFO); put_info(ORACLE_WELCOME_COPYRIGHT_NOTICE("2000"), INFO_INFO); @@ -1242,6 +1242,16 @@ sig_handler mysql_end(int sig) { +#ifndef _WIN32 + /* + Ingnoring SIGQUIT and SIGINT signals when cleanup process starts. + This will help in resolving the double free issues, which occures in case + the signal handler function is started in between the clean up function. + */ + signal(SIGQUIT, SIG_IGN); + signal(SIGINT, SIG_IGN); +#endif + mysql_close(&mysql); #ifdef HAVE_READLINE if (!status.batch && !quick && !opt_html && !opt_xml && diff -Nru mysql-5.5-5.5.35+dfsg/client/mysqlcheck.c mysql-5.5-5.5.43/client/mysqlcheck.c --- mysql-5.5-5.5.35+dfsg/client/mysqlcheck.c 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/client/mysqlcheck.c 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2001, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2001, 2011, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/client/mysqldump.c mysql-5.5-5.5.43/client/mysqldump.c --- mysql-5.5-5.5.35+dfsg/client/mysqldump.c 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/client/mysqldump.c 2015-02-27 08:30:34.000000000 +0000 @@ -5538,19 +5538,36 @@ dump_all_tablespaces(); dump_all_databases(); } - else if (argc > 1 && !opt_databases) - { - /* Only one database and selected table(s) */ - if (!opt_alltspcs && !opt_notspcs) - dump_tablespaces_for_tables(*argv, (argv + 1), (argc -1)); - dump_selected_tables(*argv, (argv + 1), (argc - 1)); - } else { - /* One or more databases, all tables */ - if (!opt_alltspcs && !opt_notspcs) - dump_tablespaces_for_databases(argv); - dump_databases(argv); + // Check all arguments meet length condition. Currently database and table + // names are limited to NAME_LEN bytes and stack-based buffers assumes + // that escaped name will be not longer than NAME_LEN*2 + 2 bytes long. + int argument; + for (argument= 0; argument < argc; argument++) + { + size_t argument_length= strlen(argv[argument]); + if (argument_length > NAME_LEN) + { + die(EX_CONSCHECK, "[ERROR] Argument '%s' is too long, it cannot be " + "name for any table or database.\n", argv[argument]); + } + } + + if (argc > 1 && !opt_databases) + { + /* Only one database and selected table(s) */ + if (!opt_alltspcs && !opt_notspcs) + dump_tablespaces_for_tables(*argv, (argv + 1), (argc - 1)); + dump_selected_tables(*argv, (argv + 1), (argc - 1)); + } + else + { + /* One or more databases, all tables */ + if (!opt_alltspcs && !opt_notspcs) + dump_tablespaces_for_databases(argv); + dump_databases(argv); + } } /* if --dump-slave , start the slave sql thread */ diff -Nru mysql-5.5-5.5.35+dfsg/client/mysql_plugin.c mysql-5.5-5.5.43/client/mysql_plugin.c --- mysql-5.5-5.5.35+dfsg/client/mysql_plugin.c 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/client/mysql_plugin.c 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2011, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2011, 2013, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -856,7 +856,7 @@ strncat(buff, FN_DIRSEP, sizeof(buff) - strlen(buff) - 1); #endif buff[sizeof(buff) - 1]= 0; - my_delete(opt_basedir, MYF(0)); + my_free(opt_basedir); opt_basedir= my_strdup(buff, MYF(MY_FAE)); } } diff -Nru mysql-5.5-5.5.35+dfsg/client/mysql_upgrade.c mysql-5.5-5.5.43/client/mysql_upgrade.c --- mysql-5.5-5.5.35+dfsg/client/mysql_upgrade.c 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/client/mysql_upgrade.c 2015-02-27 08:30:34.000000000 +0000 @@ -462,6 +462,7 @@ */ if (run_tool(tool_executable_name, &ds_tmp, /* Get output from command, discard*/ + "--no-defaults", "--help", "2>&1", IF_WIN("> NUL", "> /dev/null"), diff -Nru mysql-5.5-5.5.35+dfsg/cmake/build_configurations/mysql_release.cmake mysql-5.5-5.5.43/cmake/build_configurations/mysql_release.cmake --- mysql-5.5-5.5.35+dfsg/cmake/build_configurations/mysql_release.cmake 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/cmake/build_configurations/mysql_release.cmake 2015-02-27 08:30:34.000000000 +0000 @@ -189,15 +189,16 @@ ENDIF() ENDIF() - # OSX flags - IF(APPLE) - SET(COMMON_C_FLAGS "-g -fno-common -fno-strict-aliasing") - # XXX: why are we using -felide-constructors on OSX? - SET(COMMON_CXX_FLAGS "-g -fno-common -felide-constructors -fno-strict-aliasing") - SET(CMAKE_C_FLAGS_DEBUG "-O ${COMMON_C_FLAGS}") - SET(CMAKE_CXX_FLAGS_DEBUG "-O ${COMMON_CXX_FLAGS}") - SET(CMAKE_C_FLAGS_RELWITHDEBINFO "-Os ${COMMON_C_FLAGS}") - SET(CMAKE_CXX_FLAGS_RELWITHDEBINFO "-Os ${COMMON_CXX_FLAGS}") + # Default Clang flags + IF(CMAKE_C_COMPILER_ID MATCHES "Clang") + SET(COMMON_C_FLAGS "-g -fno-omit-frame-pointer -fno-strict-aliasing") + SET(CMAKE_C_FLAGS_DEBUG "${COMMON_C_FLAGS}") + SET(CMAKE_C_FLAGS_RELWITHDEBINFO "-O3 ${COMMON_C_FLAGS}") + ENDIF() + IF(CMAKE_CXX_COMPILER_ID MATCHES "Clang") + SET(COMMON_CXX_FLAGS "-g -fno-omit-frame-pointer -fno-strict-aliasing") + SET(CMAKE_CXX_FLAGS_DEBUG "${COMMON_CXX_FLAGS}") + SET(CMAKE_CXX_FLAGS_RELWITHDEBINFO "-O3 ${COMMON_CXX_FLAGS}") ENDIF() # Solaris flags diff -Nru mysql-5.5-5.5.35+dfsg/cmake/compile_flags.cmake mysql-5.5-5.5.43/cmake/compile_flags.cmake --- mysql-5.5-5.5.35+dfsg/cmake/compile_flags.cmake 1970-01-01 00:00:00.000000000 +0000 +++ mysql-5.5-5.5.43/cmake/compile_flags.cmake 2015-02-27 08:30:34.000000000 +0000 @@ -0,0 +1,44 @@ +# Copyright (c) 2014, 2015, Oracle and/or its affiliates. All rights reserved. +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; version 2 of the License. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program; if not, write to the Free Software +# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + + +## ADD_COMPILE_FLAGS( COMPILE_FLAGS ) +MACRO(ADD_COMPILE_FLAGS) + SET(FILES "") + SET(FLAGS "") + SET(COMPILE_FLAGS_SEEN) + FOREACH(ARG ${ARGV}) + IF(ARG STREQUAL "COMPILE_FLAGS") + SET(COMPILE_FLAGS_SEEN 1) + ELSEIF(COMPILE_FLAGS_SEEN) + LIST(APPEND FLAGS ${ARG}) + ELSE() + LIST(APPEND FILES ${ARG}) + ENDIF() + ENDFOREACH() + FOREACH(FILE ${FILES}) + FOREACH(FLAG ${FLAGS}) + GET_SOURCE_FILE_PROPERTY(PROP ${FILE} COMPILE_FLAGS) + IF(NOT PROP) + SET(PROP ${FLAG}) + ELSE() + SET(PROP "${PROP} ${FLAG}") + ENDIF() + SET_SOURCE_FILES_PROPERTIES( + ${FILE} PROPERTIES COMPILE_FLAGS "${PROP}" + ) + ENDFOREACH() + ENDFOREACH() +ENDMACRO() diff -Nru mysql-5.5-5.5.35+dfsg/cmake/cpack_source_ignore_files.cmake mysql-5.5-5.5.43/cmake/cpack_source_ignore_files.cmake --- mysql-5.5-5.5.35+dfsg/cmake/cpack_source_ignore_files.cmake 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/cmake/cpack_source_ignore_files.cmake 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -# Copyright (c) 2009, 2010, Oracle and/or its affiliates. All rights reserved. +# Copyright (c) 2009, 2014, Oracle and/or its affiliates. All rights reserved. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -14,9 +14,6 @@ # Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA SET(CPACK_SOURCE_IGNORE_FILES -\\\\.bzr/ -\\\\.bzr-mysql -\\\\.bzrignore CMakeCache\\\\.txt cmake_dist\\\\.cmake CPackSourceConfig\\\\.cmake diff -Nru mysql-5.5-5.5.35+dfsg/cmake/dtrace.cmake mysql-5.5-5.5.43/cmake/dtrace.cmake --- mysql-5.5-5.5.35+dfsg/cmake/dtrace.cmake 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/cmake/dtrace.cmake 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -# Copyright (c) 2009, 2013, Oracle and/or its affiliates. All rights reserved. +# Copyright (c) 2009, 2014, Oracle and/or its affiliates. All rights reserved. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -37,7 +37,15 @@ # On FreeBSD, dtrace does not handle userland tracing yet IF(DTRACE AND NOT CMAKE_SYSTEM_NAME MATCHES "FreeBSD" AND NOT BUGGY_GCC_NO_DTRACE_MODULES) - SET(ENABLE_DTRACE ON CACHE BOOL "Enable dtrace") + # 5.5 not able to do Sun dtrace on linux, just disable it + EXECUTE_PROCESS( + COMMAND ${DTRACE} -V + OUTPUT_VARIABLE out) + IF(out MATCHES "Sun D" AND CMAKE_SYSTEM_NAME MATCHES "Linux") + SET(ENABLE_DTRACE OFF CACHE BOOL "Sun DTrace on Linux not supported") + ELSE() + SET(ENABLE_DTRACE ON CACHE BOOL "Enable dtrace") + ENDIF() ENDIF() SET(HAVE_DTRACE ${ENABLE_DTRACE}) IF(CMAKE_SYSTEM_NAME MATCHES "SunOS") @@ -74,13 +82,6 @@ ${CMAKE_BINARY_DIR}/include/probes_mysql_dtrace.h ${CMAKE_BINARY_DIR}/include/probes_mysql_nodtrace.h ) - IF(CMAKE_SYSTEM_NAME MATCHES "Linux") - # Systemtap object - EXECUTE_PROCESS( - COMMAND ${DTRACE} -G -s ${CMAKE_SOURCE_DIR}/include/probes_mysql.d.base - -o ${CMAKE_BINARY_DIR}/probes_mysql.o - ) - ENDIF() ADD_CUSTOM_TARGET(gen_dtrace_header DEPENDS ${CMAKE_BINARY_DIR}/include/probes_mysql.d @@ -99,12 +100,7 @@ IF(ENABLE_DTRACE) ADD_DEPENDENCIES(${target} gen_dtrace_header) - IF(CMAKE_SYSTEM_NAME MATCHES "Linux") - TARGET_LINK_LIBRARIES(${target} ${CMAKE_BINARY_DIR}/probes_mysql.o) - ENDIF() - - # On Solaris, invoke dtrace -G to generate object file and - # link it together with target. + # Invoke dtrace to generate object file and link it together with target. IF(CMAKE_SYSTEM_NAME MATCHES "SunOS") SET(objdir ${CMAKE_CURRENT_BINARY_DIR}/CMakeFiles/${target}.dir) SET(outfile ${objdir}/${target}_dtrace.o) @@ -121,6 +117,21 @@ -P ${CMAKE_SOURCE_DIR}/cmake/dtrace_prelink.cmake WORKING_DIRECTORY ${objdir} ) + ELSEIF(CMAKE_SYSTEM_NAME MATCHES "Linux") + # dtrace on Linux runs gcc and uses flags from environment + SET(CFLAGS_SAVED $ENV{CFLAGS}) + SET(ENV{CFLAGS} ${CMAKE_C_FLAGS}) + SET(outfile "${CMAKE_BINARY_DIR}/probes_mysql.o") + # Systemtap object + EXECUTE_PROCESS( + COMMAND ${DTRACE} -G -s ${CMAKE_SOURCE_DIR}/include/probes_mysql.d.base + -o ${outfile} + ) + SET(ENV{CFLAGS} ${CFLAGS_SAVED}) + ENDIF() + + # Do not try to extend the library if we have not built the .o file + IF(outfile) # Add full object path to linker flags GET_TARGET_PROPERTY(target_type ${target} TYPE) IF(NOT target_type MATCHES "STATIC") @@ -132,12 +143,12 @@ # but maybe one day this will be fixed. GET_TARGET_PROPERTY(target_location ${target} LOCATION) ADD_CUSTOM_COMMAND( - TARGET ${target} POST_BUILD - COMMAND ${CMAKE_AR} r ${target_location} ${outfile} - COMMAND ${CMAKE_RANLIB} ${target_location} - ) - # Used in DTRACE_INSTRUMENT_WITH_STATIC_LIBS - SET(TARGET_OBJECT_DIRECTORY_${target} ${objdir} CACHE INTERNAL "") + TARGET ${target} POST_BUILD + COMMAND ${CMAKE_AR} r ${target_location} ${outfile} + COMMAND ${CMAKE_RANLIB} ${target_location} + ) + # Used in DTRACE_INSTRUMENT_WITH_STATIC_LIBS + SET(TARGET_OBJECT_DIRECTORY_${target} ${objdir} CACHE INTERNAL "") ENDIF() ENDIF() ENDIF() diff -Nru mysql-5.5-5.5.35+dfsg/cmake/info_macros.cmake.in mysql-5.5-5.5.43/cmake/info_macros.cmake.in --- mysql-5.5-5.5.35+dfsg/cmake/info_macros.cmake.in 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/cmake/info_macros.cmake.in 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -# Copyright (c) 2011, 2012, Oracle and/or its affiliates. All rights reserved. +# Copyright (c) 2011, 2014, Oracle and/or its affiliates. All rights reserved. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -23,11 +23,14 @@ # If further variables are used in this file, add them to this list. SET(VERSION "@VERSION@") +SET(MAJOR_VERSION "@MAJOR_VERSION@") +SET(MINOR_VERSION "@MINOR_VERSION@") +SET(PATCH_VERSION "@PATCH_VERSION@") SET(CMAKE_SOURCE_DIR "@CMAKE_SOURCE_DIR@") SET(CMAKE_BINARY_DIR "@CMAKE_BINARY_DIR@") SET(CMAKE_GENERATOR "@CMAKE_GENERATOR@") SET(CMAKE_SIZEOF_VOID_P "@CMAKE_SIZEOF_VOID_P@") -SET(BZR_EXECUTABLE "@BZR_EXECUTABLE@") +SET(GIT_EXECUTABLE "@GIT_EXECUTABLE@") SET(CMAKE_CROSSCOMPILING "@CMAKE_CROSSCOMPILING@") SET(CMAKE_HOST_SYSTEM "@CMAKE_HOST_SYSTEM@") SET(CMAKE_HOST_SYSTEM_PROCESSOR "@CMAKE_HOST_SYSTEM_PROCESSOR@") @@ -36,27 +39,51 @@ # Create an "INFO_SRC" file with information about the source (only). -# We use "bzr version-info", if possible, and the "VERSION" contents. +# We use "git log", if possible, and the "VERSION" contents. # -# Outside development (BZR tree), the "INFO_SRC" file will not be modified +# Outside development (git tree), the "INFO_SRC" file will not be modified # provided it exists (from "make dist" or a source tarball creation). MACRO(CREATE_INFO_SRC target_dir) SET(INFO_SRC "${target_dir}/INFO_SRC") - IF(EXISTS ${CMAKE_SOURCE_DIR}/.bzr) - # Sources are in a BZR repository: Always update. + SET(PERLSCRIPT + "use warnings; use POSIX qw(strftime); " + "print strftime \"%F %T %z\", localtime;") + EXECUTE_PROCESS( + COMMAND perl -e "${PERLSCRIPT}" + RESULT_VARIABLE result + OUTPUT_VARIABLE bdate + ERROR_VARIABLE error + ) + IF(error) + MESSAGE(STATUS "Could not determine build-date: <${error}>") + ENDIF() + + IF(GIT_EXECUTABLE AND EXISTS ${CMAKE_SOURCE_DIR}/.git) + # Sources are in a GIT repository: Always update. EXECUTE_PROCESS( - COMMAND ${BZR_EXECUTABLE} version-info ${CMAKE_SOURCE_DIR} + COMMAND ${GIT_EXECUTABLE} rev-parse --abbrev-ref HEAD + WORKING_DIRECTORY ${CMAKE_SOURCE_DIR} + OUTPUT_VARIABLE bname + ) + + EXECUTE_PROCESS( + COMMAND ${GIT_EXECUTABLE} log -1 + --pretty="commit: %H%ndate: %ci%nbuild-date: ${bdate} %nshort: %h%nbranch: ${bname}" + WORKING_DIRECTORY ${CMAKE_SOURCE_DIR} OUTPUT_VARIABLE VERSION_INFO - RESULT_VARIABLE RESULT ) + + ## Output from git is quoted with "", remove them. + STRING(REPLACE "\"" "" VERSION_INFO "${VERSION_INFO}") FILE(WRITE ${INFO_SRC} "${VERSION_INFO}\n") # to debug, add: FILE(APPEND ${INFO_SRC} "\nResult ${RESULT}\n") # For better readability ... - FILE(APPEND ${INFO_SRC} "\nMySQL source ${VERSION}\n") + FILE(APPEND ${INFO_SRC} + "MySQL source ${MAJOR_VERSION}.${MINOR_VERSION}.${PATCH_VERSION}\n") ELSEIF(EXISTS ${INFO_SRC}) - # Outside a BZR tree, there is no need to change an existing "INFO_SRC", + # Outside a git tree, there is no need to change an existing "INFO_SRC", # it cannot be improved. ELSEIF(EXISTS ${CMAKE_SOURCE_DIR}/Docs/INFO_SRC) # If we are building from a source distribution, it also contains "INFO_SRC". diff -Nru mysql-5.5-5.5.35+dfsg/cmake/info_src.cmake mysql-5.5-5.5.43/cmake/info_src.cmake --- mysql-5.5-5.5.35+dfsg/cmake/info_src.cmake 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/cmake/info_src.cmake 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -# Copyright (c) 2011, Oracle and/or its affiliates. All rights reserved. +# Copyright (c) 2011, 2014, Oracle and/or its affiliates. All rights reserved. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -16,11 +16,11 @@ # The sole purpose of this cmake control file is to create the "INFO_SRC" file. -# As long as and "bzr pull" (or "bzr commit") is followed by a "cmake", +# As long as and "git pull" (or "git commit") is followed by a "cmake", # the call in top level "CMakeLists.txt" is sufficient. # This file is to provide a separate target for the "make" phase, -# to ensure the BZR revision-id is correct even after a sequence -# cmake ; make ; bzr pull ; make +# to ensure the git commit hash is correct even after a sequence +# cmake ; make ; git pull ; make # Get the macros which handle the "INFO_*" files. diff -Nru mysql-5.5-5.5.35+dfsg/cmake/install_macros.cmake mysql-5.5-5.5.43/cmake/install_macros.cmake --- mysql-5.5-5.5.35+dfsg/cmake/install_macros.cmake 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/cmake/install_macros.cmake 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -# Copyright (c) 2009, 2011, Oracle and/or its affiliates. All rights reserved. +# Copyright (c) 2009, 2014, Oracle and/or its affiliates. All rights reserved. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -21,26 +21,35 @@ GET_TARGET_PROPERTY(location ${target} LOCATION) GET_TARGET_PROPERTY(type ${target} TYPE) IF(NOT INSTALL_LOCATION) - IF(type MATCHES "STATIC_LIBRARY" OR type MATCHES "MODULE_LIBRARY" OR type MATCHES "SHARED_LIBRARY") + IF(type MATCHES "STATIC_LIBRARY" + OR type MATCHES "MODULE_LIBRARY" + OR type MATCHES "SHARED_LIBRARY") SET(INSTALL_LOCATION "lib") ELSEIF(type MATCHES "EXECUTABLE") SET(INSTALL_LOCATION "bin") ELSE() - MESSAGE(FATAL_ERROR "cannot determine type of ${target}. Don't now where to install") + MESSAGE(FATAL_ERROR + "cannot determine type of ${target}. Don't now where to install") ENDIF() ENDIF() STRING(REPLACE ".exe" ".pdb" pdb_location ${location}) STRING(REPLACE ".dll" ".pdb" pdb_location ${pdb_location}) STRING(REPLACE ".lib" ".pdb" pdb_location ${pdb_location}) IF(CMAKE_GENERATOR MATCHES "Visual Studio") - STRING(REPLACE "${CMAKE_CFG_INTDIR}" "\${CMAKE_INSTALL_CONFIG_NAME}" pdb_location ${pdb_location}) + STRING(REPLACE + "${CMAKE_CFG_INTDIR}" "\${CMAKE_INSTALL_CONFIG_NAME}" + pdb_location ${pdb_location}) ENDIF() IF(target STREQUAL "mysqld") SET(comp Server) ELSE() SET(comp Debuginfo) ENDIF() - INSTALL(FILES ${pdb_location} DESTINATION ${INSTALL_LOCATION} COMPONENT ${comp}) + # No .pdb file for static libraries. + IF(NOT type MATCHES "STATIC_LIBRARY") + INSTALL(FILES ${pdb_location} + DESTINATION ${INSTALL_LOCATION} COMPONENT ${comp}) + ENDIF() ENDFOREACH() ENDIF() ENDMACRO() @@ -111,28 +120,28 @@ ENDFUNCTION() # Install symbolic link to CMake target. -# the link is created in the same directory as target -# and extension will be the same as for target file. -MACRO(INSTALL_SYMLINK linkname target destination component) +# We do 'cd path; ln -s target_name link_name' +# We also add an INSTALL target for "${path}/${link_name}" +MACRO(INSTALL_SYMLINK target target_name link_name destination component) IF(UNIX) GET_TARGET_PROPERTY(location ${target} LOCATION) GET_FILENAME_COMPONENT(path ${location} PATH) - GET_FILENAME_COMPONENT(name ${location} NAME) - SET(output ${path}/${linkname}) + + SET(output ${path}/${link_name}) ADD_CUSTOM_COMMAND( OUTPUT ${output} COMMAND ${CMAKE_COMMAND} ARGS -E remove -f ${output} COMMAND ${CMAKE_COMMAND} ARGS -E create_symlink - ${name} - ${linkname} + ${target_name} + ${link_name} WORKING_DIRECTORY ${path} DEPENDS ${target} ) - ADD_CUSTOM_TARGET(symlink_${linkname} + ADD_CUSTOM_TARGET(symlink_${link_name} ALL DEPENDS ${output}) - SET_TARGET_PROPERTIES(symlink_${linkname} PROPERTIES CLEAN_DIRECT_OUTPUT 1) + SET_TARGET_PROPERTIES(symlink_${link_name} PROPERTIES CLEAN_DIRECT_OUTPUT 1) IF(CMAKE_GENERATOR MATCHES "Xcode") # For Xcode, replace project config with install config STRING(REPLACE "${CMAKE_CFG_INTDIR}" diff -Nru mysql-5.5-5.5.35+dfsg/cmake/libutils.cmake mysql-5.5-5.5.43/cmake/libutils.cmake --- mysql-5.5-5.5.35+dfsg/cmake/libutils.cmake 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/cmake/libutils.cmake 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -# Copyright (c) 2009, 2010, Oracle and/or its affiliates. All rights reserved. +# Copyright (c) 2009, 2014, Oracle and/or its affiliates. All rights reserved. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -158,6 +158,7 @@ IF(OSLIBS) LIST(REMOVE_DUPLICATES OSLIBS) TARGET_LINK_LIBRARIES(${TARGET} ${OSLIBS}) + MESSAGE(STATUS "Library ${TARGET} depends on OSLIBS ${OSLIBS}") ENDIF() # Make the generated dummy source file depended on all static input diff -Nru mysql-5.5-5.5.35+dfsg/cmake/maintainer.cmake mysql-5.5-5.5.43/cmake/maintainer.cmake --- mysql-5.5-5.5.35+dfsg/cmake/maintainer.cmake 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/cmake/maintainer.cmake 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -# Copyright (c) 2010, 2011, Oracle and/or its affiliates. All rights reserved. +# Copyright (c) 2010, 2014, Oracle and/or its affiliates. All rights reserved. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -13,42 +13,39 @@ # along with this program; if not, write to the Free Software # Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA -INCLUDE(CheckCCompilerFlag) - -# Setup GCC (GNU C compiler) warning options. -MACRO(SET_MYSQL_MAINTAINER_GNU_C_OPTIONS) - SET(MY_MAINTAINER_WARNINGS - "-Wall -Wextra -Wunused -Wwrite-strings -Wno-strict-aliasing -Werror") - CHECK_C_COMPILER_FLAG("-Wdeclaration-after-statement" - HAVE_DECLARATION_AFTER_STATEMENT) - IF(HAVE_DECLARATION_AFTER_STATEMENT) - SET(MY_MAINTAINER_DECLARATION_AFTER_STATEMENT - "-Wdeclaration-after-statement") - ENDIF() - SET(MY_MAINTAINER_C_WARNINGS - "${MY_MAINTAINER_WARNINGS} ${MY_MAINTAINER_DECLARATION_AFTER_STATEMENT}" - CACHE STRING "C warning options used in maintainer builds.") - # Do not make warnings in checks into errors. - SET(CMAKE_REQUIRED_FLAGS "${CMAKE_REQUIRED_FLAGS} -Wno-error") -ENDMACRO() - -# Setup G++ (GNU C++ compiler) warning options. -MACRO(SET_MYSQL_MAINTAINER_GNU_CXX_OPTIONS) - SET(MY_MAINTAINER_CXX_WARNINGS - "${MY_MAINTAINER_WARNINGS} -Wno-unused-parameter -Woverloaded-virtual" - CACHE STRING "C++ warning options used in maintainer builds.") -ENDMACRO() - -# Setup ICC (Intel C Compiler) warning options. -MACRO(SET_MYSQL_MAINTAINER_INTEL_C_OPTIONS) - SET(MY_MAINTAINER_WARNINGS "-Wcheck") - SET(MY_MAINTAINER_C_WARNINGS "${MY_MAINTAINER_WARNINGS}" - CACHE STRING "C warning options used in maintainer builds.") -ENDMACRO() - -# Setup ICPC (Intel C++ Compiler) warning options. -MACRO(SET_MYSQL_MAINTAINER_INTEL_CXX_OPTIONS) - SET(MY_MAINTAINER_CXX_WARNINGS "${MY_MAINTAINER_WARNINGS}" - CACHE STRING "C++ warning options used in maintainer builds.") -ENDMACRO() - +# Common warning flags for GCC, G++, Clang and Clang++ +SET(MY_WARNING_FLAGS "-Wall -Wextra -Wformat-security") +MY_CHECK_C_COMPILER_FLAG("-Wvla" HAVE_WVLA) # Requires GCC 4.3+ or Clang +IF(HAVE_WVLA) + SET(MY_WARNING_FLAGS "${MY_WARNING_FLAGS} -Wvla") +ENDIF() + +# Common warning flags for GCC and Clang +SET(MY_C_WARNING_FLAGS + "${MY_WARNING_FLAGS} -Wwrite-strings -Wdeclaration-after-statement") + +# Common warning flags for G++ and Clang++ +SET(MY_CXX_WARNING_FLAGS + "${MY_WARNING_FLAGS} -Woverloaded-virtual -Wno-unused-parameter") + +# Extra warning flags for Clang++ +IF(CMAKE_CXX_COMPILER_ID MATCHES "Clang") + SET(MY_CXX_WARNING_FLAGS + "${MY_CXX_WARNING_FLAGS} -Wno-null-conversion -Wno-unused-private-field") +ENDIF() + +# Turn on Werror (warning => error) when using maintainer mode. +IF(MYSQL_MAINTAINER_MODE) + SET(MY_C_WARNING_FLAGS "${MY_C_WARNING_FLAGS} -Werror") + SET(MY_CXX_WARNING_FLAGS "${MY_CXX_WARNING_FLAGS} -Werror") + SET(COMPILE_FLAG_WERROR 1) +ENDIF() + +# Set warning flags for GCC/Clang +IF(CMAKE_COMPILER_IS_GNUCC OR CMAKE_C_COMPILER_ID MATCHES "Clang") + SET(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} ${MY_C_WARNING_FLAGS}") +ENDIF() +# Set warning flags for G++/Clang++ +IF(CMAKE_COMPILER_IS_GNUCXX OR CMAKE_CXX_COMPILER_ID MATCHES "Clang") + SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${MY_CXX_WARNING_FLAGS}") +ENDIF() diff -Nru mysql-5.5-5.5.35+dfsg/cmake/make_dist.cmake.in mysql-5.5-5.5.43/cmake/make_dist.cmake.in --- mysql-5.5-5.5.35+dfsg/cmake/make_dist.cmake.in 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/cmake/make_dist.cmake.in 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -# Copyright (c) 2009, 2012, Oracle and/or its affiliates. All rights reserved. +# Copyright (c) 2009, 2014, Oracle and/or its affiliates. All rights reserved. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -14,7 +14,7 @@ # Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA # Make source distribution -# If bzr is present, run bzr export. +# If git is present, run git archive. # Otherwise, just run cpack with source configuration. SET(CMAKE_SOURCE_DIR "@CMAKE_SOURCE_DIR@") @@ -22,13 +22,12 @@ SET(CPACK_SOURCE_PACKAGE_FILE_NAME "@CPACK_SOURCE_PACKAGE_FILE_NAME@") SET(CMAKE_CPACK_COMMAND "@CMAKE_CPACK_COMMAND@") SET(CMAKE_COMMAND "@CMAKE_COMMAND@") -SET(BZR_EXECUTABLE "@BZR_EXECUTABLE@") +SET(GIT_EXECUTABLE "@GIT_EXECUTABLE@") SET(GTAR_EXECUTABLE "@GTAR_EXECUTABLE@") SET(TAR_EXECUTABLE "@TAR_EXECUTABLE@") SET(CMAKE_GENERATOR "@CMAKE_GENERATOR@") SET(CMAKE_MAKE_PROGRAM "@CMAKE_MAKE_PROGRAM@") SET(CMAKE_SYSTEM_NAME "@CMAKE_SYSTEM_NAME@") -SET(PLUGIN_REPOS "@PLUGIN_REPOS@") SET(VERSION "@VERSION@") @@ -40,38 +39,54 @@ FILE(REMOVE_RECURSE ${PACKAGE_DIR}) FILE(REMOVE ${PACKAGE_DIR}.tar.gz ) -IF(BZR_EXECUTABLE) - MESSAGE(STATUS "Running bzr export") +# Only allow git if source dir itself is a git repository +IF(GIT_EXECUTABLE) EXECUTE_PROCESS( - COMMAND "${BZR_EXECUTABLE}" export - ${PACKAGE_DIR} + COMMAND "${GIT_EXECUTABLE}" rev-parse --show-toplevel + OUTPUT_VARIABLE GIT_ROOT + ERROR_VARIABLE GIT_ROOT_ERROR + OUTPUT_STRIP_TRAILING_WHITESPACE WORKING_DIRECTORY ${CMAKE_SOURCE_DIR} RESULT_VARIABLE RESULT ) - IF(NOT RESULT EQUAL 0) - SET(BZR_EXECUTABLE) + IF(NOT RESULT EQUAL 0 OR NOT GIT_ROOT STREQUAL ${CMAKE_SOURCE_DIR}) + MESSAGE(STATUS "This is not a git repository") + SET(GIT_EXECUTABLE) ENDIF() ENDIF() -IF(BZR_EXECUTABLE) - FOREACH(REPO ${PLUGIN_REPOS}) - GET_FILENAME_COMPONENT(PLUGIN_NAME ${REPO} NAME) - SET(DEST ${PACKAGE_DIR}/plugin/${PLUGIN_NAME}) - MESSAGE(STATUS "Running bzr export for plugin/${PLUGIN_NAME}") +IF(GIT_EXECUTABLE) + MESSAGE(STATUS "Running git archive -o ${PACKAGE_DIR}.tar") + EXECUTE_PROCESS( + COMMAND "${GIT_EXECUTABLE}" archive --format=tar + --prefix=${CPACK_SOURCE_PACKAGE_FILE_NAME}/ -o ${PACKAGE_DIR}.tar HEAD + WORKING_DIRECTORY ${CMAKE_SOURCE_DIR} + RESULT_VARIABLE RESULT + ) + IF(NOT RESULT EQUAL 0) + SET(GIT_EXECUTABLE) + ELSE() + # Unpack tarball EXECUTE_PROCESS( - COMMAND "${BZR_EXECUTABLE}" export ${DEST} - WORKING_DIRECTORY ${REPO} - RESULT_VARIABLE RESULT + COMMAND ${CMAKE_COMMAND} -E tar xf ${PACKAGE_DIR}.tar + WORKING_DIRECTORY ${CMAKE_BINARY_DIR} + RESULT_VARIABLE TAR_RESULT ) - IF(NOT RESULT EQUAL 0) - MESSAGE(STATUS "bzr export failed") + IF(NOT TAR_RESULT EQUAL 0) + SET(GIT_EXECUTABLE) + ELSE() + # Remove tarball after unpacking + EXECUTE_PROCESS( + COMMAND ${CMAKE_COMMAND} -E remove ${PACKAGE_DIR}.tar + WORKING_DIRECTORY ${CMAKE_BINARY_DIR} + ) ENDIF() - ENDFOREACH() + ENDIF() ENDIF() -IF(NOT BZR_EXECUTABLE) - MESSAGE(STATUS "bzr not found or source dir is not a repo, use CPack") +IF(NOT GIT_EXECUTABLE) + MESSAGE(STATUS "git not found or source dir is not a repo, use CPack") IF(CMAKE_SOURCE_DIR STREQUAL CMAKE_BINARY_DIR) # In-source build is the worst option, we have to cleanup source tree. diff -Nru mysql-5.5-5.5.35+dfsg/cmake/mysql_version.cmake mysql-5.5-5.5.43/cmake/mysql_version.cmake --- mysql-5.5-5.5.35+dfsg/cmake/mysql_version.cmake 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/cmake/mysql_version.cmake 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -# Copyright (c) 2009, 2012, Oracle and/or its affiliates. All rights reserved. +# Copyright (c) 2009, 2014, Oracle and/or its affiliates. All rights reserved. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -18,6 +18,7 @@ # SET(SHARED_LIB_MAJOR_VERSION "18") +SET(SHARED_LIB_MINOR_VERSION "0") SET(PROTOCOL_VERSION "10") SET(DOT_FRM_VERSION "6") diff -Nru mysql-5.5-5.5.35+dfsg/cmake/os/Darwin.cmake mysql-5.5-5.5.43/cmake/os/Darwin.cmake --- mysql-5.5-5.5.35+dfsg/cmake/os/Darwin.cmake 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/cmake/os/Darwin.cmake 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,4 @@ -# Copyright (c) 2010 Sun Microsystems, Inc. -# Use is subject to license terms. +# Copyright (c) 2010, 2014, Oracle and/or its affiliates. All rights reserved. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -15,21 +14,3 @@ # Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA # This file includes OSX specific options and quirks, related to system checks - -# Workaround for CMake bug#9051 -# (CMake does not pass CMAKE_OSX_SYSROOT and CMAKE_OSX_DEPLOYMENT_TARGET when -# running TRY_COMPILE) - -IF(CMAKE_OSX_SYSROOT) - SET(ENV{CMAKE_OSX_SYSROOT} ${CMAKE_OSX_SYSROOT}) -ENDIF() -IF(CMAKE_OSX_SYSROOT) - SET(ENV{MACOSX_DEPLOYMENT_TARGET} ${OSX_DEPLOYMENT_TARGET}) -ENDIF() - -IF(CMAKE_OSX_DEPLOYMENT_TARGET) - # Workaround linker problems on OSX 10.4 - IF(CMAKE_OSX_DEPLOYMENT_TARGET VERSION_LESS "10.5") - ADD_DEFINITIONS(-fno-common) - ENDIF() -ENDIF() diff -Nru mysql-5.5-5.5.35+dfsg/cmake/os/WindowsCache.cmake mysql-5.5-5.5.43/cmake/os/WindowsCache.cmake --- mysql-5.5-5.5.35+dfsg/cmake/os/WindowsCache.cmake 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/cmake/os/WindowsCache.cmake 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -# Copyright (c) 2010, 2011, Oracle and/or its affiliates. All rights reserved. +# Copyright (c) 2010, 2014, Oracle and/or its affiliates. All rights reserved. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -88,7 +88,7 @@ SET(HAVE_GETRUSAGE CACHE INTERNAL "") SET(HAVE_GETTIMEOFDAY CACHE INTERNAL "") SET(HAVE_GETWD CACHE INTERNAL "") -SET(HAVE_GMTIME_R CACHE INTERNAL "") +SET(HAVE_GMTIME_R 1 CACHE INTERNAL "") SET(HAVE_GRP_H CACHE INTERNAL "") SET(HAVE_IA64INTRIN_H CACHE INTERNAL "") SET(HAVE_IEEEFP_H CACHE INTERNAL "") @@ -109,7 +109,7 @@ SET(HAVE_LDIV 1 CACHE INTERNAL "") SET(HAVE_LIMITS_H 1 CACHE INTERNAL "") SET(HAVE_LOCALE_H 1 CACHE INTERNAL "") -SET(HAVE_LOCALTIME_R CACHE INTERNAL "") +SET(HAVE_LOCALTIME_R 1 CACHE INTERNAL "") SET(HAVE_LOG2 CACHE INTERNAL "") SET(HAVE_LONGJMP 1 CACHE INTERNAL "") SET(HAVE_LRAND48 CACHE INTERNAL "") diff -Nru mysql-5.5-5.5.35+dfsg/cmake/os/Windows.cmake mysql-5.5-5.5.43/cmake/os/Windows.cmake --- mysql-5.5-5.5.35+dfsg/cmake/os/Windows.cmake 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/cmake/os/Windows.cmake 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -# Copyright (c) 2010, 2011, Oracle and/or its affiliates. All rights reserved. +# Copyright (c) 2010, 2014, Oracle and/or its affiliates. All rights reserved. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -62,22 +62,30 @@ ENDIF() IF(MSVC) - # Enable debug info also in Release build, and create PDB to be able to analyze - # crashes - FOREACH(lang C CXX) - SET(CMAKE_${lang}_FLAGS_RELEASE "${CMAKE_${lang}_FLAGS_RELEASE} /Zi") - ENDFOREACH() + # Enable debug info also in Release build, + # and create PDB to be able to analyze crashes. FOREACH(type EXE SHARED MODULE) - SET(CMAKE_{type}_LINKER_FLAGS_RELEASE "${CMAKE_${type}_LINKER_FLAGS_RELEASE} /debug") + SET(CMAKE_{type}_LINKER_FLAGS_RELEASE + "${CMAKE_${type}_LINKER_FLAGS_RELEASE} /debug") ENDFOREACH() # Force static runtime libraries + # - Choose debugging information: + # /Z7 + # Produces an .obj file containing full symbolic debugging + # information for use with the debugger. The symbolic debugging + # information includes the names and types of variables, as well as + # functions and line numbers. No .pdb file is produced by the compiler. + FOREACH(lang C CXX) + SET(CMAKE_${lang}_FLAGS_RELEASE "${CMAKE_${lang}_FLAGS_RELEASE} /Z7") + ENDFOREACH() FOREACH(flag - CMAKE_C_FLAGS_RELEASE CMAKE_C_FLAGS_RELWITHDEBINFO - CMAKE_C_FLAGS_DEBUG CMAKE_C_FLAGS_DEBUG_INIT + CMAKE_C_FLAGS_RELEASE CMAKE_C_FLAGS_RELWITHDEBINFO + CMAKE_C_FLAGS_DEBUG CMAKE_C_FLAGS_DEBUG_INIT CMAKE_CXX_FLAGS_RELEASE CMAKE_CXX_FLAGS_RELWITHDEBINFO - CMAKE_CXX_FLAGS_DEBUG CMAKE_CXX_FLAGS_DEBUG_INIT) + CMAKE_CXX_FLAGS_DEBUG CMAKE_CXX_FLAGS_DEBUG_INIT) STRING(REPLACE "/MD" "/MT" "${flag}" "${${flag}}") + STRING(REPLACE "/Zi" "/Z7" "${flag}" "${${flag}}") ENDFOREACH() # Remove support for exceptions @@ -107,7 +115,6 @@ SET(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} /wd4800 /wd4805 /wd4996") SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} /wd4800 /wd4805 /wd4996 /we4099") - IF(CMAKE_SIZEOF_VOID_P MATCHES 8) # _WIN64 is defined by the compiler itself. # Yet, we define it here again to work around a bug with Intellisense diff -Nru mysql-5.5-5.5.35+dfsg/cmake/plugin.cmake mysql-5.5-5.5.43/cmake/plugin.cmake --- mysql-5.5-5.5.35+dfsg/cmake/plugin.cmake 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/cmake/plugin.cmake 2015-02-27 08:30:34.000000000 +0000 @@ -232,11 +232,4 @@ ADD_SUBDIRECTORY(${dir}) ENDIF() ENDFOREACH() - FOREACH(dir ${dirs_plugin}) - IF (EXISTS ${dir}/.bzr) - MESSAGE(STATUS "Found repo ${dir}/.bzr") - LIST(APPEND PLUGIN_BZR_REPOS "${dir}") - ENDIF() - ENDFOREACH() - SET(PLUGIN_REPOS "${PLUGIN_BZR_REPOS}" CACHE INTERNAL "") ENDMACRO() diff -Nru mysql-5.5-5.5.35+dfsg/cmake/zlib.cmake mysql-5.5-5.5.43/cmake/zlib.cmake --- mysql-5.5-5.5.35+dfsg/cmake/zlib.cmake 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/cmake/zlib.cmake 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,4 @@ -# Copyright (c) 2009 Sun Microsystems, Inc. -# Use is subject to license terms. +# Copyright (c) 2009, 2013, Oracle and/or its affiliates. All rights reserved. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/CMakeLists.txt mysql-5.5-5.5.43/CMakeLists.txt --- mysql-5.5-5.5.35+dfsg/CMakeLists.txt 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/CMakeLists.txt 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -# Copyright (c) 2006, 2013, Oracle and/or its affiliates. All rights reserved. +# Copyright (c) 2006, 2014, Oracle and/or its affiliates. All rights reserved. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -19,8 +19,27 @@ CMAKE_POLICY(VERSION 2.8) endif() +# We use PROPERTIES LINK_INTERFACE_LIBRARIES. See cmake --help-policy CMP0022 +IF(CMAKE_VERSION VERSION_EQUAL "2.8.12" OR + CMAKE_VERSION VERSION_GREATER "2.8.12") + CMAKE_POLICY(SET CMP0022 OLD) +ENDIF() + +# We use the LOCATION target property (CMP0026) +# and get_target_property() for non-existent targets (CMP0045) +# and INSTALL_NAME_DIR (CMP0042) +IF(CMAKE_VERSION VERSION_EQUAL "3.0.0" OR + CMAKE_VERSION VERSION_GREATER "3.0.0") + CMAKE_POLICY(SET CMP0026 OLD) + CMAKE_POLICY(SET CMP0045 OLD) + CMAKE_POLICY(SET CMP0042 OLD) +ENDIF() + MESSAGE(STATUS "Running cmake version ${CMAKE_VERSION}") +# Will set GIT_EXECUTABLE and GIT_FOUND +FIND_PACKAGE(Git) + SET(CMAKE_MODULE_PATH ${CMAKE_MODULE_PATH} ${CMAKE_SOURCE_DIR}/cmake) # First, decide about build type (debug or release) @@ -59,11 +78,9 @@ SET(BUILDTYPE_DOCSTRING "Choose the type of build, options are: None(CMAKE_CXX_FLAGS or CMAKE_C_FLAGS used) Debug Release RelWithDebInfo MinSizeRel") - + IF(WITH_DEBUG) SET(CMAKE_BUILD_TYPE "Debug" CACHE STRING ${BUILDTYPE_DOCSTRING} FORCE) - SET(MYSQL_MAINTAINER_MODE ON CACHE BOOL - "MySQL maintainer-specific development environment") IF(UNIX AND NOT APPLE) # Compiling with PIC speeds up embedded build, on PIC sensitive systems # Predefine it to ON, in case user chooses to build embedded. @@ -93,6 +110,15 @@ ENDIF() PROJECT(${MYSQL_PROJECT_NAME}) +# Maintainer mode is default on only for Linux debug builds using GCC/G++ +IF(CMAKE_BUILD_TYPE MATCHES "Debug" OR WITH_DEBUG) + IF(CMAKE_SYSTEM_NAME MATCHES "Linux" AND + CMAKE_COMPILER_IS_GNUCC AND CMAKE_COMPILER_IS_GNUCXX) + SET(MYSQL_MAINTAINER_MODE ON CACHE BOOL + "MySQL maintainer-specific development environment") + ENDIF() +ENDIF() + IF(BUILD_CONFIG) INCLUDE( ${CMAKE_SOURCE_DIR}/cmake/build_configurations/${BUILD_CONFIG}.cmake) @@ -116,38 +142,12 @@ ENDFOREACH() - # Following autotools tradition, add preprocessor definitions # specified in environment variable CPPFLAGS IF(DEFINED ENV{CPPFLAGS}) ADD_DEFINITIONS($ENV{CPPFLAGS}) ENDIF() -# -# Control aspects of the development environment which are -# specific to MySQL maintainers and developers. -# -INCLUDE(maintainer) - -OPTION(MYSQL_MAINTAINER_MODE - "MySQL maintainer-specific development environment" OFF) - -# Whether the maintainer mode compiler options should be enabled. -IF(MYSQL_MAINTAINER_MODE) - IF(CMAKE_C_COMPILER_ID MATCHES "GNU") - SET_MYSQL_MAINTAINER_GNU_C_OPTIONS() - ENDIF() - IF(CMAKE_CXX_COMPILER_ID MATCHES "GNU") - SET_MYSQL_MAINTAINER_GNU_CXX_OPTIONS() - ENDIF() - IF(CMAKE_C_COMPILER_ID MATCHES "Intel") - SET_MYSQL_MAINTAINER_INTEL_C_OPTIONS() - ENDIF() - IF(CMAKE_CXX_COMPILER_ID MATCHES "Intel") - SET_MYSQL_MAINTAINER_INTEL_CXX_OPTIONS() - ENDIF() -ENDIF() - # Add macros INCLUDE(character_sets) INCLUDE(zlib) @@ -178,7 +178,6 @@ MARK_AS_ADVANCED(CYBOZU BACKUP_TEST WITHOUT_SERVER DISABLE_SHARED) - include(CheckCSourceCompiles) include(CheckCXXSourceCompiles) # We need some extra FAIL_REGEX patterns @@ -329,6 +328,16 @@ SET(DEFAULT_SYSCONFDIR "${SYSCONFDIR}") ENDIF() +SET(TMPDIR "P_tmpdir" + CACHE PATH + "PATH to MySQL TMP dir. Defaults to the P_tmpdir macro in ") +IF(TMPDIR STREQUAL "P_tmpdir") + # Do not quote it, to refer to the P_tmpdir macro. + SET(DEFAULT_TMPDIR "P_tmpdir") +ELSE() + # Quote it, to make it a const char string. + SET(DEFAULT_TMPDIR "\"${TMPDIR}\"") +ENDIF() # Run platform tests INCLUDE(configure.cmake) @@ -349,13 +358,13 @@ # not run with the warning options as to not perturb fragile checks # (i.e. do not make warnings into errors). # -IF(MYSQL_MAINTAINER_MODE) - # Set compiler flags required under maintainer mode. - MESSAGE(STATUS "C warning options: ${MY_MAINTAINER_C_WARNINGS}") - SET(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} ${MY_MAINTAINER_C_WARNINGS}") - MESSAGE(STATUS "C++ warning options: ${MY_MAINTAINER_CXX_WARNINGS}") - SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${MY_MAINTAINER_CXX_WARNINGS}") -ENDIF() +# Why doesn't these flags affect the entire build? +# Because things may already have been included with ADD_SUBDIRECTORY +# +OPTION(MYSQL_MAINTAINER_MODE + "MySQL maintainer-specific development environment" OFF) + +INCLUDE(maintainer) IF(NOT WITHOUT_SERVER) SET (MYSQLD_STATIC_PLUGIN_LIBS "" CACHE INTERNAL "") @@ -371,7 +380,6 @@ ADD_SUBDIRECTORY(mysys) ADD_SUBDIRECTORY(libmysql) - IF(WITH_UNIT_TESTS) ENABLE_TESTING() ENDIF() @@ -405,7 +413,8 @@ IF(EXISTS ${CMAKE_SOURCE_DIR}/internal/CMakeLists.txt) ADD_SUBDIRECTORY(internal) ENDIF() - ADD_SUBDIRECTORY(packaging/rpm-uln) + ADD_SUBDIRECTORY(packaging/rpm-oel) + ADD_SUBDIRECTORY(packaging/rpm-sles) ENDIF() INCLUDE(cmake/abi_check.cmake) @@ -418,13 +427,14 @@ CONFIGURE_FILE(${CMAKE_SOURCE_DIR}/sql/sql_builtin.cc.in ${CMAKE_BINARY_DIR}/sql/sql_builtin.cc) CONFIGURE_FILE( - ${CMAKE_SOURCE_DIR}/cmake/info_macros.cmake.in ${CMAKE_BINARY_DIR}/info_macros.cmake @ONLY) + ${CMAKE_SOURCE_DIR}/cmake/info_macros.cmake.in + ${CMAKE_BINARY_DIR}/info_macros.cmake @ONLY) # Handle the "INFO_*" files. INCLUDE(${CMAKE_BINARY_DIR}/info_macros.cmake) # Source: This can be done during the cmake phase, all information is # available, but should be repeated on each "make" just in case someone -# does "cmake ; make ; bzr pull ; make". +# does "cmake ; make ; git pull ; make". CREATE_INFO_SRC(${CMAKE_BINARY_DIR}/Docs) ADD_CUSTOM_TARGET(INFO_SRC ALL COMMAND ${CMAKE_COMMAND} -P ${CMAKE_SOURCE_DIR}/cmake/info_src.cmake @@ -463,7 +473,6 @@ ) INSTALL(FILES README DESTINATION ${INSTALL_DOCREADMEDIR} COMPONENT Readme) INSTALL(FILES ${CMAKE_BINARY_DIR}/Docs/INFO_SRC ${CMAKE_BINARY_DIR}/Docs/INFO_BIN DESTINATION ${INSTALL_DOCDIR}) - IF(UNIX) INSTALL(FILES Docs/INSTALL-BINARY DESTINATION ${INSTALL_DOCREADMEDIR} COMPONENT Readme) ENDIF() @@ -483,3 +492,37 @@ ENDIF() INCLUDE(CPack) + +# C compiler flags consist of: +# CPPFLAGS Taken from environment, see above. +# ADD_DEFINITIONS In each individual CMakeLists.txt +# CMAKE_C_FLAGS From command line. +# We extend these in maintainer.cmake +# ENV{CFLAGS} From environment, but environment is ignored if +# CMAKE_C_FLAGS is also given on command line +# CMAKE_C_FLAGS_${CMAKE_BUILD_TYPE} +# We extend these in compiler_options.cmake +# +# Note that CMakeCache.txt contains cmake builtins for these variables, +# *not* the values that will actually be used: + +IF(CMAKE_GENERATOR MATCHES "Makefiles") + MESSAGE(STATUS "CMAKE_BUILD_TYPE: ${CMAKE_BUILD_TYPE}") +ENDIF() +GET_PROPERTY(cwd_definitions DIRECTORY PROPERTY COMPILE_DEFINITIONS) +MESSAGE(STATUS "COMPILE_DEFINITIONS: ${cwd_definitions}") +MESSAGE(STATUS "CMAKE_C_FLAGS: ${CMAKE_C_FLAGS}") +MESSAGE(STATUS "CMAKE_CXX_FLAGS: ${CMAKE_CXX_FLAGS}") +IF(CMAKE_BUILD_TYPE AND CMAKE_GENERATOR MATCHES "Makefiles") + STRING(TOUPPER "${CMAKE_BUILD_TYPE}" CMAKEBT) + MESSAGE(STATUS "CMAKE_C_FLAGS_${CMAKEBT}: ${CMAKE_C_FLAGS_${CMAKEBT}}") + MESSAGE(STATUS "CMAKE_CXX_FLAGS_${CMAKEBT}: ${CMAKE_CXX_FLAGS_${CMAKEBT}}") +ENDIF() +IF(NOT CMAKE_GENERATOR MATCHES "Makefiles") + MESSAGE(STATUS "CMAKE_C_FLAGS_DEBUG: ${CMAKE_C_FLAGS_DEBUG}") + MESSAGE(STATUS "CMAKE_CXX_FLAGS_DEBUG: ${CMAKE_CXX_FLAGS_DEBUG}") + MESSAGE(STATUS + "CMAKE_C_FLAGS_RELWITHDEBINFO: ${CMAKE_C_FLAGS_RELWITHDEBINFO}") + MESSAGE(STATUS + "CMAKE_CXX_FLAGS_RELWITHDEBINFO: ${CMAKE_CXX_FLAGS_RELWITHDEBINFO}") +ENDIF() diff -Nru mysql-5.5-5.5.35+dfsg/config.h.cmake mysql-5.5-5.5.43/config.h.cmake --- mysql-5.5-5.5.35+dfsg/config.h.cmake 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/config.h.cmake 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -/* Copyright (c) 2009, 2011, Oracle and/or its affiliates. All rights reserved. +/* Copyright (c) 2009, 2013, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -600,6 +600,7 @@ #cmakedefine DEFAULT_CHARSET_HOME "@DEFAULT_CHARSET_HOME@" #cmakedefine PLUGINDIR "@PLUGINDIR@" #cmakedefine DEFAULT_SYSCONFDIR "@DEFAULT_SYSCONFDIR@" +#cmakedefine DEFAULT_TMPDIR @DEFAULT_TMPDIR@ #cmakedefine SO_EXT "@CMAKE_SHARED_MODULE_SUFFIX@" diff -Nru mysql-5.5-5.5.35+dfsg/configure.cmake mysql-5.5-5.5.43/configure.cmake --- mysql-5.5-5.5.35+dfsg/configure.cmake 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/configure.cmake 2015-02-27 08:30:34.000000000 +0000 @@ -53,15 +53,6 @@ ENDIF() -# Always enable -Wall for gnu C/C++ -IF(CMAKE_COMPILER_IS_GNUCXX) - SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wall -Wno-unused-parameter") -ENDIF() -IF(CMAKE_COMPILER_IS_GNUCC) - SET(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wall") -ENDIF() - - IF(CMAKE_COMPILER_IS_GNUCXX) # MySQL "canonical" GCC flags. At least -fno-rtti flag affects # ABI and cannot be simply removed. diff -Nru mysql-5.5-5.5.35+dfsg/debian/changelog mysql-5.5-5.5.43/debian/changelog --- mysql-5.5-5.5.35+dfsg/debian/changelog 2014-02-19 21:19:52.000000000 +0000 +++ mysql-5.5-5.5.43/debian/changelog 2015-06-15 18:11:41.000000000 +0000 @@ -1,3 +1,71 @@ +mysql-5.5 (5.5.43-0ubuntu0.14.04.2) trusty-proposed; urgency=medium + + * Introduce full memory barrier support for arm64 and ppc64el to fix + corruption/hang issues (LP: #1427406). + + -- dann frazier Mon, 15 Jun 2015 12:11:36 -0600 + +mysql-5.5 (5.5.43-0ubuntu0.14.04.1) trusty-security; urgency=medium + + * SECURITY UPDATE: Update to 5.5.43 to fix security issues (LP: #1444616) + - http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html + - CVE-2015-0433 + - CVE-2015-0441 + - CVE-2015-0499 + - CVE-2015-0501 + - CVE-2015-0505 + - CVE-2015-2568 + - CVE-2015-2571 + - CVE-2015-2573 + + -- Marc Deslauriers Mon, 20 Apr 2015 09:30:47 -0400 + +mysql-5.5 (5.5.41-0ubuntu0.14.04.1) trusty-security; urgency=medium + + * SECURITY UPDATE: Update to 5.5.41 to fix security issues (LP: #1413188) + - http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html + - CVE-2014-6568 + - CVE-2015-0374 + - CVE-2015-0381 + - CVE-2015-0382 + - CVE-2015-0411 + - CVE-2015-0432 + + -- Marc Deslauriers Wed, 21 Jan 2015 11:49:48 -0500 + +mysql-5.5 (5.5.40-0ubuntu0.14.04.1) trusty-security; urgency=medium + + * SECURITY UPDATE: Update to 5.5.40 to fix security issues (LP: #1379903) + + -- Marc Deslauriers Fri, 10 Oct 2014 14:57:34 -0400 + +mysql-5.5 (5.5.38-0ubuntu0.14.04.1) trusty-security; urgency=medium + + * SECURITY UPDATE: Update to 5.5.38 to fix security issues (LP: #1342709) + - http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html + - CVE-2014-2494 + - CVE-2014-4207 + - CVE-2014-4258 + - CVE-2014-4260 + + -- Marc Deslauriers Wed, 16 Jul 2014 11:39:56 -0400 + +mysql-5.5 (5.5.37-0ubuntu0.14.04.1) trusty-security; urgency=medium + + * SECURITY UPDATE: Update to 5.5.37 to fix security issues (LP: #1309662) + - http://www.oracle.com/technetwork/topics/security/cpuapr2014-1972952.html + - CVE-2014-0001 + - CVE-2014-0384 + - CVE-2014-2419 + - CVE-2014-2430 + - CVE-2014-2431 + - CVE-2014-2432 + - CVE-2014-2436 + - CVE-2014-2438 + - CVE-2014-2440 + + -- Marc Deslauriers Fri, 18 Apr 2014 13:37:55 -0400 + mysql-5.5 (5.5.35+dfsg-1ubuntu1) trusty; urgency=low * Merge from Debian unstable. diff -Nru mysql-5.5-5.5.35+dfsg/debian/control mysql-5.5-5.5.43/debian/control --- mysql-5.5-5.5.35+dfsg/debian/control 2014-02-19 21:19:52.000000000 +0000 +++ mysql-5.5-5.5.43/debian/control 2015-06-15 18:11:08.000000000 +0000 @@ -25,6 +25,7 @@ perl, po-debconf, psmisc, + quilt, zlib1g-dev (>= 1:1.1.3-5) Standards-Version: 3.9.5 Homepage: http://dev.mysql.com/ diff -Nru mysql-5.5-5.5.35+dfsg/debian/patches/arch-specific/Bug-11755438-Bug-47213-INNODB-MUTEX-RW_LOCK-SHOULD-B.patch mysql-5.5-5.5.43/debian/patches/arch-specific/Bug-11755438-Bug-47213-INNODB-MUTEX-RW_LOCK-SHOULD-B.patch --- mysql-5.5-5.5.35+dfsg/debian/patches/arch-specific/Bug-11755438-Bug-47213-INNODB-MUTEX-RW_LOCK-SHOULD-B.patch 1970-01-01 00:00:00.000000000 +0000 +++ mysql-5.5-5.5.43/debian/patches/arch-specific/Bug-11755438-Bug-47213-INNODB-MUTEX-RW_LOCK-SHOULD-B.patch 2015-06-15 18:11:08.000000000 +0000 @@ -0,0 +1,438 @@ +From: Yasufumi Kinoshita +Subject: [PATCH] Bug#11755438: Bug#47213: INNODB MUTEX/RW_LOCK SHOULD BE + CONSCIOUS ABOUT MEMORY ORDERING OTHER THAN INTEL + +Because of difference about memory ordering, some critical flags of mutex/rw_lock might be missed to read on non-Intel CPUs. +Even for Intel-CPUs, the explicit memory barrier instruction might cause positive effects for performance. + +Approved by Kevin Lewis in rb#5561 + +Bug-Ubuntu: https://bugs.launchpad.net/bugs/1427406 +Origin: https://github.com/mysql/mysql-server/commit/19b3f570fcd91be13eb8e29256a458f4d45942c5 +Last-Update: 2015-06-12 + +diff -urpN a/storage/innobase/CMakeLists.txt b/storage/innobase/CMakeLists.txt +--- a/storage/innobase/CMakeLists.txt 2015-02-27 01:30:34.000000000 -0700 ++++ b/storage/innobase/CMakeLists.txt 2015-06-12 14:17:07.952227810 -0600 +@@ -54,7 +54,6 @@ IF(NOT CMAKE_CROSSCOMPILING) + long x; + long y; + long res; +- char c; + + x = 10; + y = 123; +@@ -75,6 +74,16 @@ IF(NOT CMAKE_CROSSCOMPILING) + if (res != 123 + 10 || x != 123 + 10) { + return(1); + } ++ return(0); ++ }" ++ HAVE_IB_GCC_ATOMIC_BUILTINS_BYTE ++ ) ++ CHECK_C_SOURCE_RUNS( ++ " ++ int main() ++ { ++ long res; ++ char c; + + c = 10; + res = __sync_lock_test_and_set(&c, 123); +@@ -85,12 +94,43 @@ IF(NOT CMAKE_CROSSCOMPILING) + }" + HAVE_IB_GCC_ATOMIC_BUILTINS + ) ++ CHECK_C_SOURCE_RUNS( ++ "#include ++ int main() ++ { ++ __sync_synchronize(); ++ return(0); ++ }" ++ HAVE_IB_GCC_SYNC_SYNCHRONISE ++ ) ++ CHECK_C_SOURCE_RUNS( ++ "#include ++ int main() ++ { ++ __atomic_thread_fence(__ATOMIC_ACQUIRE); ++ __atomic_thread_fence(__ATOMIC_RELEASE); ++ return(0); ++ }" ++ HAVE_IB_GCC_ATOMIC_THREAD_FENCE ++ ) + ENDIF() + + IF(HAVE_IB_GCC_ATOMIC_BUILTINS) + ADD_DEFINITIONS(-DHAVE_IB_GCC_ATOMIC_BUILTINS=1) + ENDIF() + ++IF(HAVE_IB_GCC_ATOMIC_BUILTINS_BYTE) ++ ADD_DEFINITIONS(-DHAVE_IB_GCC_ATOMIC_BUILTINS_BYTE=1) ++ENDIF() ++ ++IF(HAVE_IB_GCC_SYNC_SYNCHRONISE) ++ ADD_DEFINITIONS(-DHAVE_IB_GCC_SYNC_SYNCHRONISE=1) ++ENDIF() ++ ++IF(HAVE_IB_GCC_ATOMIC_THREAD_FENCE) ++ ADD_DEFINITIONS(-DHAVE_IB_GCC_ATOMIC_THREAD_FENCE=1) ++ENDIF() ++ + # either define HAVE_IB_ATOMIC_PTHREAD_T_GCC or not + IF(NOT CMAKE_CROSSCOMPILING) + CHECK_C_SOURCE_RUNS( +@@ -169,10 +209,21 @@ IF(CMAKE_SYSTEM_NAME STREQUAL "SunOS") + return(0); + } + " HAVE_IB_ATOMIC_PTHREAD_T_SOLARIS) ++ CHECK_C_SOURCE_COMPILES( ++ "#include ++ int main() { ++ __machine_r_barrier(); ++ __machine_w_barrier(); ++ return(0); ++ }" ++ HAVE_IB_MACHINE_BARRIER_SOLARIS) + ENDIF() + IF(HAVE_IB_ATOMIC_PTHREAD_T_SOLARIS) + ADD_DEFINITIONS(-DHAVE_IB_ATOMIC_PTHREAD_T_SOLARIS=1) + ENDIF() ++ IF(HAVE_IB_MACHINE_BARRIER_SOLARIS) ++ ADD_DEFINITIONS(-DHAVE_IB_MACHINE_BARRIER_SOLARIS=1) ++ ENDIF() + ENDIF() + + +@@ -190,6 +241,7 @@ ENDIF() + + IF(MSVC) + ADD_DEFINITIONS(-DHAVE_WINDOWS_ATOMICS) ++ ADD_DEFINITIONS(-DHAVE_WINDOWS_MM_FENCE) + ENDIF() + + +diff -urpN a/storage/innobase/include/os0sync.h b/storage/innobase/include/os0sync.h +--- a/storage/innobase/include/os0sync.h 2015-02-27 01:30:34.000000000 -0700 ++++ b/storage/innobase/include/os0sync.h 2015-06-12 14:20:25.448406822 -0600 +@@ -267,6 +267,10 @@ Atomic compare-and-swap and increment fo + + #define HAVE_ATOMIC_BUILTINS + ++#ifdef HAVE_IB_GCC_ATOMIC_BUILTINS_BYTE ++# define HAVE_ATOMIC_BUILTINS_BYTE ++#endif ++ + /**********************************************************//** + Returns true if swapped, ptr is pointer to target, old_val is value to + compare to, new_val is the value to swap in. */ +@@ -313,6 +317,7 @@ Returns the old value of *ptr, atomicall + #elif defined(HAVE_IB_SOLARIS_ATOMICS) + + #define HAVE_ATOMIC_BUILTINS ++#define HAVE_ATOMIC_BUILTINS_BYTE + + /* If not compiling with GCC or GCC doesn't support the atomic + intrinsics and running on Solaris >= 10 use Solaris atomics */ +@@ -366,6 +371,7 @@ Returns the old value of *ptr, atomicall + #elif defined(HAVE_WINDOWS_ATOMICS) + + #define HAVE_ATOMIC_BUILTINS ++#define HAVE_ATOMIC_BUILTINS_BYTE + + /* On Windows, use Windows atomics / interlocked */ + # ifdef _WIN64 +@@ -416,6 +422,52 @@ clobbered */ + "Mutexes and rw_locks use InnoDB's own implementation" + #endif + ++/** barrier definitions for memory ordering */ ++#ifdef HAVE_IB_GCC_ATOMIC_THREAD_FENCE ++# define HAVE_MEMORY_BARRIER ++# define os_rmb __atomic_thread_fence(__ATOMIC_ACQUIRE) ++# define os_wmb __atomic_thread_fence(__ATOMIC_RELEASE) ++# define IB_MEMORY_BARRIER_STARTUP_MSG \ ++ "GCC builtin __atomic_thread_fence() is used for memory barrier" ++ ++#elif defined(HAVE_IB_GCC_SYNC_SYNCHRONISE) ++# define HAVE_MEMORY_BARRIER ++# define os_rmb __sync_synchronize() ++# define os_wmb __sync_synchronize() ++# define IB_MEMORY_BARRIER_STARTUP_MSG \ ++ "GCC builtin __sync_synchronize() is used for memory barrier" ++ ++#elif defined(HAVE_IB_MACHINE_BARRIER_SOLARIS) ++# define HAVE_MEMORY_BARRIER ++# include ++# define os_rmb __machine_r_barrier() ++# define os_wmb __machine_w_barrier() ++# define IB_MEMORY_BARRIER_STARTUP_MSG \ ++ "Solaris memory ordering functions are used for memory barrier" ++ ++#elif defined(HAVE_WINDOWS_MM_FENCE) ++# define HAVE_MEMORY_BARRIER ++# include ++# define os_rmb _mm_lfence() ++# define os_wmb _mm_sfence() ++# define IB_MEMORY_BARRIER_STARTUP_MSG \ ++ "_mm_lfence() and _mm_sfence() are used for memory barrier" ++ ++#else ++# define os_rmb ++# define os_wmb ++# define IB_MEMORY_BARRIER_STARTUP_MSG \ ++ "Memory barrier is not used" ++#endif ++ ++/* internal counter for innodb_sync_spin_loops is adjusted ++because memory barrier is more expensive than an empty loop. */ ++#ifdef HAVE_MEMORY_BARRIER ++# define SPIN_WAIT_INCREMENT 2 ++#else ++# define SPIN_WAIT_INCREMENT 1 ++#endif /* HAVE_MEMORY_BARRIER */ ++ + #ifndef UNIV_NONINL + #include "os0sync.ic" + #endif +diff -urpN a/storage/innobase/include/sync0rw.ic b/storage/innobase/include/sync0rw.ic +--- a/storage/innobase/include/sync0rw.ic 2015-02-27 01:30:34.000000000 -0700 ++++ b/storage/innobase/include/sync0rw.ic 2015-06-12 14:21:41.593405957 -0600 +@@ -93,6 +93,7 @@ rw_lock_set_waiter_flag( + (void) os_compare_and_swap_ulint(&lock->waiters, 0, 1); + #else /* INNODB_RW_LOCKS_USE_ATOMICS */ + lock->waiters = 1; ++ os_wmb; + #endif /* INNODB_RW_LOCKS_USE_ATOMICS */ + } + +@@ -110,6 +111,7 @@ rw_lock_reset_waiter_flag( + (void) os_compare_and_swap_ulint(&lock->waiters, 1, 0); + #else /* INNODB_RW_LOCKS_USE_ATOMICS */ + lock->waiters = 0; ++ os_wmb; + #endif /* INNODB_RW_LOCKS_USE_ATOMICS */ + } + +@@ -200,7 +202,10 @@ rw_lock_lock_word_decr( + ulint amount) /*!< in: amount to decrement */ + { + #ifdef INNODB_RW_LOCKS_USE_ATOMICS +- lint local_lock_word = lock->lock_word; ++ lint local_lock_word; ++ ++ os_rmb; ++ local_lock_word = lock->lock_word; + while (local_lock_word > 0) { + if (os_compare_and_swap_lint(&lock->lock_word, + local_lock_word, +diff -urpN a/storage/innobase/include/sync0sync.h b/storage/innobase/include/sync0sync.h +--- a/storage/innobase/include/sync0sync.h 2015-02-27 01:30:34.000000000 -0700 ++++ b/storage/innobase/include/sync0sync.h 2015-06-12 14:28:13.297014889 -0600 +@@ -48,6 +48,8 @@ extern my_bool timed_mutexes; + #ifdef HAVE_WINDOWS_ATOMICS + typedef LONG lock_word_t; /*!< On Windows, InterlockedExchange operates + on LONG variable */ ++#elif defined(HAVE_ATOMIC_BUILTINS) && !defined(HAVE_ATOMIC_BUILTINS_BYTE) ++typedef ulint lock_word_t; + #else + typedef byte lock_word_t; + #endif +diff -urpN a/storage/innobase/include/sync0sync.ic b/storage/innobase/include/sync0sync.ic +--- a/storage/innobase/include/sync0sync.ic 2015-02-27 01:30:34.000000000 -0700 ++++ b/storage/innobase/include/sync0sync.ic 2015-06-12 14:29:58.239813599 -0600 +@@ -80,7 +80,11 @@ mutex_test_and_set( + mutex_t* mutex) /*!< in: mutex */ + { + #if defined(HAVE_ATOMIC_BUILTINS) ++# if defined(HAVE_ATOMIC_BUILTINS_BYTE) + return(os_atomic_test_and_set_byte(&mutex->lock_word, 1)); ++# else ++ return(os_atomic_test_and_set_ulint(&mutex->lock_word, 1)); ++# endif + #else + ibool ret; + +@@ -92,6 +96,7 @@ mutex_test_and_set( + ut_a(mutex->lock_word == 0); + + mutex->lock_word = 1; ++ os_wmb; + } + + return((byte)ret); +@@ -111,7 +116,11 @@ mutex_reset_lock_word( + /* In theory __sync_lock_release should be used to release the lock. + Unfortunately, it does not work properly alone. The workaround is + that more conservative __sync_lock_test_and_set is used instead. */ ++# if defined(HAVE_ATOMIC_BUILTINS_BYTE) + os_atomic_test_and_set_byte(&mutex->lock_word, 0); ++# else ++ os_atomic_test_and_set_ulint(&mutex->lock_word, 0); ++# endif + #else + mutex->lock_word = 0; + +diff -urpN a/storage/innobase/srv/srv0start.c b/storage/innobase/srv/srv0start.c +--- a/storage/innobase/srv/srv0start.c 2015-02-27 01:30:34.000000000 -0700 ++++ b/storage/innobase/srv/srv0start.c 2015-06-12 14:33:14.906224837 -0600 +@@ -1153,6 +1153,18 @@ innobase_start_or_create_for_mysql(void) + ut_print_timestamp(stderr); + fputs(" InnoDB: " IB_ATOMICS_STARTUP_MSG "\n", stderr); + ++ fputs(" InnoDB: " IB_MEMORY_BARRIER_STARTUP_MSG "\n", stderr); ++ ++#ifndef HAVE_MEMORY_BARRIER ++#if defined __i386__ || defined __x86_64__ || defined _M_IX86 || defined _M_X64 ++#else ++ ib_logf(IB_LOG_LEVEL_WARN, ++ "MySQL was built without a memory barrier capability on this" ++ " architecture, which might allow a mutex/rw_lock violation" ++ " under high thread concurrency. This may cause a hang."); ++#endif /* IA32 or AMD64 */ ++#endif /* HAVE_MEMORY_BARRIER */ ++ + ut_print_timestamp(stderr); + fputs(" InnoDB: Compressed tables use zlib " ZLIB_VERSION + #ifdef UNIV_ZIP_DEBUG +diff -urpN a/storage/innobase/sync/sync0arr.c b/storage/innobase/sync/sync0arr.c +--- a/storage/innobase/sync/sync0arr.c 2015-02-27 01:30:34.000000000 -0700 ++++ b/storage/innobase/sync/sync0arr.c 2015-06-12 14:41:38.481091057 -0600 +@@ -776,6 +776,7 @@ sync_arr_cell_can_wake_up( + + mutex = cell->wait_object; + ++ os_rmb; + if (mutex_get_lock_word(mutex) == 0) { + + return(TRUE); +@@ -785,6 +786,7 @@ sync_arr_cell_can_wake_up( + + lock = cell->wait_object; + ++ os_rmb; + if (lock->lock_word > 0) { + /* Either unlocked or only read locked. */ + +@@ -796,6 +798,7 @@ sync_arr_cell_can_wake_up( + lock = cell->wait_object; + + /* lock_word == 0 means all readers have left */ ++ os_rmb; + if (lock->lock_word == 0) { + + return(TRUE); +@@ -804,6 +807,7 @@ sync_arr_cell_can_wake_up( + lock = cell->wait_object; + + /* lock_word > 0 means no writer or reserved writer */ ++ os_rmb; + if (lock->lock_word > 0) { + + return(TRUE); +diff -urpN a/storage/innobase/sync/sync0rw.c b/storage/innobase/sync/sync0rw.c +--- a/storage/innobase/sync/sync0rw.c 2015-02-27 01:30:34.000000000 -0700 ++++ b/storage/innobase/sync/sync0rw.c 2015-06-12 14:45:26.785074328 -0600 +@@ -390,15 +390,17 @@ rw_lock_s_lock_spin( + lock_loop: + + /* Spin waiting for the writer field to become free */ ++ os_rmb; + while (i < SYNC_SPIN_ROUNDS && lock->lock_word <= 0) { + if (srv_spin_wait_delay) { + ut_delay(ut_rnd_interval(0, srv_spin_wait_delay)); + } + +- i++; ++ i += SPIN_WAIT_INCREMENT; ++ os_rmb; + } + +- if (i == SYNC_SPIN_ROUNDS) { ++ if (i >= SYNC_SPIN_ROUNDS) { + os_thread_yield(); + } + +@@ -498,6 +500,7 @@ rw_lock_x_lock_wait( + ulint index; + ulint i = 0; + ++ os_rmb; + ut_ad(lock->lock_word <= 0); + + while (lock->lock_word < 0) { +@@ -505,7 +508,8 @@ rw_lock_x_lock_wait( + ut_delay(ut_rnd_interval(0, srv_spin_wait_delay)); + } + if(i < SYNC_SPIN_ROUNDS) { +- i++; ++ i += SPIN_WAIT_INCREMENT; ++ os_rmb; + continue; + } + +@@ -582,6 +586,10 @@ rw_lock_x_lock_low( + file_name, line); + + } else { ++ if (!pass) { ++ os_rmb; ++ } ++ + /* Decrement failed: relock or failed lock */ + if (!pass && lock->recursive + && os_thread_eq(lock->writer_thread, curr_thread)) { +@@ -647,6 +655,7 @@ lock_loop: + } + + /* Spin waiting for the lock_word to become free */ ++ os_rmb; + while (i < SYNC_SPIN_ROUNDS + && lock->lock_word <= 0) { + if (srv_spin_wait_delay) { +@@ -654,9 +663,10 @@ lock_loop: + srv_spin_wait_delay)); + } + +- i++; ++ i += SPIN_WAIT_INCREMENT; ++ os_rmb; + } +- if (i == SYNC_SPIN_ROUNDS) { ++ if (i >= SYNC_SPIN_ROUNDS) { + os_thread_yield(); + } else { + goto lock_loop; +diff -urpN a/storage/innobase/sync/sync0sync.c b/storage/innobase/sync/sync0sync.c +--- a/storage/innobase/sync/sync0sync.c 2015-02-27 01:30:34.000000000 -0700 ++++ b/storage/innobase/sync/sync0sync.c 2015-06-12 14:47:23.196895662 -0600 +@@ -472,6 +472,7 @@ mutex_set_waiters( + + *ptr = n; /* Here we assume that the write of a single + word in memory is atomic */ ++ os_wmb; + } + + /******************************************************************//** +@@ -516,16 +517,17 @@ mutex_loop: + + spin_loop: + ut_d(mutex->count_spin_loop++); +- ++ os_rmb; + while (mutex_get_lock_word(mutex) != 0 && i < SYNC_SPIN_ROUNDS) { + if (srv_spin_wait_delay) { + ut_delay(ut_rnd_interval(0, srv_spin_wait_delay)); + } + +- i++; ++ i += SPIN_WAIT_INCREMENT; ++ os_rmb; + } + +- if (i == SYNC_SPIN_ROUNDS) { ++ if (i >= SYNC_SPIN_ROUNDS) { + #ifdef UNIV_DEBUG + mutex->count_os_yield++; + #ifndef UNIV_HOTBACKUP diff -Nru mysql-5.5-5.5.35+dfsg/debian/patches/arch-specific/Bug-19048563-PERFORMANCE-REGRESSION-IN-UPDATE-OPS-CA.patch mysql-5.5-5.5.43/debian/patches/arch-specific/Bug-19048563-PERFORMANCE-REGRESSION-IN-UPDATE-OPS-CA.patch --- mysql-5.5-5.5.35+dfsg/debian/patches/arch-specific/Bug-19048563-PERFORMANCE-REGRESSION-IN-UPDATE-OPS-CA.patch 1970-01-01 00:00:00.000000000 +0000 +++ mysql-5.5-5.5.43/debian/patches/arch-specific/Bug-19048563-PERFORMANCE-REGRESSION-IN-UPDATE-OPS-CA.patch 2015-06-15 18:11:08.000000000 +0000 @@ -0,0 +1,87 @@ +From: Yasufumi Kinoshita +Subject: [PATCH] Bug #19048563 : PERFORMANCE REGRESSION IN UPDATE OPS CAUSED + BY TRUNK REVNO 8242 (BUG#11755438) + +Some of the added memory barrier (internal of spin loops of mutex/rw_lock) was too expensive. Removed. +This is partial reverting of the fix for Bug#11755438. + +------------------------------------------------------------ +revno: 6004 +committer: Yasufumi Kinoshita +branch nick: mysql-5.6 +timestamp: Thu 2014-06-19 07:33:57 +0200 +message: + Bug#11755438: Bug#47213: INNODB MUTEX/RW_LOCK SHOULD BE CONSCIOUS ABOUT MEMORY ORDERING OTHER THAN INTEL + + Because of difference about memory ordering, some critical flags of mutex/rw_lock might be missed to read on non-Intel CPUs. + Even for Intel-CPUs, the explicit memory barrier instruction might cause positive effects for performance. + + Approved by Kevin Lewis in rb#5561 +------------------------------------------------------------ +Bug-Ubuntu: https://bugs.launchpad.net/bugs/1427406 +Origin: https://github.com/mysql/mysql-server/commit/518f1d0cb7d369ada859af768acbfcdd4168cf3e +Last-Update: 2015-06-12 + +diff -urpN a/storage/innobase/include/os0sync.h b/storage/innobase/include/os0sync.h +--- a/storage/innobase/include/os0sync.h 2015-06-12 14:20:25.448406822 -0600 ++++ b/storage/innobase/include/os0sync.h 2015-06-12 14:57:07.784876623 -0600 +@@ -460,14 +460,6 @@ clobbered */ + "Memory barrier is not used" + #endif + +-/* internal counter for innodb_sync_spin_loops is adjusted +-because memory barrier is more expensive than an empty loop. */ +-#ifdef HAVE_MEMORY_BARRIER +-# define SPIN_WAIT_INCREMENT 2 +-#else +-# define SPIN_WAIT_INCREMENT 1 +-#endif /* HAVE_MEMORY_BARRIER */ +- + #ifndef UNIV_NONINL + #include "os0sync.ic" + #endif +diff -urpN a/storage/innobase/sync/sync0rw.c b/storage/innobase/sync/sync0rw.c +--- a/storage/innobase/sync/sync0rw.c 2015-06-12 14:45:26.785074328 -0600 ++++ b/storage/innobase/sync/sync0rw.c 2015-06-12 14:57:59.881017791 -0600 +@@ -396,8 +396,7 @@ lock_loop: + ut_delay(ut_rnd_interval(0, srv_spin_wait_delay)); + } + +- i += SPIN_WAIT_INCREMENT; +- os_rmb; ++ i++; + } + + if (i >= SYNC_SPIN_ROUNDS) { +@@ -508,7 +507,7 @@ rw_lock_x_lock_wait( + ut_delay(ut_rnd_interval(0, srv_spin_wait_delay)); + } + if(i < SYNC_SPIN_ROUNDS) { +- i += SPIN_WAIT_INCREMENT; ++ i++; + os_rmb; + continue; + } +@@ -663,8 +662,7 @@ lock_loop: + srv_spin_wait_delay)); + } + +- i += SPIN_WAIT_INCREMENT; +- os_rmb; ++ i++; + } + if (i >= SYNC_SPIN_ROUNDS) { + os_thread_yield(); +diff -urpN a/storage/innobase/sync/sync0sync.c b/storage/innobase/sync/sync0sync.c +--- a/storage/innobase/sync/sync0sync.c 2015-06-12 14:47:23.196895662 -0600 ++++ b/storage/innobase/sync/sync0sync.c 2015-06-12 14:58:18.989606255 -0600 +@@ -523,8 +523,7 @@ spin_loop: + ut_delay(ut_rnd_interval(0, srv_spin_wait_delay)); + } + +- i += SPIN_WAIT_INCREMENT; +- os_rmb; ++ i++; + } + + if (i >= SYNC_SPIN_ROUNDS) { diff -Nru mysql-5.5-5.5.35+dfsg/debian/patches/arch-specific/Disable-memory-barrier-only-for-Intel-CPU-because-pe.patch mysql-5.5-5.5.43/debian/patches/arch-specific/Disable-memory-barrier-only-for-Intel-CPU-because-pe.patch --- mysql-5.5-5.5.35+dfsg/debian/patches/arch-specific/Disable-memory-barrier-only-for-Intel-CPU-because-pe.patch 1970-01-01 00:00:00.000000000 +0000 +++ mysql-5.5-5.5.43/debian/patches/arch-specific/Disable-memory-barrier-only-for-Intel-CPU-because-pe.patch 2015-06-15 18:11:08.000000000 +0000 @@ -0,0 +1,41 @@ +From: Yasufumi Kinoshita +Subject: [PATCH] Disable memory barrier only for Intel CPU, because + performance regression was observed at some conditions for Intel CPU. follow + up for Bug#11755438: Bug#47213: INNODB MUTEX/RW_LOCK SHOULD BE CONSCIOUS + ABOUT MEMORY ORDERING OTHER THAN INTEL + +Bug-Ubuntu: https://bugs.launchpad.net/bugs/1427406 +Origin: https://github.com/mysql/mysql-server/commit/5f280dd21dd4b4ceefacf412932ac4b706c98bb5 +Last-Update: 2015-06-12 + +diff -urpN a/storage/innobase/include/os0sync.h b/storage/innobase/include/os0sync.h +--- a/storage/innobase/include/os0sync.h 2015-06-12 15:00:22.350537718 -0600 ++++ b/storage/innobase/include/os0sync.h 2015-06-12 15:02:19.981950485 -0600 +@@ -423,7 +423,14 @@ clobbered */ + #endif + + /** barrier definitions for memory ordering */ +-#ifdef HAVE_IB_GCC_ATOMIC_THREAD_FENCE ++#if defined __i386__ || defined __x86_64__ || defined _M_IX86 || defined _M_X64 || defined __WIN__ ++/* Performance regression was observed at some conditions for Intel ++architecture. Disable memory barrier for Intel architecture for now. */ ++# define os_rmb ++# define os_wmb ++# define IB_MEMORY_BARRIER_STARTUP_MSG \ ++ "Memory barrier is not used" ++#elif defined(HAVE_IB_GCC_ATOMIC_THREAD_FENCE) + # define HAVE_MEMORY_BARRIER + # define os_rmb __atomic_thread_fence(__ATOMIC_ACQUIRE) + # define os_wmb __atomic_thread_fence(__ATOMIC_RELEASE) +diff -urpN a/storage/innobase/srv/srv0start.c b/storage/innobase/srv/srv0start.c +--- a/storage/innobase/srv/srv0start.c 2015-06-12 15:00:59.117848000 -0600 ++++ b/storage/innobase/srv/srv0start.c 2015-06-12 15:02:46.949988712 -0600 +@@ -1156,7 +1156,7 @@ innobase_start_or_create_for_mysql(void) + fputs(" InnoDB: " IB_MEMORY_BARRIER_STARTUP_MSG "\n", stderr); + + #ifndef HAVE_MEMORY_BARRIER +-#if defined __i386__ || defined __x86_64__ || defined _M_IX86 || defined _M_X64 || defined _WIN32 ++#if defined __i386__ || defined __x86_64__ || defined _M_IX86 || defined _M_X64 || defined __WIN__ + #else + ib_logf(IB_LOG_LEVEL_WARN, + "MySQL was built without a memory barrier capability on this" diff -Nru mysql-5.5-5.5.35+dfsg/debian/patches/arch-specific/fix-build-fail-for-win32.patch mysql-5.5-5.5.43/debian/patches/arch-specific/fix-build-fail-for-win32.patch --- mysql-5.5-5.5.35+dfsg/debian/patches/arch-specific/fix-build-fail-for-win32.patch 1970-01-01 00:00:00.000000000 +0000 +++ mysql-5.5-5.5.43/debian/patches/arch-specific/fix-build-fail-for-win32.patch 2015-06-15 18:11:08.000000000 +0000 @@ -0,0 +1,33 @@ +From: Yasufumi Kinoshita +Subject: [PATCH] fix build fail for win32. follow up for Bug#11755438: + Bug#47213: INNODB MUTEX/RW_LOCK SHOULD BE CONSCIOUS ABOUT MEMORY ORDERING + OTHER THAN INTEL + +Bug-Ubuntu: https://bugs.launchpad.net/bugs/1427406 +Origin: https://github.com/mysql/mysql-server/commit/c3ef01981a645cf27b0a697e72bc606200fa58a8 +Last-Update: 2015-06-12 + +diff -urpN a/storage/innobase/include/os0sync.h b/storage/innobase/include/os0sync.h +--- a/storage/innobase/include/os0sync.h 2015-06-12 14:57:07.784876623 -0600 ++++ b/storage/innobase/include/os0sync.h 2015-06-12 15:00:22.350537718 -0600 +@@ -445,7 +445,7 @@ clobbered */ + # define IB_MEMORY_BARRIER_STARTUP_MSG \ + "Solaris memory ordering functions are used for memory barrier" + +-#elif defined(HAVE_WINDOWS_MM_FENCE) ++#elif defined(HAVE_WINDOWS_MM_FENCE) && defined(_WIN64) + # define HAVE_MEMORY_BARRIER + # include + # define os_rmb _mm_lfence() +diff -urpN a/storage/innobase/srv/srv0start.c b/storage/innobase/srv/srv0start.c +--- a/storage/innobase/srv/srv0start.c 2015-06-12 14:33:14.906224837 -0600 ++++ b/storage/innobase/srv/srv0start.c 2015-06-12 15:00:59.117848000 -0600 +@@ -1156,7 +1156,7 @@ innobase_start_or_create_for_mysql(void) + fputs(" InnoDB: " IB_MEMORY_BARRIER_STARTUP_MSG "\n", stderr); + + #ifndef HAVE_MEMORY_BARRIER +-#if defined __i386__ || defined __x86_64__ || defined _M_IX86 || defined _M_X64 ++#if defined __i386__ || defined __x86_64__ || defined _M_IX86 || defined _M_X64 || defined _WIN32 + #else + ib_logf(IB_LOG_LEVEL_WARN, + "MySQL was built without a memory barrier capability on this" diff -Nru mysql-5.5-5.5.35+dfsg/debian/patches/arch-specific/MDEV-6450-MariaDB-crash-on-Power8-when-built-with-advance-tool-chain.patch mysql-5.5-5.5.43/debian/patches/arch-specific/MDEV-6450-MariaDB-crash-on-Power8-when-built-with-advance-tool-chain.patch --- mysql-5.5-5.5.35+dfsg/debian/patches/arch-specific/MDEV-6450-MariaDB-crash-on-Power8-when-built-with-advance-tool-chain.patch 1970-01-01 00:00:00.000000000 +0000 +++ mysql-5.5-5.5.43/debian/patches/arch-specific/MDEV-6450-MariaDB-crash-on-Power8-when-built-with-advance-tool-chain.patch 2015-06-15 18:11:08.000000000 +0000 @@ -0,0 +1,58 @@ +Description: Fix crash on Power8 when built with advanced tool chain + This was later discovered to also fix a corruption issue on AArch64: + https://mariadb.atlassian.net/browse/MDEV-6615 +Origin: https://github.com/MariaDB/server/commit/40497577ffd9f85557b15e08ad913f627b2e9530 +Bug-Ubuntu: https://bugs.launchpad.net/bugs/1427406 +Forwarded: http://bugs.mysql.com/bug.php?id=76135; blocked by Oracle Contributor Agreement requirement +Author: Sergey Vojtovich +Last-Update: 2015-06-12 + +diff -urpN a/storage/innobase/include/os0sync.h b/storage/innobase/include/os0sync.h +--- a/storage/innobase/include/os0sync.h 2015-06-12 15:02:19.981950485 -0600 ++++ b/storage/innobase/include/os0sync.h 2015-06-12 15:05:45.087082920 -0600 +@@ -314,6 +314,9 @@ Returns the old value of *ptr, atomicall + # define os_atomic_test_and_set_byte(ptr, new_val) \ + __sync_lock_test_and_set(ptr, (byte) new_val) + ++# define os_atomic_lock_release_byte(ptr) \ ++ __sync_lock_release(ptr) ++ + #elif defined(HAVE_IB_SOLARIS_ATOMICS) + + #define HAVE_ATOMIC_BUILTINS +@@ -368,6 +371,9 @@ Returns the old value of *ptr, atomicall + # define os_atomic_test_and_set_byte(ptr, new_val) \ + atomic_swap_uchar(ptr, new_val) + ++# define os_atomic_lock_release_byte(ptr) \ ++ (void) atomic_swap_uchar(ptr, 0) ++ + #elif defined(HAVE_WINDOWS_ATOMICS) + + #define HAVE_ATOMIC_BUILTINS +@@ -460,6 +466,9 @@ architecture. Disable memory barrier for + # define IB_MEMORY_BARRIER_STARTUP_MSG \ + "_mm_lfence() and _mm_sfence() are used for memory barrier" + ++# define os_atomic_lock_release_byte(ptr) \ ++ (void) InterlockedExchange(ptr, 0) ++ + #else + # define os_rmb + # define os_wmb +diff -urpN a/storage/innobase/include/sync0sync.ic b/storage/innobase/include/sync0sync.ic +--- a/storage/innobase/include/sync0sync.ic 2015-06-12 14:29:58.239813599 -0600 ++++ b/storage/innobase/include/sync0sync.ic 2015-06-12 15:06:15.494887760 -0600 +@@ -113,11 +113,8 @@ mutex_reset_lock_word( + mutex_t* mutex) /*!< in: mutex */ + { + #if defined(HAVE_ATOMIC_BUILTINS) +- /* In theory __sync_lock_release should be used to release the lock. +- Unfortunately, it does not work properly alone. The workaround is +- that more conservative __sync_lock_test_and_set is used instead. */ + # if defined(HAVE_ATOMIC_BUILTINS_BYTE) +- os_atomic_test_and_set_byte(&mutex->lock_word, 0); ++ os_atomic_lock_release_byte(&mutex->lock_word); + # else + os_atomic_test_and_set_ulint(&mutex->lock_word, 0); + # endif diff -Nru mysql-5.5-5.5.35+dfsg/debian/patches/arch-specific/MDEV-6483-Deadlock_around_rw_lock_debug_mutex_on_PPC64.patch mysql-5.5-5.5.43/debian/patches/arch-specific/MDEV-6483-Deadlock_around_rw_lock_debug_mutex_on_PPC64.patch --- mysql-5.5-5.5.35+dfsg/debian/patches/arch-specific/MDEV-6483-Deadlock_around_rw_lock_debug_mutex_on_PPC64.patch 1970-01-01 00:00:00.000000000 +0000 +++ mysql-5.5-5.5.43/debian/patches/arch-specific/MDEV-6483-Deadlock_around_rw_lock_debug_mutex_on_PPC64.patch 2015-06-15 18:11:08.000000000 +0000 @@ -0,0 +1,113 @@ +Description: Deadlock around rw_lock_debug_mutex on PPC64 + This was later discovered to also fix a corruption issue on AArch64: + https://mariadb.atlassian.net/browse/MDEV-6615 +Origin: https://github.com/MariaDB/server/commit/c01c819209fdf09b4ba95f34d87d0617776f47cd +Bug-Ubuntu: https://bugs.launchpad.net/bugs/1427406 +Forwarded: http://bugs.mysql.com/bug.php?id=76135; blocked by Oracle Contributor Agreement requirement +Author: Sergey Vojtovich +Last-Update: 2015-06-12 + +diff -urpN a/storage/innobase/include/sync0rw.h b/storage/innobase/include/sync0rw.h +--- a/storage/innobase/include/sync0rw.h 2015-02-27 01:30:34.000000000 -0700 ++++ b/storage/innobase/include/sync0rw.h 2015-06-12 15:10:01.388634410 -0600 +@@ -70,14 +70,8 @@ extern mutex_t rw_lock_list_mutex; + #ifdef UNIV_SYNC_DEBUG + /* The global mutex which protects debug info lists of all rw-locks. + To modify the debug info list of an rw-lock, this mutex has to be +- + acquired in addition to the mutex protecting the lock. */ +-extern mutex_t rw_lock_debug_mutex; +-extern os_event_t rw_lock_debug_event; /*!< If deadlock detection does +- not get immediately the mutex it +- may wait for this event */ +-extern ibool rw_lock_debug_waiters; /*!< This is set to TRUE, if +- there may be waiters for the event */ ++extern os_fast_mutex_t rw_lock_debug_mutex; + #endif /* UNIV_SYNC_DEBUG */ + + /** number of spin waits on rw-latches, +diff -urpN a/storage/innobase/sync/sync0rw.c b/storage/innobase/sync/sync0rw.c +--- a/storage/innobase/sync/sync0rw.c 2015-06-12 14:57:59.881017791 -0600 ++++ b/storage/innobase/sync/sync0rw.c 2015-06-12 15:11:02.614242513 -0600 +@@ -179,18 +179,12 @@ UNIV_INTERN mysql_pfs_key_t rw_lock_mute + To modify the debug info list of an rw-lock, this mutex has to be + acquired in addition to the mutex protecting the lock. */ + +-UNIV_INTERN mutex_t rw_lock_debug_mutex; ++UNIV_INTERN os_fast_mutex_t rw_lock_debug_mutex; + + # ifdef UNIV_PFS_MUTEX + UNIV_INTERN mysql_pfs_key_t rw_lock_debug_mutex_key; + # endif + +-/* If deadlock detection does not get immediately the mutex, +-it may wait for this event */ +-UNIV_INTERN os_event_t rw_lock_debug_event; +-/* This is set to TRUE, if there may be waiters for the event */ +-UNIV_INTERN ibool rw_lock_debug_waiters; +- + /******************************************************************//** + Creates a debug info struct. */ + static +@@ -728,22 +722,7 @@ void + rw_lock_debug_mutex_enter(void) + /*===========================*/ + { +-loop: +- if (0 == mutex_enter_nowait(&rw_lock_debug_mutex)) { +- return; +- } +- +- os_event_reset(rw_lock_debug_event); +- +- rw_lock_debug_waiters = TRUE; +- +- if (0 == mutex_enter_nowait(&rw_lock_debug_mutex)) { +- return; +- } +- +- os_event_wait(rw_lock_debug_event); +- +- goto loop; ++ os_fast_mutex_lock(&rw_lock_debug_mutex); + } + + /******************************************************************//** +@@ -753,12 +732,7 @@ void + rw_lock_debug_mutex_exit(void) + /*==========================*/ + { +- mutex_exit(&rw_lock_debug_mutex); +- +- if (rw_lock_debug_waiters) { +- rw_lock_debug_waiters = FALSE; +- os_event_set(rw_lock_debug_event); +- } ++ os_fast_mutex_unlock(&rw_lock_debug_mutex); + } + + /******************************************************************//** +diff -urpN a/storage/innobase/sync/sync0sync.c b/storage/innobase/sync/sync0sync.c +--- a/storage/innobase/sync/sync0sync.c 2015-06-12 14:58:18.989606255 -0600 ++++ b/storage/innobase/sync/sync0sync.c 2015-06-12 15:11:53.410602187 -0600 +@@ -1528,11 +1528,7 @@ sync_init(void) + SYNC_NO_ORDER_CHECK); + + #ifdef UNIV_SYNC_DEBUG +- mutex_create(rw_lock_debug_mutex_key, &rw_lock_debug_mutex, +- SYNC_NO_ORDER_CHECK); +- +- rw_lock_debug_event = os_event_create(NULL); +- rw_lock_debug_waiters = FALSE; ++ os_fast_mutex_init(rw_lock_debug_mutex_key, &rw_lock_debug_mutex); + #endif /* UNIV_SYNC_DEBUG */ + } + +@@ -1600,6 +1596,7 @@ sync_close(void) + sync_order_checks_on = FALSE; + + sync_thread_level_arrays_free(); ++ os_fast_mutex_free(&rw_lock_debug_mutex); + #endif /* UNIV_SYNC_DEBUG */ + + sync_initialized = FALSE; diff -Nru mysql-5.5-5.5.35+dfsg/debian/patches/arch-specific/MDEV-7026-Race-in-InnoDB-XtraDB-mutex-implementation.patch mysql-5.5-5.5.43/debian/patches/arch-specific/MDEV-7026-Race-in-InnoDB-XtraDB-mutex-implementation.patch --- mysql-5.5-5.5.35+dfsg/debian/patches/arch-specific/MDEV-7026-Race-in-InnoDB-XtraDB-mutex-implementation.patch 1970-01-01 00:00:00.000000000 +0000 +++ mysql-5.5-5.5.43/debian/patches/arch-specific/MDEV-7026-Race-in-InnoDB-XtraDB-mutex-implementation.patch 2015-06-15 18:11:08.000000000 +0000 @@ -0,0 +1,265 @@ +Description: Add full memory barrier to ensure proper StoreLoad order on Power + The fixes for MDEV-6450 and MDEV-6483 introduced a regression on x86, so + the solution was reworked with full barrier support added for Power in + architectures specific ifdefs. This patch brought back a data corruption issue + on AArch64: + https://mariadb.atlassian.net/browse/MDEV-7658 + This is fixed up in a patch later in the series. +Origin: https://github.com/MariaDB/server/commit/6ea41f1e84eb6b864cac17ad0b862bde9820dc33 +Bug-Ubuntu: https://bugs.launchpad.net/bugs/1427406 +Forwarded: no; blocked by Oracle Contributor Agreement requirement +Author: Kristian Nielsen +Last-Update: 2015-06-12 + +Index: mysql-5.5-5.5.43/storage/innobase/include/os0sync.h +=================================================================== +--- mysql-5.5-5.5.43.orig/storage/innobase/include/os0sync.h ++++ mysql-5.5-5.5.43/storage/innobase/include/os0sync.h +@@ -232,12 +232,29 @@ os_fast_mutex_trylock( + /*==================*/ + os_fast_mutex_t* fast_mutex); /*!< in: mutex to acquire */ + /**********************************************************//** ++Acquires ownership of a fast mutex. Implies a full memory barrier even on ++platforms such as PowerPC where this is not normally required. ++@return 0 if success, != 0 if was reserved by another thread */ ++UNIV_INLINE ++ulint ++os_fast_mutex_trylock_full_barrier( ++/*==================*/ ++ os_fast_mutex_t* fast_mutex); /*!< in: mutex to acquire */ ++/**********************************************************//** + Releases ownership of a fast mutex. */ + UNIV_INTERN + void + os_fast_mutex_unlock( + /*=================*/ + os_fast_mutex_t* fast_mutex); /*!< in: mutex to release */ ++/**********************************************************//** ++Releases ownership of a fast mutex. Implies a full memory barrier even on ++platforms such as PowerPC where this is not normally required. */ ++UNIV_INTERN ++void ++os_fast_mutex_unlock_full_barrier( ++/*=================*/ ++ os_fast_mutex_t* fast_mutex); /*!< in: mutex to release */ + /*********************************************************//** + Initializes an operating system fast mutex semaphore. */ + UNIV_INTERN +@@ -311,11 +328,28 @@ amount of increment. */ + /**********************************************************//** + Returns the old value of *ptr, atomically sets *ptr to new_val */ + +-# define os_atomic_test_and_set_byte(ptr, new_val) \ ++#ifdef __powerpc__ ++/* ++ os_atomic_test_and_set_byte_release() should imply a release barrier before ++ setting, and a full barrier after. But __sync_lock_test_and_set() is only ++ documented as an aquire barrier. So on PowerPC we need to add the full ++ barrier explicitly. */ ++# define os_atomic_test_and_set_byte_release(ptr, new_val) \ ++ do { __sync_lock_release(ptr); \ ++ __sync_synchronize(); } while (0) ++#else ++/* ++ On x86, __sync_lock_test_and_set() happens to be full barrier, due to ++ LOCK prefix. ++*/ ++# define os_atomic_test_and_set_byte_release(ptr, new_val) \ ++ __sync_lock_test_and_set(ptr, (byte) new_val) ++#endif ++/* ++ os_atomic_test_and_set_byte_acquire() is a full memory barrier on x86. But ++ in general, just an aquire barrier should be sufficient. */ ++# define os_atomic_test_and_set_byte_acquire(ptr, new_val) \ + __sync_lock_test_and_set(ptr, (byte) new_val) +- +-# define os_atomic_lock_release_byte(ptr) \ +- __sync_lock_release(ptr) + + #elif defined(HAVE_IB_SOLARIS_ATOMICS) + +@@ -368,11 +402,10 @@ amount of increment. */ + /**********************************************************//** + Returns the old value of *ptr, atomically sets *ptr to new_val */ + +-# define os_atomic_test_and_set_byte(ptr, new_val) \ ++# define os_atomic_test_and_set_byte_acquire(ptr, new_val) \ ++ atomic_swap_uchar(ptr, new_val) ++# define os_atomic_test_and_set_byte_release(ptr, new_val) \ + atomic_swap_uchar(ptr, new_val) +- +-# define os_atomic_lock_release_byte(ptr) \ +- (void) atomic_swap_uchar(ptr, 0) + + #elif defined(HAVE_WINDOWS_ATOMICS) + +@@ -420,7 +453,9 @@ Returns the old value of *ptr, atomicall + InterlockedExchange() operates on LONG, and the LONG will be + clobbered */ + +-# define os_atomic_test_and_set_byte(ptr, new_val) \ ++# define os_atomic_test_and_set_byte_acquire(ptr, new_val) \ ++ ((byte) InterlockedExchange(ptr, new_val)) ++# define os_atomic_test_and_set_byte_release(ptr, new_val) \ + ((byte) InterlockedExchange(ptr, new_val)) + + #else +@@ -440,6 +475,7 @@ architecture. Disable memory barrier for + # define HAVE_MEMORY_BARRIER + # define os_rmb __atomic_thread_fence(__ATOMIC_ACQUIRE) + # define os_wmb __atomic_thread_fence(__ATOMIC_RELEASE) ++# define os_mb __atomic_thread_fence(__ATOMIC_SEQ_CST) + # define IB_MEMORY_BARRIER_STARTUP_MSG \ + "GCC builtin __atomic_thread_fence() is used for memory barrier" + +@@ -455,6 +491,7 @@ architecture. Disable memory barrier for + # include + # define os_rmb __machine_r_barrier() + # define os_wmb __machine_w_barrier() ++# define os_mb __machine_rw_barrier() + # define IB_MEMORY_BARRIER_STARTUP_MSG \ + "Solaris memory ordering functions are used for memory barrier" + +@@ -463,15 +500,14 @@ architecture. Disable memory barrier for + # include + # define os_rmb _mm_lfence() + # define os_wmb _mm_sfence() ++# define os_mb _mm_mfence() + # define IB_MEMORY_BARRIER_STARTUP_MSG \ + "_mm_lfence() and _mm_sfence() are used for memory barrier" + +-# define os_atomic_lock_release_byte(ptr) \ +- (void) InterlockedExchange(ptr, 0) +- + #else + # define os_rmb + # define os_wmb ++# define os_mb + # define IB_MEMORY_BARRIER_STARTUP_MSG \ + "Memory barrier is not used" + #endif +Index: mysql-5.5-5.5.43/storage/innobase/include/os0sync.ic +=================================================================== +--- mysql-5.5-5.5.43.orig/storage/innobase/include/os0sync.ic ++++ mysql-5.5-5.5.43/storage/innobase/include/os0sync.ic +@@ -54,3 +54,29 @@ os_fast_mutex_trylock( + return((ulint) pthread_mutex_trylock(fast_mutex)); + #endif + } ++ ++/**********************************************************//** ++Acquires ownership of a fast mutex. Implies a full memory barrier even on ++platforms such as PowerPC where this is not normally required. ++@return 0 if success, != 0 if was reserved by another thread */ ++UNIV_INLINE ++ulint ++os_fast_mutex_trylock_full_barrier( ++/*==================*/ ++ os_fast_mutex_t* fast_mutex) /*!< in: mutex to acquire */ ++{ ++#ifdef __WIN__ ++ return(!TryEnterCriticalSection(fast_mutex)); ++#else ++ /* NOTE that the MySQL my_pthread.h redefines pthread_mutex_trylock ++ so that it returns 0 on success. In the operating system ++ libraries, HP-UX-10.20 follows the old Posix 1003.4a Draft 4 and ++ returns 1 on success (but MySQL remaps that to 0), while Linux, ++ FreeBSD, Solaris, AIX, Tru64 Unix, HP-UX-11.0 return 0 on success. */ ++ ++#ifdef __powerpc__ ++ os_mb; ++#endif ++ return((ulint) pthread_mutex_trylock(fast_mutex)); ++#endif ++} +Index: mysql-5.5-5.5.43/storage/innobase/include/sync0sync.ic +=================================================================== +--- mysql-5.5-5.5.43.orig/storage/innobase/include/sync0sync.ic ++++ mysql-5.5-5.5.43/storage/innobase/include/sync0sync.ic +@@ -81,14 +81,14 @@ mutex_test_and_set( + { + #if defined(HAVE_ATOMIC_BUILTINS) + # if defined(HAVE_ATOMIC_BUILTINS_BYTE) +- return(os_atomic_test_and_set_byte(&mutex->lock_word, 1)); ++ return(os_atomic_test_and_set_byte_acquire(&mutex->lock_word, 1)); + # else + return(os_atomic_test_and_set_ulint(&mutex->lock_word, 1)); + # endif + #else + ibool ret; + +- ret = os_fast_mutex_trylock(&(mutex->os_fast_mutex)); ++ ret = os_fast_mutex_trylock_full_barrier(&(mutex->os_fast_mutex)); + + if (ret == 0) { + /* We check that os_fast_mutex_trylock does not leak +@@ -96,7 +96,6 @@ mutex_test_and_set( + ut_a(mutex->lock_word == 0); + + mutex->lock_word = 1; +- os_wmb; + } + + return((byte)ret); +@@ -114,14 +113,17 @@ mutex_reset_lock_word( + { + #if defined(HAVE_ATOMIC_BUILTINS) + # if defined(HAVE_ATOMIC_BUILTINS_BYTE) +- os_atomic_lock_release_byte(&mutex->lock_word); ++ /* In theory __sync_lock_release should be used to release the lock. ++ Unfortunately, it does not work properly alone. The workaround is ++ that more conservative __sync_lock_test_and_set is used instead. */ ++ os_atomic_test_and_set_byte_release(&mutex->lock_word, 0); + # else + os_atomic_test_and_set_ulint(&mutex->lock_word, 0); + # endif + #else + mutex->lock_word = 0; + +- os_fast_mutex_unlock(&(mutex->os_fast_mutex)); ++ os_fast_mutex_unlock_full_barrier(&(mutex->os_fast_mutex)); + #endif + } + +Index: mysql-5.5-5.5.43/storage/innobase/os/os0sync.c +=================================================================== +--- mysql-5.5-5.5.43.orig/storage/innobase/os/os0sync.c ++++ mysql-5.5-5.5.43/storage/innobase/os/os0sync.c +@@ -798,6 +798,25 @@ os_mutex_exit( + } + + /**********************************************************//** ++Releases ownership of a fast mutex. Implies a full memory barrier even on ++platforms such as PowerPC where this is not normally required. */ ++UNIV_INTERN ++void ++os_fast_mutex_unlock_full_barrier( ++/*=================*/ ++ os_fast_mutex_t* fast_mutex) /*!< in: mutex to release */ ++{ ++#ifdef __WIN__ ++ LeaveCriticalSection(fast_mutex); ++#else ++ pthread_mutex_unlock(fast_mutex); ++#ifdef __powerpc__ ++ os_mb; ++#endif ++#endif ++} ++ ++/**********************************************************//** + Frees a mutex object. */ + UNIV_INTERN + void +Index: mysql-5.5-5.5.43/storage/innobase/sync/sync0sync.c +=================================================================== +--- mysql-5.5-5.5.43.orig/storage/innobase/sync/sync0sync.c ++++ mysql-5.5-5.5.43/storage/innobase/sync/sync0sync.c +@@ -472,7 +472,6 @@ mutex_set_waiters( + + *ptr = n; /* Here we assume that the write of a single + word in memory is atomic */ +- os_wmb; + } + + /******************************************************************//** diff -Nru mysql-5.5-5.5.35+dfsg/debian/patches/arch-specific/MDEV-7658-fix-AArch64-MDEV-6615-regression.patch mysql-5.5-5.5.43/debian/patches/arch-specific/MDEV-7658-fix-AArch64-MDEV-6615-regression.patch --- mysql-5.5-5.5.35+dfsg/debian/patches/arch-specific/MDEV-7658-fix-AArch64-MDEV-6615-regression.patch 1970-01-01 00:00:00.000000000 +0000 +++ mysql-5.5-5.5.43/debian/patches/arch-specific/MDEV-7658-fix-AArch64-MDEV-6615-regression.patch 2015-06-15 18:11:08.000000000 +0000 @@ -0,0 +1,47 @@ +Description: Enable full memory barrier usage on AArch64 + The fix for MDEV-7026 reworked a corruption fix for PowerPC using + #ifdef __powerpc__ guards. AArch64 is also impacted by that corruption + issue, so this introduced a regression. Follow suit by placing __aarch64__ + in the guard as well. The author isn't a fan of using arch #ifdefs in this + way, but he also isn't familiar enough with the code to rearchitect it. +Author: dann frazier +Bug-Ubuntu: https://bugs.launchpad.net/bugs/1427406 +Forwarded: no; dependent on earlier patches which are blocked by the Oracle Contributor Agreement requirement +Last-Update: 2015-06-12 + +diff -urpN a/storage/innobase/include/os0sync.h b/storage/innobase/include/os0sync.h +--- a/storage/innobase/include/os0sync.h 2015-06-12 15:31:39.786245779 -0600 ++++ b/storage/innobase/include/os0sync.h 2015-06-12 15:31:09.318386449 -0600 +@@ -328,7 +328,7 @@ amount of increment. */ + /**********************************************************//** + Returns the old value of *ptr, atomically sets *ptr to new_val */ + +-#ifdef __powerpc__ ++#if defined(__aarch64__) || defined(__powerpc__) + /* + os_atomic_test_and_set_byte_release() should imply a release barrier before + setting, and a full barrier after. But __sync_lock_test_and_set() is only +diff -urpN a/storage/innobase/include/os0sync.ic b/storage/innobase/include/os0sync.ic +--- a/storage/innobase/include/os0sync.ic 2015-06-12 15:31:39.786245779 -0600 ++++ b/storage/innobase/include/os0sync.ic 2015-06-12 15:31:09.318386449 -0600 +@@ -76,7 +76,7 @@ os_fast_mutex_trylock_full_barrier( + returns 1 on success (but MySQL remaps that to 0), while Linux, + FreeBSD, Solaris, AIX, Tru64 Unix, HP-UX-11.0 return 0 on success. */ + +-#ifdef __powerpc__ ++#if defined( __aarch64__) || defined(__powerpc__) + os_mb; + #endif + return((ulint) pthread_mutex_trylock(mutex)); +diff -urpN a/storage/innobase/os/os0sync.c b/storage/innobase/os/os0sync.c +--- a/storage/innobase/os/os0sync.c 2015-06-12 15:31:39.786245779 -0600 ++++ b/storage/innobase/os/os0sync.c 2015-06-12 15:31:15.637942541 -0600 +@@ -810,7 +810,7 @@ os_fast_mutex_unlock_full_barrier_func( + LeaveCriticalSection(fast_mutex); + #else + pthread_mutex_unlock(fast_mutex); +-#ifdef __powerpc__ ++#if defined(__aarch64__) || defined(__powerpc__) + os_mb; + #endif + #endif diff -Nru mysql-5.5-5.5.35+dfsg/debian/patches/arch-specific/series-arm64 mysql-5.5-5.5.43/debian/patches/arch-specific/series-arm64 --- mysql-5.5-5.5.35+dfsg/debian/patches/arch-specific/series-arm64 1970-01-01 00:00:00.000000000 +0000 +++ mysql-5.5-5.5.43/debian/patches/arch-specific/series-arm64 2015-06-15 18:11:08.000000000 +0000 @@ -0,0 +1,8 @@ +Bug-11755438-Bug-47213-INNODB-MUTEX-RW_LOCK-SHOULD-B.patch +Bug-19048563-PERFORMANCE-REGRESSION-IN-UPDATE-OPS-CA.patch +fix-build-fail-for-win32.patch +Disable-memory-barrier-only-for-Intel-CPU-because-pe.patch +MDEV-6450-MariaDB-crash-on-Power8-when-built-with-advance-tool-chain.patch +MDEV-6483-Deadlock_around_rw_lock_debug_mutex_on_PPC64.patch +MDEV-7026-Race-in-InnoDB-XtraDB-mutex-implementation.patch +MDEV-7658-fix-AArch64-MDEV-6615-regression.patch diff -Nru mysql-5.5-5.5.35+dfsg/debian/patches/arch-specific/series-ppc64el mysql-5.5-5.5.43/debian/patches/arch-specific/series-ppc64el --- mysql-5.5-5.5.35+dfsg/debian/patches/arch-specific/series-ppc64el 1970-01-01 00:00:00.000000000 +0000 +++ mysql-5.5-5.5.43/debian/patches/arch-specific/series-ppc64el 2015-06-15 18:11:08.000000000 +0000 @@ -0,0 +1,8 @@ +Bug-11755438-Bug-47213-INNODB-MUTEX-RW_LOCK-SHOULD-B.patch +Bug-19048563-PERFORMANCE-REGRESSION-IN-UPDATE-OPS-CA.patch +fix-build-fail-for-win32.patch +Disable-memory-barrier-only-for-Intel-CPU-because-pe.patch +MDEV-6450-MariaDB-crash-on-Power8-when-built-with-advance-tool-chain.patch +MDEV-6483-Deadlock_around_rw_lock_debug_mutex_on_PPC64.patch +MDEV-7026-Race-in-InnoDB-XtraDB-mutex-implementation.patch +MDEV-7658-fix-AArch64-MDEV-6615-regression.patch diff -Nru mysql-5.5-5.5.35+dfsg/debian/rules mysql-5.5-5.5.43/debian/rules --- mysql-5.5-5.5.35+dfsg/debian/rules 2014-02-19 21:19:52.000000000 +0000 +++ mysql-5.5-5.5.43/debian/rules 2015-06-15 18:11:08.000000000 +0000 @@ -76,6 +76,10 @@ rm -rf $(BUILDDIR) $(BUILDDIR_PIC) debconf-updatepo rm -f $(EXPORTED_SOURCE_TARBALL) + QUILT_PC=.pc-arch-specific \ + QUILT_PATCHES=debian/patches/arch-specific \ + QUILT_SERIES=series-$(ARCH) quilt pop -a || [ $$? = 2 ] + rm -rf .pc-arch-specific arch-patch-stamp override_dh_prep: @@ -84,7 +88,19 @@ configure-pic-stamp: FORCE_FPIC_CFLAGS=-fPIC configure-pic-stamp: FORCE_FPIC=-DWITH_PIC=On -configure-stamp configure-pic-stamp: +# arch-specific patches are used here to deal with a data corruption +# issue that impacts Power and ARM64: +# http://bugs.launchpad.net/bugs/1427406 +# Though we didn't observe any regressions when testing these patches on x86, +# we decided to minimize the regression risk by only applying these patches +# on affected architectures until we can replace it with an upstream fix. +arch-patch-stamp: + QUILT_PC=.pc-arch-specific \ + QUILT_PATCHES=debian/patches/arch-specific \ + QUILT_SERIES=series-$(ARCH) quilt push -a || [ $$? = 2 ] + touch $@ + +configure-stamp configure-pic-stamp: arch-patch-stamp @echo "RULES.$@" dh_testdir ( test -d $(builddir) || mkdir $(builddir) ) && cd $(builddir) && \ diff -Nru mysql-5.5-5.5.35+dfsg/Docs/ChangeLog mysql-5.5-5.5.43/Docs/ChangeLog --- mysql-5.5-5.5.35+dfsg/Docs/ChangeLog 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/Docs/ChangeLog 2015-02-27 08:30:42.000000000 +0000 @@ -1,993 +1 @@ ------------------------------------------------------------- -revno: 4535 -committer: Balasubramanian Kandasamy -branch nick: mysql-5.5.35-release -timestamp: Tue 2013-11-05 08:03:43 +0100 -message: - Removed non gpl file mysql.info from uln community package ------------------------------------------------------------- -revno: 4534 [merge] -tags: clone-5.5.35-build -committer: Tor Didriksen -branch nick: 5.5-merge -timestamp: Fri 2013-11-01 16:52:21 +0100 -message: - merge 5.1 => 5.5 - ------------------------------------------------------------ - revno: 2661.844.85 - tags: clone-5.1.73-build - committer: Tor Didriksen - branch nick: 5.1 - timestamp: Fri 2013-11-01 16:39:19 +0100 - message: - Bug#17617945 BUFFER OVERFLOW IN GET_MERGE_MANY_BUFFS_COST WITH SMALL SORT_BUFFER_SIZE - - get_cost_calc_buff_size() could return wrong value for the size of imerge_cost_buff. ------------------------------------------------------------- -revno: 4533 -committer: Venkata Sidagam -branch nick: 5.5 -timestamp: Fri 2013-11-01 13:48:24 +0530 -message: - Bug #12917164 DROP USER CAN'T DROP USERS WITH LEGACY - UPPER CASE HOST NAME ANYMORE - Fixing the testcase failure ------------------------------------------------------------- -revno: 4532 [merge] -committer: Nuno Carvalho -branch nick: mysql-5.5 -timestamp: Thu 2013-10-31 22:58:07 +0000 -message: - BUG#17662398: REMOVE DUPLICATE TEST CASES - - Merge from mysql-5.1 into mysql-5.5. - ------------------------------------------------------------ - revno: 2661.844.84 - committer: Nuno Carvalho - branch nick: mysql-5.1 - timestamp: Thu 2013-10-31 22:53:56 +0000 - message: - BUG#17662398: REMOVE DUPLICATE TEST CASES - - Remove duplicate test cases. ------------------------------------------------------------- -revno: 4531 [merge] -committer: Venkata Sidagam -branch nick: 5.5 -timestamp: Thu 2013-10-31 23:14:33 +0530 -message: - Bug #12917164 DROP USER CAN'T DROP USERS WITH LEGACY - UPPER CASE HOST NAME ANYMORE - Merging from mysql-5.1 to mysql-5.5 - ------------------------------------------------------------ - revno: 2661.844.83 - committer: Venkata Sidagam - branch nick: 5.1 - timestamp: Thu 2013-10-31 23:02:44 +0530 - message: - Bug #12917164 DROP USER CAN'T DROP USERS WITH LEGACY - UPPER CASE HOST NAME ANYMORE - - Description: - It is not possible to drop users with host names with upper case - letters in them. i.e DROP USER 'root'@'Tmp_Host_Name'; is failing - with error. - - Analysis: Since the fix 11748570 we came up with lower case hostnames - as standard. But in the current bug the hostname is created by - mysql_install_db script is still having upper case hostnames. - So, if we have the hostname with upper case letters like(Tmp_Host_Name) - then we will have as it is stored in the mysql.user table. - In this case if use "'DROP USER 'root'@'Tmp_Host_Name';" it gives - error because we do compare with the lower case of hostname since the - 11748570 fix. - - Fix: We need to convert the hostname to lower case before storing into - the mysql.user table when we run the mysql_install_db script. ------------------------------------------------------------- -revno: 4530 -committer: Saikumar V -branch nick: mysql-5.5 -timestamp: Thu 2013-10-31 09:01:09 +0530 -message: - Synching rqg grammars/redefines to mysql-repos internal. ------------------------------------------------------------- -revno: 4529 [merge] -committer: Balasubramanian Kandasamy -branch nick: mysql-5.5 -timestamp: Wed 2013-10-30 04:12:24 +0100 -message: - Merge 5.1 => 5.5 - ------------------------------------------------------------ - revno: 2661.844.82 - committer: Balasubramanian Kandasamy - branch nick: mysql-5.1 - timestamp: Wed 2013-10-30 04:07:07 +0100 - message: - Removed non gpl file docs/mysql.info from community packages ------------------------------------------------------------- -revno: 4528 [merge] -committer: Tor Didriksen -branch nick: 5.5-merge -timestamp: Tue 2013-10-29 19:55:38 +0100 -message: - remerge 5.1 => 5.5 - ------------------------------------------------------------ - revno: 2661.844.81 - committer: Tor Didriksen - branch nick: 5.1 - timestamp: Tue 2013-10-29 17:26:20 +0100 - message: - Bug#17326567 MYSQL SERVER FILESORT IMPLEMENTATION HAS A VERY SERIOUS BUG - - The filesort implementation needs space for at least 15 records - (plus some internal overhead) in its main sort buffer. ------------------------------------------------------------- -revno: 4527 -committer: kevin.lewis@oracle.com -branch nick: mysql-5.5 -timestamp: Tue 2013-10-29 11:39:04 -0500 -message: - Testcase i_innodb.innodb-alter-restart.test fails on some Windows platforms - possibly since it was introduced in the patch for Bug#16720368 around - 2013-04-30. This fix is simply to adjust the mtr.add_suppression() lines - in the testcase and to add a missing "\n" in the error message. - - Approved by Marko in RB 3746 ------------------------------------------------------------- -revno: 4526 -committer: Mattias Jonsson -branch nick: test-5.5 -timestamp: Mon 2013-10-28 17:08:31 +0100 -message: - post-push fix for bug#17565888/bug#14621190 ------------------------------------------------------------- -revno: 4525 -committer: Luis Soares -branch nick: mysql-5.5 -timestamp: Fri 2013-10-25 09:42:59 +0100 -message: - BUG#17460821: ASSERTION ERROR WHEN STOPPING SLAVE AFTER SEMI-SYNC ON MASTER IS DISABLED - - In the test case, make sure that the IO thread is not stopped - during the binlog dump request. ------------------------------------------------------------- -revno: 4524 -committer: sayantan dutta -branch nick: mysql-5.5 -timestamp: Fri 2013-10-25 11:38:34 +0530 -message: - Bug #17654275 - MTR EXTRACT_WARNING_LINES IS NOT REMOVING TIMESTAMP IN UTC FORMAT WITH TIMEZONES ------------------------------------------------------------- -revno: 4523 -committer: Jon Olav Hauglid -branch nick: mysql-5.5-bug17632386 -timestamp: Mon 2013-10-21 13:14:46 +0200 -message: - Bug#17632386: WITH_ASAN CONFLICTS WITH -WL,--NO-UNDEFINED - - -Wl,--no-undefined (=-z defs) gives linking errors when used with WITH_ASAN. - According to the documentation: - "When linking shared libraries, the AddressSanitizer run-time is not linked, - so -Wl,-z,defs may cause link errors (don?t use it with AddressSanitizer)." - - This patch turns off -Wl,--no-undefined if WITH_ASAN is used. ------------------------------------------------------------- -revno: 4522 -committer: Aditya A -branch nick: mysql-5.5 -timestamp: Mon 2013-10-21 12:07:02 +0530 -message: - Bug #16051817 GOT ERROR 124 FROM STORAGE ENGINE - ON DELETE FROM A PARTITIONED TABLE - - PROBLEM - ------- - - The user first disables all the non unique indexes - in the table and then rebuilds one partition. - During rebuild the indexes on that particular - partition are enabled. Now when we give a query - the optimizer is unaware that on one partition - indexes are enabled and if the optimizer selects - that index,myisam thinks that the index is not - active and gives an error. - - FIX - --- - - Before rebuilding a partition check whether non - unique indexes are disabled on the partitons. - If they are disabled then after rebuild disable - the index on the partition. - - [Approved by Mattiasj #rb3469] ------------------------------------------------------------- -revno: 4521 -committer: Mattias Jonsson -branch nick: test-5.5 -timestamp: Sat 2013-10-19 15:29:51 +0200 -message: - post-push fix for bug17565888. ------------------------------------------------------------- -revno: 4520 -committer: Mattias Jonsson -branch nick: test-5.5 -timestamp: Fri 2013-10-18 23:49:35 +0200 -message: - post-push fix for bug17565888. - - Too restrictive assertion, failing during purge ------------------------------------------------------------- -revno: 4519 -committer: Mattias Jonsson -branch nick: test-5.5 -timestamp: Fri 2013-10-18 23:39:15 +0200 -message: - post-push fix for bug17565888. - - Too restrictive assertion, can fail during purge ------------------------------------------------------------- -revno: 4518 -committer: Mattias Jonsson -branch nick: test-5.5 -timestamp: Fri 2013-10-18 19:25:59 +0200 -message: - Bug#17565888: UP TO 75% INCREASE IN DBT3 QUERY (Q7) EXECUTION TIME - - Regression from bug#14621190 due to disabled optimistic restoration - of cursor, which required full key lookup instead of verifying - if previously positioned btree cursor could be reused. - - Fixed by enable optimistic restore and adjust cursor afterward. - - rb#3324 approved by Marko. ------------------------------------------------------------- -revno: 4517 -committer: Anirudh Mangipudi -branch nick: 5.5 -timestamp: Fri 2013-10-18 17:14:39 +0530 -message: - Bug #17357535 BACKPORT BUG#16241992 TO 5.5 - Problem: - COM_CHANGE_USER allows brute-force attempts to crack a password at a very high - rate as it does not cause any significant delay after a login attempt has - failed. This issue was reproduced using John-The-Ripper password - cracking tool through which about 5000 passwords per second could be attempted. - - Solution: - The non-GA version's solution was to disconnect the connection when a login - attempt failed. Now since our aim to to reduce the rate at which passwords - are tested, we introduced a sleep(1) after every login attempt failed. This - significantly increased the delay with which the password was cracked. ------------------------------------------------------------- -revno: 4516 [merge] -committer: Luis Soares -branch nick: mysql-5.5 -timestamp: Fri 2013-10-18 10:50:49 +0100 -message: - BUG#17460821 - - Automerged from mysql-5.5 bug branch into latest mysql-5.5. - ------------------------------------------------------------ - revno: 4512.1.1 - committer: Luis Soares - branch nick: mysql-5.5 - timestamp: Thu 2013-10-17 17:48:26 +0100 - message: - BUG#17460821: ASSERTION ERROR WHEN STOPPING SLAVE AFTER SEMI-SYNC ON MASTER IS DISABLED - - The assertion happens when: (i) the master and slave are configured to - use the semisync plugin; (ii) the DBA disables semisync on the master; - (iii) and he also unsets the option to wait for slaves ACK even if the - semisync slave count reaches 0 during the waiting period. This - combination of factors makes the server run into an assertion as soon - as the last semisync slave disconnects and its dump thread exits. - - The root of the problem is the fact that when the dump thread - disconnects and calls the observer hook transmit_stop, which ends up - calling ReplSemiSyncMaster::remove_slave, there is no check whether - the master has already disabled semisync or not. If it has, the then a - second call to the switch_off member function must be avoided. - - The quick fix is to avoid calling switch_off if the DBA has disabled - the semisync plugin interactively on the master. Also, the switch_off - member function should only be called if the plugin has not been - switched off already. This is basically the pattern throughout the - rest of the semisync plugin and no other calls seem vulnerable to - similar crashes/assertions. - - (This a backport of the patch to 5.5, which is also vulnerable.) ------------------------------------------------------------- -revno: 4515 [merge] -committer: Aditya A -branch nick: mysql-5.5 -timestamp: Fri 2013-10-18 13:49:03 +0530 -message: - Bug#17559867 AFTER REBUILDING , A MYISAM PARTITION ENDS UP - AS A INNODB PARTITTION. - [Merged from 5.1] - ------------------------------------------------------------ - revno: 2661.844.80 - committer: Aditya A - branch nick: mysql-5.1 - timestamp: Fri 2013-10-18 12:26:28 +0530 - message: - Bug#17559867 AFTER REBUILDING,A MYISAM PARTITION ENDS UP - AS A INNODB PARTITTION. - - PROBLEM - ------- - The correct engine_type was not being set during - rebuild of the partition due to which the handler - was always created with the default engine, - which is innodb for 5.5+ ,therefore even if the - table was myisam, after rebuilding the partitions - ended up as innodb partitions. - - FIX - --- - Set the correct engine type during rebuild. - - [Approved by mattiasj #rb3599] ------------------------------------------------------------- -revno: 4514 -committer: Anil Toshniwal -branch nick: mysql-5.5 -timestamp: Thu 2013-10-17 18:09:04 +0530 -message: - Bug#17513737 INTRODUCE CHECK TABLE...QUICK - - --Implemented CHECK TABLE...QUICK. - Introduce CHECK TABLE...QUICK that would skip the btr_validate_index() - and btr_search_validate() call, and count the no. of records in each index. - - Approved by Marko and Kevin. (rb#3567). ------------------------------------------------------------- -revno: 4513 -committer: Praveenkumar Hulakund -branch nick: mysql-5.5 -timestamp: Thu 2013-10-17 17:59:45 +0530 -message: - Bug#17474166 - EXECUTING STATEMENT LIKE 'SHOW ENGINE INNODB' - AND 'KILL SESSION' LEAD TO CRASH - - Fixing pb2 failure on embedded version. ------------------------------------------------------------- -revno: 4512 [merge] -committer: Luis Soares -branch nick: mysql-5.5 -timestamp: Thu 2013-10-17 12:27:45 +0100 -message: - BUG#17508351 - - Merging mysql-5.5 bug branch into latest mysql-5.5. - ------------------------------------------------------------ - revno: 4488.1.1 - committer: Luis Soares - branch nick: mysql-5.5 - timestamp: Tue 2013-10-08 18:37:43 +0100 - message: - BUG#17508351: REDUNDANT CODE IN REPLSEMISYNCMASTER::UPDATESYNCHEADER - - ReplSemiSyncMaster::updateSyncHeader contains redundant assignments - to the local variable sync. - - This patch removes them. ------------------------------------------------------------- -revno: 4511 [merge] -committer: Venkatesh Duggirala -branch nick: mysql-5.5 -timestamp: Wed 2013-10-16 22:15:59 +0530 -message: - Bug#17234370 LAST_INSERT_ID IS REPLICATED INCORRECTLY IF - REPLICATION FILTERS ARE USED. - Merging fix from mysql-5.1 - ------------------------------------------------------------ - revno: 2661.844.79 - committer: Venkatesh Duggirala - branch nick: mysql-5.1 - timestamp: Wed 2013-10-16 22:12:23 +0530 - message: - Bug#17234370 LAST_INSERT_ID IS REPLICATED INCORRECTLY IF - REPLICATION FILTERS ARE USED. - - Problem: - When Filtered-slave applies Int_var_log_event and when it - tries to write the event to its own binlog, LAST_INSERT_ID - value is written wrongly. - - Analysis: - THD::stmt_depends_on_first_successful_insert_id_in_prev_stmt - is a variable which is set when LAST_INSERT_ID() is used by - a statement. If it is set, first_successful_insert_id_in_ - prev_stmt_for_binlog will be stored in the statement-based - binlog. This variable is CUMULATIVE along the execution of - a stored function or trigger: if one substatement sets it - to 1 it will stay 1 until the function/trigger ends, - thus making sure that first_successful_insert_id_in_ - prev_stmt_for_binlog does not change anymore and is - propagated to the caller for binlogging. This is achieved - using the following code - if(!stmt_depends_on_first_successful_insert_id_in_prev_stmt) - { - /* It's the first time we read it */ - first_successful_insert_id_in_prev_stmt_for_binlog= - first_successful_insert_id_in_prev_stmt; - stmt_depends_on_first_successful_insert_id_in_prev_stmt= 1; - } - - Slave server, after receiving Int_var_log_event event from - master, it is setting - stmt_depends_on_first_successful_insert_id_in_prev_stmt - to true(*which is wrong*) and not setting - first_successful_insert_id_in_prev_stmt_for_binlog. Because - of this problem, when the actual DML statement with - LAST_INSERT_ID() is parsed by slave SQL thread, - first_successful_insert_id_in_prev_stmt_for_binlog is not - set. Hence the value zero (default value) is written to - slave's binlog. - - Why only *Filtered slave* is effected when the code is - in common place: - ------------------------------------------------------- - In Query_log_event::do_apply_event, - THD::stmt_depends_on_first_successful_insert_id_in_prev_stmt - is reset to zero at the end of the function. In case of - normal slave (No Filters), this variable will be reset. - In Filtered slave, Slave SQL thread defers all IRU events's - execution until IRU's Query_log event is received. Once it - receives Query_log_event it executes all pending IRU events - and then it executes Query_log_event. Hence the variable is - not getting reset to 0, causing this bug. - - Fix: As described above, the root cause was setting - THD::stmt_depends_on_first_successful_insert_id_in_prev_stmt - when Int_var_log_event was executed by a SQL thread. Hence - removing the problematic line from the code. ------------------------------------------------------------- -revno: 4510 [merge] -committer: Venkata Sidagam -branch nick: 5.5 -timestamp: Wed 2013-10-16 14:16:32 +0530 -message: - Bug#16900358 FIX FOR CVE-2012-5611 IS INCOMPLETE - - Merging from mysql-5.1 to mysql-5.5 - ------------------------------------------------------------ - revno: 2661.844.78 - committer: Venkata Sidagam - branch nick: 5.1 - timestamp: Wed 2013-10-16 14:14:44 +0530 - message: - Bug#16900358 FIX FOR CVE-2012-5611 IS INCOMPLETE - - Description: Fix for bug CVE-2012-5611 (bug 67685) is - incomplete. The ACL_KEY_LENGTH-sized buffers in acl_get() and - check_grant_db() can be overflown by up to two bytes. That's - probably not enough to do anything more serious than crashing - mysqld. - Analysis: In acl_get() when "copy_length" is calculated it - just adding the variable lengths. But when we are using them - with strmov() we are adding +1 to each. This will lead to a - three byte buffer overflow (i.e two +1's at strmov() and one - byte for the null added by strmov() function). Similarly it - happens for check_grant_db() function as well. - Fix: We need to add "+2" to "copy_length" in acl_get() - and "+1" to "copy_length" in check_grant_db(). ------------------------------------------------------------- -revno: 4509 -committer: Sujatha Sivakumar -branch nick: Bug17429677_mysql-5.5 -timestamp: Wed 2013-10-16 11:49:00 +0530 -message: - Bug#17429677:LAST ARGUMENT OF LOAD DATA ...SET ...STATEMENT - REPEATED TWICE IN BINLOG - - Problem: - ======= - If LOAD DATA ... SET ... is used the last argument of SET is - repeated twice in replication binlog. - - Analysis: - ======== - LOAD DATA statements are reconstructed once again before - they are written to the binary log. When SET clauses are - specified as part of LOAD DATA statement, these SET clause - user command strings need to be stored in order to rebuild - the original user command. During parsing each column and - the value in the SET command are stored in two differenet - lists. All the values are stored in a string list. - - When SET expression has more than one value as shown in the - following example: - SET a = @a, b = CONCAT(@b, '| 123456789'); - - Parser extracts values in the following manner i.e Item name - , value string, actual length of the value of the item with - in the string. - - Item a: - Value for a:"= @a, b = CONCAT(@b, '| 123456789') - str_length = 4 - Item b: - Value for b:"= CONCAT(@b, '| 123456789') - str_length = 27 - - During reconstructing the LOAD DATA command the above - strings are retrived as it is and appended to the LOAD DATA - statement. Hence it becomes as shown below. - - SET `a`= @a, b = CONCAT(@b, '| 123456789'), - `b`= CONCAT(@b, '| 123456789') - - Fix: - === - During reconstruction of SET command, retrieve exact item - value string rather than reading the entire string. ------------------------------------------------------------- -revno: 4508 -committer: Sreedhar.S -branch nick: mysql-5.5 -timestamp: Wed 2013-10-16 11:05:20 +0530 -message: - Fix for Bug 17584523 - LICENSE AND DOCUMENTATION FILES MISSING FROM WINDOWS MSI PACKAGE ------------------------------------------------------------- -revno: 4507 [merge] -committer: Nuno Carvalho -branch nick: mysql-5.5 -timestamp: Mon 2013-10-14 15:51:09 +0100 -message: - WL#7266: Dump-thread additional concurrency tests - - Merge from mysql-5.1 into mysql-5.5. - ------------------------------------------------------------ - revno: 2661.844.77 - committer: Nuno Carvalho - branch nick: mysql-5.1 - timestamp: Mon 2013-10-14 15:45:12 +0100 - message: - WL#7266: Dump-thread additional concurrency tests - - This worklog aims at testing the two following scenarios: - - 1) Whenever the mysql_binlog_send method (dump thread) - reaches the end of file when reading events from the binlog, before - checking if it should wait for more events, there was a test to - check if the file being read was still active, i.e, it was the last - known binlog. However, it was possible that something was written to - the binary log and then a rotation would happen, after EOF was - detected and before the check for active was performed. In this - case, the end of the binary log would not be read by the dump - thread, and this would cause the slave to lose updates. - This test verifies that the problem has been fixed. It waits during - this window while forcing a rotation in the binlog. - - 2) Verify dump thread can send events in active file, correctly after - encountering an IO error. ------------------------------------------------------------- -revno: 4506 -committer: Satya Bodapati -branch nick: mysql-5.5 -timestamp: Wed 2013-10-09 18:42:27 +0530 -message: - BUG#17446090 - TESTCASE INNODB_BUG16752251.TEST FAILS RANDOMLY ON PB2 - - DBUG_SUICIDE() hangs valgrind. Disable the test under valgrind ------------------------------------------------------------- -revno: 4505 -committer: Sreedhar.S -branch nick: mysql-5.5 -timestamp: Wed 2013-10-09 17:08:45 +0530 -message: - BUG 17560050 - MYSQL_INSTALL_DB SCRIPT FAILING WITH RESOLVEIP ISSUES. ------------------------------------------------------------- -revno: 4504 -committer: Praveenkumar Hulakund -branch nick: mysql-5.5 -timestamp: Wed 2013-10-09 13:32:31 +0530 -message: - Bug#17474166 - EXECUTING STATEMENT LIKE 'SHOW ENGINE INNODB' - AND 'KILL SESSION' LEAD TO CRASH - - Analysis: - -------- - This situation occurs when the connection executes query - "show engine innodb status" and this connection is killed by - executing statement "kill " by another connection. - - In function "innodb_show_status", function "stat_print" - is called to print the status but return value of function - is not checked. After killing connection, if write to - connection fails then error is returned and same is set - in Diagnostic area. Since FALSE is returned from - "innodb_show_status" now, assert to check no error - is set in function "set_eof_status" (called from - my_eof) is failing. - - Fix: - ---- - Changed code to check return value of function "stat_print" - in "innodb_show_status". ------------------------------------------------------------- -revno: 4503 -committer: Sreedhar.S -branch nick: mysql-5.5 -timestamp: Wed 2013-10-09 11:10:46 +0530 -message: - Bug 13878021 - WINDOWS PACKAGE THAT INCLUDES .PDB FILES FOR INTERMEDIATE LIBRARIES USED ------------------------------------------------------------- -revno: 4502 -committer: Praveenkumar Hulakund -branch nick: mysql_5_5 -timestamp: Mon 2013-10-07 18:17:26 +0530 -message: - Bug#11745656 - KILL THREAD -> ERROR: "SERVER SHUTDOWN IN PROGRESS" - - Fixing pb2 test failure for 5.5 version on solaris platform. ------------------------------------------------------------- -revno: 4501 [merge] -committer: Kent Boortz -branch nick: mysql-5.5 -timestamp: Mon 2013-10-07 13:05:49 +0200 -message: - Corrections of copyright headers (RE-request 45781) - ------------------------------------------------------------ - revno: 2661.844.76 [merge] - committer: Kent Boortz - branch nick: mysql-5.1 - timestamp: Mon 2013-10-07 12:44:38 +0200 - message: - Corrections of copyright headers (RE-request 45781) ------------------------------------------------------------- -revno: 4500 [merge] -committer: Kent Boortz -branch nick: mysql-5.5 -timestamp: Mon 2013-10-07 12:45:05 +0200 -message: - Corrections of copyright headers (RE-request 45781) - ------------------------------------------------------------ - revno: 4495.1.1 [merge] - committer: Kent Boortz - branch nick: mysql-5.5 - timestamp: Sun 2013-10-06 18:16:09 +0200 - message: - Corretions of copyright headers (RE-request 45781) - ------------------------------------------------------------ - revno: 2661.851.1 - committer: Kent Boortz - branch nick: mysql-5.1 - timestamp: Fri 2013-10-04 13:51:13 +0200 - message: - Corretions of copyright headers (RE-request 45781) ------------------------------------------------------------- -revno: 4499 -committer: Praveenkumar Hulakund -branch nick: mysql_5_5 -timestamp: Mon 2013-10-07 14:03:57 +0530 -message: - Bug#11745656 - KILL THREAD -> ERROR: "SERVER SHUTDOWN IN PROGRESS" - - Fixing pb2 test failure. ------------------------------------------------------------- -revno: 4498 [merge] -committer: Yasufumi Kinoshita -branch nick: mysql-5.5 -timestamp: Mon 2013-10-07 15:17:56 +0900 -message: - Merge mysql-5.1 to mysql-5.5. - ------------------------------------------------------------ - revno: 2661.844.75 - committer: Yasufumi Kinoshita - branch nick: mysql-5.1 - timestamp: Mon 2013-10-07 15:16:31 +0900 - message: - Bug#17431533 : FAILING ASSERTION: INDEX->PAGE != 0XFFFFFFFF AFTER DISCARDING TABLESPACE - - ha_innobase::records_in_range() should return HA_POS_ERROR for the table during discarded without requesting pages. - The later other handler method should treat the error correctly. - - Approved by Sunny in rb#3433 ------------------------------------------------------------- -revno: 4497 -committer: Praveenkumar Hulakund -branch nick: mysql_5_5 -timestamp: Mon 2013-10-07 09:49:32 +0530 -message: - Bug#11745656 - KILL THREAD -> ERROR: "SERVER SHUTDOWN IN PROGRESS" - - Fixing pb2 test failure for 5.5 version on solaris platform. ------------------------------------------------------------- -revno: 4496 -committer: Praveenkumar Hulakund -branch nick: mysql_5_5 -timestamp: Sat 2013-10-05 15:29:02 +0530 -message: - Bug#11745656 - KILL THREAD -> ERROR: "SERVER SHUTDOWN IN PROGRESS" - - Description: - ------------ - There are 2 issues reported in the bug report, - - 1. One session running a "long" select, then, from the other - session, you kill that first one, while select is - running, and it receives that message "Server shutdown in - progress". - Reported Date: 02-Apr-2006 - - => Looks like this isuse is already fixed in 2009 by the patch - pushed for bug28141. - - 2. Killing query which goes to filesort, logs error entries like: - - 120416 9:17:28 [ERROR] mysqld: Sort aborted: Server shutdown in - progress - 120416 9:18:48 [ERROR] mysqld: Sort aborted: Server shutdown in - progress - 120416 9:19:39 [ERROR] mysqld: Sort aborted: Server shutdown in - progress - Reported Date: 16-Apr-2012 - - => This issue is introduced in 5.5+ versions. Fixing this issue - in this patch. - - - Analysis: - --------- - In function "filesort()", on error we are logging error message. - To the error message, the message related THD::killed_errno is - also appeneded, if it is set.(THD::kill_errno value is obtained - by calling member function THD::killed_errno) - - In the scenario mentioned in this bug report, when we kill the - connection, THD::kill_errno is set to the THD::KILL_CONNECTION. - Enum type THD::KILL_CONNECTION corressponds to value - ER_SERVER_SHUTDOWN. Because of this, "Server shutdown in ...." is - appended to the message logged. - - Fix: - ---- - Modified code of "filesort()" function to append "KILL_QUERY" - status to error message when thread is killed and server - shutdown is not in progress. ------------------------------------------------------------- -revno: 4495 -committer: Marko M?kel? -branch nick: mysql-5.5 -timestamp: Tue 2013-10-01 14:17:35 +0300 -message: - Followup to Bug#17446090 fix: - - Now that ibuf_change_buffering_debug a.k.a. ibuf_debug should work - reliably (no "surprise" merges), make some tests stricter - (require that the server crashes where we expect it to). ------------------------------------------------------------- -revno: 4494 -committer: Mattias Jonsson -branch nick: b14621190-55 -timestamp: Tue 2013-10-01 10:05:45 +0200 -message: - Bug#14621190: HA_INNOBASE::INDEX_NEXT SKIPS A RECORD IF PREVIOUS - INDEX_READ_MAP HAD NO MATCH - - If index_read_map is called for exact search and no matching records - exists it will position the cursor on the next record, but still having the - relative position to BTR_PCUR_ON. - This will make a call for index_next to read yet another next record, - instead of returning the record the cursor points to. - - Fixed by setting pcur->rel_pos = BTR_PCUR_BEFORE if an exact - [prefix] search is done, but failed. - - Also avoids optimistic restoration if rel_pos != BTR_PCUR_ON, - since btr_cur may be different than old_rec. - - rb#3324, approved by Marko and Jimmy ------------------------------------------------------------- -revno: 4493 -committer: Sreedhar.S -branch nick: mysql-5.5 -timestamp: Mon 2013-09-30 13:01:17 +0530 -message: - Bug #16619754 - MYSQL_INSTALL_DB.PL FAILS TO CREATE DATABASE ON WINDOWS. - - As this mysql_install_db.pl file has always generated lots of confusion on Windows. This fix will make sure to get it removed only from Windows ------------------------------------------------------------- -revno: 4492 -committer: Sreedhar.S -branch nick: mysql-5.5 -timestamp: Mon 2013-09-30 12:41:22 +0530 -message: - Fix for Bug:16053094 - Registry redirection was improper and hence not able to pick the value for the OLDERVERSION property. as a result in the install upgrade dialog null value wa being passed. ------------------------------------------------------------- -revno: 4491 -committer: Sreedhar.S -branch nick: mysql-5.5 -timestamp: Mon 2013-09-30 12:29:10 +0530 -message: - Fix to copy missing pdb files BUG 13878021 ------------------------------------------------------------- -revno: 4490 -committer: Yasufumi Kinoshita -branch nick: mysql-5.5 -timestamp: Mon 2013-09-30 15:02:54 +0900 -message: - Adjustment for fix for Bug#11758196 - - log_buffer_extend() should fill the new buffer with 0. ------------------------------------------------------------- -revno: 4489 -committer: Yasufumi Kinoshita -branch nick: mysql-5.5 -timestamp: Mon 2013-09-30 13:41:48 +0900 -message: - Bug#11758196 : INNODB ASSERTION FAILURE WHEN CONVERTING FROM MYISAM TO INNODB - - Changed to try to extend log buffer instead of crash, when log size is too large for the size. - - Approved by Marko in rb#3229 ------------------------------------------------------------- -revno: 4488 [merge] -committer: Satya Bodapati -branch nick: mysql-5.5 -timestamp: Fri 2013-09-27 18:32:13 +0530 -message: - Merge fix for BUG#17446090 from mysql-5.1 to mysql-5.5 - - The testcase for this bug fails randomly due to two reasons. - 1. Due to ibuf merge happening background - 2. Due to dict stats update which brings the evicted page back into - buffer pool. - - Fix ibuf_contract_ext() to not do any merges with ibuf_debug enabled and - also changed dict_stats_update() to return fake statistics without - bringing the secondary index pages into buffer pool. - - Approved by Marko. rb#3419 - ------------------------------------------------------------ - revno: 2661.844.74 - committer: Satya Bodapati - branch nick: mysql-5.1 - timestamp: Fri 2013-09-27 18:30:46 +0530 - message: - BUG#17446090 - TESTCASE INNODB_BUG16752251.TEST FAILS RANDOMLY ON PB2 - - Enable disabled testcases. ------------------------------------------------------------- -revno: 4487 -committer: Shivji Kumar Jha -branch nick: mysql-5.5 -timestamp: Fri 2013-09-27 01:24:16 +0530 -message: - BUG#16580366- MTR TESTS FAILING SPORADICALLY ON PB2 (5.5, 5.6 AND 5.7) - DURING INNODB RECOVERY - - Problem: - ======= - The connection 'master' is dropped by mysqltest after - rpl_end.inc. At this point, dropping temporary tables - at the connection 'master' are not synced at slave. - So, the temporary tables replicated from master remain - on slave leading to an inconsistent close of the test. - The following test thus complains about the presence of - temporary table(s) left over from the previous test. - - Fix: - === - - Put explicit drop commands in replication tests so - that the temporary tables are dropped at slave as well. - - Added the check for Slave_open_temp_tables in - mtr_check.sql to warn about the remaining temporary - table, if any, at the close of a test. ------------------------------------------------------------- -revno: 4486 -committer: Sujatha Sivakumar -branch nick: Bug17327454_mysql-5.5 -timestamp: Mon 2013-09-23 12:13:37 +0530 -message: - Bug#17327454:SEMI-SYNC REPLICATION MASTER CRASH WHEN SET - RPL_SEMI_SYNC_MASTER_ENABLED OFF. - - Problem: - ======= - If master is waiting for a reply from slave, at this time - set global rpl_semi_sync_master_enabled=OFF, the master - server will crash. - - Analysis: - ======== - When master is waiting for a reply from slave, at this time - if semi sync is switched off on master, during switch off if - active transactions are present the transactions will be - cleared and "active_tranxs_" variable will be set to NULL. - - When the waiting master connection finds that semi sync is - switched of it tries to access "active_tranxs_" without - checking if the transaction list exists or not. Accessing - NULL transaction list causes the crash. - - Fix: - === - A check has been added to see a valid list exists before - accessing the "active_tranxs_". ------------------------------------------------------------- -revno: 4485 [merge] -committer: Hery Ramilison -branch nick: mysql-5.5 -timestamp: Fri 2013-09-20 21:42:40 +0200 -message: - Upmerge of the 5.1.72 build - ------------------------------------------------------------ - revno: 2661.844.73 [merge] - author: hery.ramilison@oracle.com - committer: Hery Ramilison - branch nick: mysql-5.1 - timestamp: Fri 2013-09-20 21:08:08 +0200 - message: - Merge from mysql-5.1.72-release - ------------------------------------------------------------ - revno: 2661.850.5 - tags: mysql-5.1.72 - committer: Balasubramanian Kandasamy - branch nick: mysql-5.1.72-release - timestamp: Mon 2013-09-09 20:07:12 +0200 - message: - Reverted the changes to spec file to ignore mysqld_safe.pid file, updated the logic to get the correct count of PID files - ------------------------------------------------------------ - revno: 2661.850.4 - committer: Hery Ramilison - branch nick: mysql-5.1.72-release - timestamp: Mon 2013-09-09 18:58:08 +0200 - message: - Committing patch from venkata.sidagam@oracle.com for Bug#16776528 - ------------------------------------------------------------ - revno: 2661.850.3 - committer: Hery Ramilison - branch nick: mysql-5.1.72-release - timestamp: Tue 2013-09-03 18:37:46 +0200 - message: - Fixing sles11 build that /usr/lib/mysql/plugin is not owned by a package - ------------------------------------------------------------ - revno: 2661.850.2 - committer: Balasubramanian Kandasamy - branch nick: mysql-5.1.72-release - timestamp: Fri 2013-08-30 17:14:46 +0200 - message: - Fix to ignore mysqld_safe.pid - ------------------------------------------------------------ - revno: 2661.850.1 - committer: Balasubramanian Kandasamy - branch nick: mysql-5.1.72-release - timestamp: Thu 2013-08-29 14:42:55 +0200 - message: - Fix for Bug#17377159, ignore mysqld_safe.pid file created by mysqld_safe script ------------------------------------------------------------- -revno: 4484 -committer: Tor Didriksen -branch nick: 5.5 -timestamp: Fri 2013-09-20 16:10:31 +0200 -message: - Bug#17435338 ADD A -DWITH_ASAN SWITCH/OPTION TO OUR CMAKE SCRIPTS - - Tested with: - gcc (GCC) 4.8.1 20130603 (Red Hat 4.8.1-1) - - clang version 3.1 (tags/RELEASE_31/final) - Target: x86_64-apple-darwin10.8.0 ------------------------------------------------------------- -revno: 4483 [merge] -author: balasubramanian.kandasamy@oracle.com -committer: Balasubramanian Kandasamy -branch nick: mysql-5.5 -timestamp: Fri 2013-09-20 11:34:06 +0200 -message: - Merge from mysql-5.5.34-release - ------------------------------------------------------------ - revno: 4457.1.5 - tags: mysql-5.5.34 - committer: Balasubramanian Kandasamy - branch nick: mysql-5.5.34-release - timestamp: Mon 2013-09-09 19:49:44 +0200 - message: - Reverted the changes to spec file, updated the logic to get the correct count of PID files +This is a first release, this file is supposed to be empty diff -Nru mysql-5.5-5.5.35+dfsg/Docs/INFO_SRC mysql-5.5-5.5.43/Docs/INFO_SRC --- mysql-5.5-5.5.35+dfsg/Docs/INFO_SRC 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/Docs/INFO_SRC 2015-02-27 08:30:34.000000000 +0000 @@ -1,7 +1,7 @@ -revision-id: balasubramanian.kandasamy@oracle.com-20131105070343-fgb4ljwrh1hzgaeh -date: 2013-11-05 08:03:43 +0100 -build-date: 2013-11-05 08:12:45 +0100 -revno: 4535 -branch-nick: mysql-5.5.35-release +commit: 367802ceef18088c24fcda705440e0d87930188b +date: 2015-02-27 09:14:35 +0100 +build-date: 2015-02-27 09:18:18 +0100 +short: 367802c +branch: mysql-5.5.43-release -MySQL source 5.5.35 +MySQL source 5.5.43 diff -Nru mysql-5.5-5.5.35+dfsg/Docs/INSTALL-BINARY mysql-5.5-5.5.43/Docs/INSTALL-BINARY --- mysql-5.5-5.5.35+dfsg/Docs/INSTALL-BINARY 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/Docs/INSTALL-BINARY 2015-02-27 08:30:42.000000000 +0000 @@ -1,60 +1,76 @@ - -2.2. Installing MySQL on Unix/Linux Using Generic Binaries +2.2 Installing MySQL on Unix/Linux Using Generic Binaries Oracle provides a set of binary distributions of MySQL. These - include binary distributions in the form of compressed tar files - (files with a .tar.gz extension) for a number of platforms, as - well as binaries in platform-specific package formats for selected - platforms. - - This section covers the installation of MySQL from a compressed - tar file binary distribution. For other platform-specific package - formats, see the other platform-specific sections. For example, - for Windows distributions, see Section 2.3, "Installing MySQL on + include binary distributions in the form of compressed tar + files (files with a .tar.gz extension) for a number of + platforms, as well as binaries in platform-specific package + formats for selected platforms. + + This section covers the installation of MySQL from a + compressed tar file binary distribution. For other + platform-specific package formats, see the other + platform-specific sections. For example, for Windows + distributions, see Section 2.3, "Installing MySQL on Microsoft Windows." - To obtain MySQL, see Section 2.1.3, "How to Get MySQL." + To obtain MySQL, see Section 2.1.2, "How to Get MySQL." - MySQL compressed tar file binary distributions have names of the - form mysql-VERSION-OS.tar.gz, where VERSION is a number (for - example, 5.5.36), and OS indicates the type of operating system - for which the distribution is intended (for example, pc-linux-i686 - or winx64). - - To install MySQL from a compressed tar file binary distribution, - your system must have GNU gunzip to uncompress the distribution - and a reasonable tar to unpack it. If your tar program supports - the z option, it can both uncompress and unpack the file. + MySQL compressed tar file binary distributions have names of + the form mysql-VERSION-OS.tar.gz, where VERSION is a number + (for example, 5.5.44), and OS indicates the type of operating + system for which the distribution is intended (for example, + pc-linux-i686 or winx64). + + To install MySQL from a compressed tar file binary + distribution, your system must have GNU gunzip to uncompress + the distribution and a reasonable tar to unpack it. If your + tar program supports the z option, it can both uncompress and + unpack the file. GNU tar is known to work. The standard tar provided with some - operating systems is not able to unpack the long file names in the - MySQL distribution. You should download and install GNU tar, or if - available, use a preinstalled version of GNU tar. Usually this is - available as gnutar, gtar, or as tar within a GNU or Free Software - directory, such as /usr/sfw/bin or /usr/local/bin. GNU tar is - available from http://www.gnu.org/software/tar/. + operating systems is not able to unpack the long file names + in the MySQL distribution. You should download and install + GNU tar, or if available, use a preinstalled version of GNU + tar. Usually this is available as gnutar, gtar, or as tar + within a GNU or Free Software directory, such as /usr/sfw/bin + or /usr/local/bin. GNU tar is available from + http://www.gnu.org/software/tar/. + Warning + + If you have previously installed MySQL using your operating + system native package management system, such as yum or + apt-get, you may experience problems installing using a + native binary. Make sure your previous MySQL installation has + been removed entirely (using your package management system), + and that any additional files, such as old versions of your + data files, have also been removed. You should also check the + existence of configuration files such as /etc/my.cnf or the + /etc/mysql directory have been deleted. Warning - If you have previously installed MySQL using your operating system - native package management system, such as yum or apt-get, you may - experience problems installing using a native binary. Make sure - your previous MySQL previous installation has been removed - entirely (using your package management system), and that any - additional files, such as old versions of your data files, have - also been removed. You should also check the existence of - configuration files such as /etc/my.cnf or the /etc/mysql - directory have been deleted. - - If you run into problems and need to file a bug report, please use - the instructions in Section 1.7, "How to Report Bugs or Problems." - - On Unix, to install a compressed tar file binary distribution, - unpack it at the installation location you choose (typically - /usr/local/mysql). This creates the directories shown in the - following table. + MySQL has a dependency on the libaio library. The + mysql_install_db and subsequent mysqld_safe steps will fail + if this library is not installed locally. If necessary, + install it using the appropriate package manager. For + example, on Yum-based systems: +shell> yum search libaio # search for info +shell> yum install libaio # install library + + Or, on APT-based systems: +shell> apt-cache search libaio # search for info +shell> apt-get install libaio1 # install library + + If you run into problems and need to file a bug report, + please use the instructions in Section 1.7, "How to Report + Bugs or Problems." + + On Unix, to install a compressed tar file binary + distribution, unpack it at the installation location you + choose (typically /usr/local/mysql). This creates the + directories shown in the following table. - Table 2.3. MySQL Installation Layout for Generic Unix/Linux Binary - Package + Table 2.3 MySQL Installation Layout for Generic Unix/Linux + Binary Package Directory Contents of Directory bin Client programs and the mysqld server data Log files, databases @@ -67,25 +83,25 @@ sample configuration files, SQL for database installation sql-bench Benchmarks - Debug versions of the mysqld binary are available as mysqld-debug. - To compile your own debug version of MySQL from a source - distribution, use the appropriate configuration options to enable - debugging support. For more information on compiling from source, - see Section 2.10, "Installing MySQL from Source." + Debug versions of the mysqld binary are available as + mysqld-debug. To compile your own debug version of MySQL from + a source distribution, use the appropriate configuration + options to enable debugging support. For more information on + compiling from source, see Section 2.9, "Installing MySQL + from Source." - To install and use a MySQL binary distribution, the basic command - sequence looks like this: + To install and use a MySQL binary distribution, the basic + command sequence looks like this: shell> groupadd mysql shell> useradd -r -g mysql mysql shell> cd /usr/local shell> tar zxvf /path/to/mysql-VERSION-OS.tar.gz shell> ln -s full-path-to-mysql-VERSION-OS mysql shell> cd mysql -shell> chown -R mysql . -shell> chgrp -R mysql . -shell> scripts/mysql_install_db --user=mysql shell> chown -R root . shell> chown -R mysql data +shell> chgrp -R mysql . +shell> scripts/mysql_install_db --user=mysql # Next command is optional shell> cp support-files/my-medium.cnf /etc/my.cnf shell> bin/mysqld_safe --user=mysql & @@ -96,697 +112,1091 @@ installing a binary distribution follows. Note - This procedure assumes that you have root (administrator) access - to your system. Alternatively, you can prefix each command using - the sudo (Linux) or pfexec (OpenSolaris) command. - - The procedure does not set up any passwords for MySQL accounts. - After following the procedure, proceed to Section 2.11.2, - "Securing the Initial MySQL Accounts." + This procedure assumes that you have root (administrator) + access to your system. Alternatively, you can prefix each + command using the sudo (Linux) or pfexec (OpenSolaris) + command. + + The procedure does not set up any passwords for MySQL + accounts. After following the procedure, proceed to Section + 2.10.2, "Securing the Initial MySQL Accounts." Create a mysql User and Group - If your system does not already have a user and group for mysqld - to run as, you may need to create one. The following commands add - the mysql group and the mysql user. You might want to call the - user and group something else instead of mysql. If so, substitute - the appropriate name in the following instructions. The syntax for - useradd and groupadd may differ slightly on different versions of - Unix, or they may have different names such as adduser and - addgroup. + If your system does not already have a user and group for + mysqld to run as, you may need to create one. The following + commands add the mysql group and the mysql user. You might + want to call the user and group something else instead of + mysql. If so, substitute the appropriate name in the + following instructions. The syntax for useradd and groupadd + may differ slightly on different versions of Unix, or they + may have different names such as adduser and addgroup. shell> groupadd mysql shell> useradd -r -g mysql mysql Note Because the user is required only for ownership purposes, not - login purposes, the useradd command uses the -r option to create a - user that does not have login permissions to your server host. - Omit this option to permit logins for the user (or if your useradd - does not support the option). + login purposes, the useradd command uses the -r option to + create a user that does not have login permissions to your + server host. Omit this option to permit logins for the user + (or if your useradd does not support the option). Obtain and Unpack the Distribution - Pick the directory under which you want to unpack the distribution - and change location into it. The example here unpacks the - distribution under /usr/local. The instructions, therefore, assume - that you have permission to create files and directories in - /usr/local. If that directory is protected, you must perform the - installation as root. + Pick the directory under which you want to unpack the + distribution and change location into it. The example here + unpacks the distribution under /usr/local. The instructions, + therefore, assume that you have permission to create files + and directories in /usr/local. If that directory is + protected, you must perform the installation as root. shell> cd /usr/local Obtain a distribution file using the instructions in Section - 2.1.3, "How to Get MySQL." For a given release, binary + 2.1.2, "How to Get MySQL." For a given release, binary distributions for all platforms are built from the same MySQL source distribution. - Unpack the distribution, which creates the installation directory. - Then create a symbolic link to that directory. tar can uncompress - and unpack the distribution if it has z option support: + Unpack the distribution, which creates the installation + directory. Then create a symbolic link to that directory. tar + can uncompress and unpack the distribution if it has z option + support: shell> tar zxvf /path/to/mysql-VERSION-OS.tar.gz shell> ln -s full-path-to-mysql-VERSION-OS mysql - The tar command creates a directory named mysql-VERSION-OS. The ln - command makes a symbolic link to that directory. This enables you - to refer more easily to the installation directory as - /usr/local/mysql. - - If your tar does not have z option support, use gunzip to unpack - the distribution and tar to unpack it. Replace the preceding tar - command with the following alternative command to uncompress and - extract the distribution: + The tar command creates a directory named mysql-VERSION-OS. + The ln command makes a symbolic link to that directory. This + enables you to refer more easily to the installation + directory as /usr/local/mysql. + + If your tar does not have z option support, use gunzip to + unpack the distribution and tar to unpack it. Replace the + preceding tar command with the following alternative command + to uncompress and extract the distribution: shell> gunzip < /path/to/mysql-VERSION-OS.tar.gz | tar xvf - Perform Postinstallation Setup - The remainder of the installation process involves setting up the - configuration file, creating the core databases, and starting the - MySQL server. For next steps, see Section 2.11, "Postinstallation - Setup and Testing." - Note - - The accounts that are listed in the MySQL grant tables initially - have no passwords. After starting the server, you should set up - passwords for them using the instructions in Section 2.11.2, - "Securing the Initial MySQL Accounts." - - Copyright (c) 1997, 2013, Oracle and/or its affiliates. All rights - reserved. Legal Notices - -2.3. Installing MySQL on Microsoft Windows - - MySQL for Microsoft Windows is available in a number of different - forms. A Microsoft Windows operating system such as Windows XP, - Windows Vista, Windows 7, Windows 8, Windows Server 2003, Windows - Server 2008, or Windows Server 2012. Both 32-bit and 64-bit - versions are supported. For supported platform information, see - http://www.mysql.com/support/supportedplatforms/database.html. - - In addition to running MySQL as a standard application, you can - also run the MySQL server as a Windows service. By using a service - you can monitor and control the operation of the server through - the standard Windows service management tools. For more - information, see Section 2.3.7.7, "Starting MySQL as a Windows - Service." + The remainder of the installation process involves setting up + the configuration file, creating the core databases, and + starting the MySQL server. For next steps, see Section 2.10, + "Postinstallation Setup and Testing." + Note + + The accounts that are listed in the MySQL grant tables + initially have no passwords. After starting the server, you + should set up passwords for them using the instructions in + Section 2.10.2, "Securing the Initial MySQL Accounts." +2.3 Installing MySQL on Microsoft Windows + + There are several different methods to install MySQL on + Microsoft Windows. + +Simple Installation Method + + The simplest and recommended method is to download MySQL + Installer (for Windows) and let it install and configure all + of the MySQL products on your system. Here is how: - Generally, you should install MySQL on Windows using an account - that has administrator rights. Otherwise, you may encounter - problems with certain operations such as editing the PATH - environment variable or accessing the Service Control Manager. - Once installed, MySQL does not need to be executed using a user - with Administrator privileges. + * Download MySQL Installer from + http://dev.mysql.com/downloads/installer/ and execute it. + Note + Unlike the standard MySQL Installer, the smaller + "web-community" version does not bundle any MySQL + applications but it will download the MySQL products you + choose to install. + + * Choose the appropriate Setup Type for your system. + Typically you will choose Developer Default to install + MySQL server and other MySQL tools related to MySQL + development, helpful tools like MySQL Workbench. Or, + choose the Custom setup type to manually select your + desired MySQL products. + Note + Multiple versions of MySQL server can exist on a single + system. You can choose one or multiple versions. - For a list of limitations within the Windows version of MySQL, see - Section E.10.6, "Windows Platform Limitations." + * Complete the installation process by following the MySQL + Installation wizard's instructions. This will install + several MySQL products and start the MySQL server. + + * MySQL is now installed. You probably configured MySQL as + a service that will automatically start MySQL server + every time you restart your system. + + Note + + You probably also installed other helpful MySQL products like + MySQL Workbench and MySQL Notifier on your system. Consider + loading Chapter 26, "MySQL Workbench" to check your new MySQL + server connection, and Section 2.3.4, "MySQL Notifier" to + view the connection's status. By default, these two programs + automatically start after installing MySQL. + + This process also installs the MySQL Installer application on + your system, and later you can use MySQL Installer to upgrade + or reconfigure your MySQL products. + +Additional Installation Information + + MySQL is available for Microsoft Windows, for both 32-bit and + 64-bit versions. For supported Windows platform information, + see + http://www.mysql.com/support/supportedplatforms/database.html + . + + It is possible to run MySQL as a standard application or as a + Windows service. By using a service, you can monitor and + control the operation of the server through the standard + Windows service management tools. For more information, see + Section 2.3.7.7, "Starting MySQL as a Windows Service." + + Generally, you should install MySQL on Windows using an + account that has administrator rights. Otherwise, you may + encounter problems with certain operations such as editing + the PATH environment variable or accessing the Service + Control Manager. Once installed, MySQL does not need to be + executed using a user with Administrator privileges. + + For a list of limitations on the use of MySQL on the Windows + platform, see Section D.10.6, "Windows Platform Limitations." In addition to the MySQL Server package, you may need or want additional components to use MySQL with your application or - development environment. These include, but are not limited to: + development environment. These include, but are not limited + to: - * If you plan to connect to the MySQL server using ODBC, you - need a Connector/ODBC driver. For more information, including - installation and configuration instructions, see Section 22.1, - "MySQL Connector/ODBC." - - * If you plan to use MySQL server with .NET applications, you - need the Connector/Net driver. For more information, including - installation and configuration instructions, see Section 22.2, - "MySQL Connector/Net." + * To connect to the MySQL server using ODBC, you must have + a Connector/ODBC driver. For more information, including + installation and configuration instructions, see MySQL + Connector/ODBC Developer Guide + (http://dev.mysql.com/doc/connector-odbc/en/index.html). + Note + MySQL Installer will install and configure Connector/ODBC + for you. + + * To use MySQL server with .NET applications, you must have + the Connector/Net driver. For more information, including + installation and configuration instructions, see MySQL + Connector/Net Developer Guide + (http://dev.mysql.com/doc/connector-net/en/index.html). + Note + MySQL Installer will install and configure Connector/NET + for you. MySQL distributions for Windows can be downloaded from - http://dev.mysql.com/downloads/. See Section 2.1.3, "How to Get - MySQL." + http://dev.mysql.com/downloads/. See Section 2.1.2, "How to + Get MySQL." - MySQL for Windows is available in several distribution formats, - detailed below. Generally speaking, you should use MySQL - Installer. It contains more features and MySQL products than the - older MSI, is simpler to use than the ZIP file, and you need no - additional tools to get MySQL up and running. MySQL Installer will - automatically install MySQL Server, install additional MySQL - products, create an options file, starts the server, and allow you - to create default user accounts. For more information on choosing - a package, see Section 2.3.2, "Choosing An Installation Package." - - MySQL for Windows is available in several distribution formats, - detailed below. Generally speaking, you should use a binary - distribution that includes an installer. It is simpler to use than - the others, and you need no additional tools to get MySQL up and - running. The installer for the Windows version of MySQL, combined - with a GUI Config Wizard, automatically installs MySQL, creates an - option file, starts the server, and secures the default user - accounts. - - * Binary installer distribution. There are two different - installable distributions that come packaged as a Microsoft - Windows Installer (MSI) package that you can install manually - or automatically on your systems. The older MSI package that - contains all the files you need to install and configure MySQL - server, but no additional components, and the preferred MySQL - Installer package that includes MySQL Server and additional - MySQL products including MySQL Workbench, MySQL Notifier, and - MySQL for Excel. And MySQL Installer can also be used to - upgrade these product in the future. For more information on - choosing a package, see Section 2.3.2, "Choosing An - Installation Package" - For instructions on installing MySQL using MySQL Installer, - see Section 2.3.3, "Installing MySQL on Microsoft Windows - Using MySQL Installer." - - * Standard binary distribution format packaged as a Zip file - containing all of the necessary files that you unpack into - your chosen location. This package contains all of the files - in the full Windows MSI Installer package, but does not - include an installation program. - For instructions on installing MySQL using the Zip file, see - Section 2.3.7, "Installing MySQL on Microsoft Windows Using a - noinstall Zip Archive." - - * The source distribution contains all the code and support - files for building the executables using the Visual Studio - compiler system. - For instructions on building MySQL from source on Windows, see - Section 2.10, "Installing MySQL from Source." + MySQL for Windows is available in several distribution + formats, detailed below. Generally speaking, you should use + MySQL Installer. It contains more features and MySQL products + than the older MSI, is simpler to use than the Zip file, and + you need no additional tools to get MySQL up and running. + MySQL Installer automatically installs MySQL Server and + additional MySQL products, creates an options file, starts + the server, and enables you to create default user accounts. + For more information on choosing a package, see Section + 2.3.2, "Choosing An Installation Package." + + * Binary installer distributions. There are two different + installable distributions that come packaged as a + Microsoft Windows Installer (MSI) package that you can + install manually or automatically on your systems. The + preferred MySQL Installer package includes MySQL Server + and additional MySQL products including MySQL Workbench, + MySQL Notifier, and MySQL for Excel. MySQL Installer can + also be used to upgrade these product in the future. The + older MSI package contains all the files you need to + install and configure MySQL server, but no additional + components. + For instructions on installing MySQL using MySQL + Installer, see Section 2.3.3, "Installing MySQL on + Microsoft Windows Using MySQL Installer." + + * The standard binary distribution (packaged as a Zip file) + contains all of the necessary files that you unpack into + your chosen location. This package contains all of the + files in the full Windows MSI Installer package, but does + not include an installation program. + For instructions on installing MySQL using the Zip file, + see Section 2.3.7, "Installing MySQL on Microsoft Windows + Using a noinstall Zip Archive." + + * The source distribution format contains all the code and + support files for building the executables using the + Visual Studio compiler system. + For instructions on building MySQL from source on + Windows, see Section 2.9, "Installing MySQL from Source." MySQL on Windows considerations: * Large Table Support - If you need tables with a size larger than 4GB, install MySQL - on an NTFS or newer file system. Do not forget to use MAX_ROWS - and AVG_ROW_LENGTH when you create tables. See Section - 13.1.17, "CREATE TABLE Syntax." + If you need tables with a size larger than 4GB, install + MySQL on an NTFS or newer file system. Do not forget to + use MAX_ROWS and AVG_ROW_LENGTH when you create tables. + See Section 13.1.17, "CREATE TABLE Syntax." * MySQL and Virus Checking Software - Using virus scanning software such as Norton/Symantec - Anti-Virus on directories containing MySQL data and temporary - tables can cause issues, both in terms of the performance of - MySQL and the virus-scanning software mis-identifying the - contents of the files as containing spam. This is because of - the fingerprinting mechanism used by the virus scanning - software, and the way in which MySQL rapidly updates different - files, which may be identified as a potential security risk. + Virus-scanning software such as Norton/Symantec + Anti-Virus on directories containing MySQL data and + temporary tables can cause issues, both in terms of the + performance of MySQL and the virus-scanning software + misidentifying the contents of the files as containing + spam. This is due to the fingerprinting mechanism used by + the virus-scanning software, and the way in which MySQL + rapidly updates different files, which may be identified + as a potential security risk. After installing MySQL Server, it is recommended that you - disable virus scanning on the main directory (datadir) being - used to store your MySQL table data. There is usually a system - built into the virus scanning software to permit certain - directories to be specifically ignored during virus scanning. - In addition, by default, MySQL creates temporary files in the - standard Windows temporary directory. To prevent the temporary - files also being scanned, you should configure a separate - temporary directory for MySQL temporary files and add this to - the virus scanning exclusion list. To do this, add a - configuration option for the tmpdir parameter to your my.ini - configuration file. For more information, see Section 2.3.7.2, - "Creating an Option File." - -2.3.1. MySQL Installation Layout on Microsoft Windows - - For MySQL 5.5 on Windows, the default installation directory is - C:\Program Files\MySQL\MySQL Server 5.5. Some Windows users prefer - to install in C:\mysql, the directory that formerly was used as - the default. However, the layout of the subdirectories remains the - same. + disable virus scanning on the main directory (datadir) + used to store your MySQL table data. There is usually a + system built into the virus-scanning software to enable + specific directories to be ignored. + In addition, by default, MySQL creates temporary files in + the standard Windows temporary directory. To prevent the + temporary files also being scanned, configure a separate + temporary directory for MySQL temporary files and add + this directory to the virus scanning exclusion list. To + do this, add a configuration option for the tmpdir + parameter to your my.ini configuration file. For more + information, see Section 2.3.7.2, "Creating an Option + File." + +2.3.1 MySQL Installation Layout on Microsoft Windows + + For MySQL 5.5 on Windows, the default installation directory + is C:\Program Files\MySQL\MySQL Server 5.5. Some Windows + users prefer to install in C:\mysql, the directory that + formerly was used as the default. However, the layout of the + subdirectories remains the same. - All of the files are located within this parent directory, using - the structure shown in the following table. + All of the files are located within this parent directory, + using the structure shown in the following table. - Table 2.4. Default MySQL Installation Layout for Microsoft Windows + Table 2.4 Default MySQL Installation Layout for Microsoft + Windows Directory Contents of Directory Notes bin Client programs and the mysqld server - %ALLUSERSPROFILE%\MySQL\MySQL Server 5.5\ Log files, databases - (Windows XP, Windows Server 2003) The Windows system variable - %ALLUSERSPROFILE% defaults to C:\Documents and Settings\All - Users\Application Data - %PROGRAMDATA%\MySQL\MySQL Server 5.5\ Log files, databases (Vista, - Windows 7, Windows Server 2008, and newer) The Windows system - variable %PROGRAMDATA% defaults to C:\ProgramData + %ALLUSERSPROFILE%\MySQL\MySQL Server 5.5\ Log files, + databases (Windows XP, Windows Server 2003) The Windows + system variable %ALLUSERSPROFILE% defaults to C:\Documents + and Settings\All Users\Application Data + %PROGRAMDATA%\MySQL\MySQL Server 5.5\ Log files, databases + (Vista, Windows 7, Windows Server 2008, and newer) The + Windows system variable %PROGRAMDATA% defaults to + C:\ProgramData examples Example programs and scripts include Include (header) files lib Libraries scripts Utility scripts share Miscellaneous support files, including error messages, - character set files, sample configuration files, SQL for database - installation + character set files, sample configuration files, SQL for + database installation - If you install MySQL using a Windows MSI package, this package - creates and sets up the data directory that the installed server - will use, but as of MySQL 5.5.5, it also creates a pristine - "template" data directory named data under the installation - directory. This directory can be useful when the machine will be - used to run multiple instances of MySQL: After an installation has - been performed using an MSI package, the template data directory - can be copied to set up additional MySQL instances. See Section - 5.3, "Running Multiple MySQL Instances on One Machine." - -2.3.2. Choosing An Installation Package - - For MySQL 5.5, there are installation package formats to choose - from when installing MySQL on Windows: - Note - - MySQL Installer and the "Complete Package" methods for installing - MySQL are similar, but different. The MySQL Installer is the newer - and more advanced option, and it includes all functionality found - within the "Complete Package." + If you install MySQL using a Windows MSI package, this + package creates and sets up the data directory that the + installed server will use, but as of MySQL 5.5.5, it also + creates a pristine "template" data directory named data under + the installation directory. This directory can be useful when + the machine will be used to run multiple instances of MySQL: + After an installation has been performed using an MSI + package, the template data directory can be copied to set up + additional MySQL instances. See Section 5.3, "Running + Multiple MySQL Instances on One Machine." + +2.3.2 Choosing An Installation Package + + For MySQL 5.5, there are installation package formats to + choose from when installing MySQL on Windows: + Note + + MySQL Installer and the "Complete Package" methods for + installing MySQL are similar, but different. The MySQL + Installer is the newer and more advanced option, and it + includes all functionality found within the "Complete + Package." * MySQL Installer: This package has a file name similar to - mysql-installer-community-5.5.36.0.msi or - mysql-installer-commercial-5.5.36.0.msi, and utilizes MSI's to - automatically install MySQL server and other products. It will - download and apply updates to itself, and for each of the - installed products. It also configures the additional - non-server products. - The installed products are configurable, and this includes: - documentation with samples and examples, connectors (such as - C, C++, J, NET, and ODBC), MySQL Workbench, MySQL Notifier for - Microsoft Windows, MySQL for Excel, and the MySQL Server with - its components. - MySQL Installer will run on all Windows platforms that are - supported by MySQL (see - http://www.mysql.com/support/supportedplatforms/database.html) - . Note: because MySQL is not a native component of Windows and - depends on .NET, it will not work on minimal installation - options like the "Server Core" version of Windows Server 2008. - For instructions on installing MySQL using MySQL Installer, - see Section 2.3.3, "Installing MySQL on Microsoft Windows - Using MySQL Installer." - - * The Complete Package: This package has a file name similar to - mysql-5.5.36-win32.msi and contains all files needed for a - complete Windows installation, including the Configuration - Wizard. This package includes optional components such as the - embedded server and benchmark suite. - - * The Noinstall Archive: This package has a file name similar to - mysql-5.5.36-win32.zip and contains all the files found in the - Complete install package, with the exception of the - Configuration Wizard. This package does not include an - automated installer, and must be manually installed and - configured. - - MySQL Installer is recommended for most users. Both MySQL - Installer and the alternative "Complete distribution" versions are - available as .msi files for use with installations on Windows. The - Noinstall distribution is packaged as a Zip archive. To use a Zip - archive, you must have a tool that can unpack .zip files. - - Your choice of install package affects the installation process - you must follow. If you choose to install using MySQL Installer, - see Section 2.3.3, "Installing MySQL on Microsoft Windows Using - MySQL Installer." If you choose to install a standard MSI package, - see Section 2.3.5, "Installing MySQL on Microsoft Windows Using an - MSI Package." If you choose to install a Noinstall archive, see - Section 2.3.7, "Installing MySQL on Microsoft Windows Using a - noinstall Zip Archive." - -2.3.3. Installing MySQL on Microsoft Windows Using MySQL Installer - - MySQL Installer is an application that simplifies the installation - and updating process for a wide range of MySQL products, including - MySQL Notifier for Microsoft Windows, MySQL Workbench, and MySQL - for Excel. From this central application, you can see which MySQL - products are already installed, configure them, and update or - remove them if necessary. The installer can also install plugins, - documentation, tutorials, and example databases. The MySQL - Installer is only available for Microsoft Windows, and includes - both a GUI and command-line interface. + mysql-installer-community-5.5.44.0.msi or + mysql-installer-commercial-5.5.44.0.msi, and utilizes + MSIs to automatically install MySQL server and other + products. It will download and apply updates to itself, + and for each of the installed products. It also + configures the additional non-server products. + The installed products are configurable, and this + includes: documentation with samples and examples, + connectors (such as C, C++, J, NET, and ODBC), MySQL + Workbench, MySQL Notifier, MySQL for Excel, and the MySQL + Server with its components. + MySQL Installer will run on all Windows platforms that + are supported by MySQL (see + http://www.mysql.com/support/supportedplatforms/database. + html). + Note + Because MySQL Installer is not a native component of + Microsoft Windows and depends on .NET, it will not work + on minimal installation options like the "Server Core" + version of Windows Server 2008. + For instructions on installing MySQL using MySQL + Installer, see Section 2.3.3, "Installing MySQL on + Microsoft Windows Using MySQL Installer." + + * The Complete Package: This package has a file name + similar to mysql-5.5.44-win32.msi or + mysql-5.5.44-winx64.zip, and contains all files needed + for a complete Windows installation, including the + Configuration Wizard. This package includes optional + components such as the embedded server and benchmark + suite. + + * The Noinstall Archive: This package has a file name + similar to mysql-5.5.44-win32.zip or + mysql-5.5.44-winx64.zip, and contains all the files found + in the Complete install package, with the exception of + the GUI. This package does not include an automated + installer, and must be manually installed and configured. + + MySQL Installer is recommended for most users. + + Your choice of install package affects the installation + process you must follow. If you choose to use MySQL + Installer, see Section 2.3.3, "Installing MySQL on Microsoft + Windows Using MySQL Installer." If you choose to install a + standard MSI package, see Section 2.3.5, "Installing MySQL on + Microsoft Windows Using an MSI Package." If you choose to + install a Noinstall archive, see Section 2.3.7, "Installing + MySQL on Microsoft Windows Using a noinstall Zip Archive." + +2.3.3 Installing MySQL on Microsoft Windows Using MySQL Installer + + MySQL Installer simplifies the installation and updating + process for your MySQL products on Microsoft Windows. From + this central application, you can view, remove, update, and + reconfigure the existing MySQL products on your system. MySQL + Installer can also install plugins, documentation, tutorials, + and example databases. The MySQL Installer is only available + for Microsoft Windows, and includes both GUI and command-line + interfaces. + + The supported products include: + + * MySQL server (http://dev.mysql.com/doc/) (one or multiple + versions) + + * MySQL Workbench + + * MySQL Connectors + (http://dev.mysql.com/doc/index-connectors.html) (.Net / + Python / ODBC / Java / C / C++) + + * MySQL Notifier + + * MySQL for Excel + (http://dev.mysql.com/doc/mysql-for-excel/en/index.html) + + * MySQL for Visual Studio + (http://dev.mysql.com/doc/connector-net/en/connector-net- + visual-studio.html) + + * MySQL Utilities and MySQL Fabric + (http://dev.mysql.com/doc/index-utils-fabric.html) + + * MySQL Samples and Examples + + * MySQL Documentation + + * MySQL Installer is also installed and remains on the + system as its own application Installer package types - * Full: Bundles all of the MySQL products (including MySQL - Server). The file is over 160MB, and have names of the form - mysql-installer-community-VERSION.N.msi where VERSION is the - MySQL Server version number such as 5.6 and N is the package - number, which begins at 0. - - * Web: Only contains the Installer and configuration files, and - it only downloads the MySQL products you choose to install. - The file is about 2MB, and have names of the form - mysql-installer-community-web-VERSION.N.msi where VERSION is - the MySQL Server version number such as 5.6 and N is the - package number, which begins at 0. + * Full: Bundles all of the MySQL products (including the + MySQL server). The file' size is over 200MB, and its name + has the form mysql-installer-community-VERSION.N.msi + where VERSION is the MySQL Server version number such as + 5.6 and N is the package number, which begins at 0. + + * Web: Only contains the Installer and configuration files, + and it only downloads the MySQL products you choose to + install. The size of this file is about 2MB; the name of + the file has the form + mysql-installer-community-web-VERSION.N.msi where VERSION + is the MySQL Server version number such as 5.6 and N is + the package number, which begins at 0. Installer editions * Community edition: Downloadable at - http://dev.mysql.com/downloads/installer/. It installs the - community edition of all MySQL products. + http://dev.mysql.com/downloads/installer/. It installs + the community edition of all MySQL products. - * Commercial edition: Downloadable at either My Oracle Support - (https://support.oracle.com/) (MOS) or + * Commercial edition: Downloadable at either My Oracle + Support (https://support.oracle.com/) (MOS) or https://edelivery.oracle.com/. It installs the commercial - version of all MySQL products, including Workbench SE. It also - integrates with your MOS account, so enter in your MOS - credentials to automatically receive updates for your - commercial MySQL products. + version of all MySQL products, including Workbench SE/EE. + It also integrates with your MOS account. + Note + Entering your MOS credentials is optional when installing + bundled MySQL products, but your credentials are required + when choosing non-bundled MySQL products that MySQL + Installer must download. - For release notes detailing the changes in each release of MySQL + For notes detailing the changes in each release of MySQL Installer, see MySQL Installer Release Notes (http://dev.mysql.com/doc/relnotes/mysql-installer/en/). - MySQL Installer is compatible with pre-existing installations, and - adds them to its list of installed components. And while the MySQL - Installer is bundled with a specific version of MySQL Server, a - single MySQL Installer instance can install and manage multiple - MySQL Server versions. For example, a single MySQL Installer - instance can install versions 5.1, 5.5, and 5.6. It can also - manage either commercial or community editions of the MySQL - Server. + MySQL Installer is compatible with pre-existing + installations, and adds them to its list of installed + components. While the standard MySQL Installer is bundled + with a specific version of MySQL Server, a single MySQL + Installer instance can install and manage multiple MySQL + Server versions. For example, a single MySQL Installer + instance can install (and update) versions 5.5, 5.6, and 5.7 + on the host. + Note + + A single host can not have both community and commercial + editions of MySQL Server installed. For example, if you want + both MySQL Server 5.5 and 5.6 installed on a single host, + then both must be the same edition. + + MySQL Installer handles the initial configuration and set up + of the applications. For example: + + 1. It creates initial MySQL Server connections in MySQL + Workbench. + + 2. It creates the configuration file (my.ini) that is used + to configure the MySQL Server. The values written to this + file are influenced by choices you make during the + installation process. + + 3. It can optionally import example databases. + + 4. It can optionally create MySQL Server user accounts with + configurable permissions based on general roles, such as + DB Administrator, DB Designer, and Backup Admin. It + optionally creates a Windows user named MysqlSys with + limited privileges, which would then run the MySQL + Server. + User accounts may also be added and configured in MySQL + Workbench. + + 5. If the "Advanced Configuration" option is checked, then + the Logging Options are also configured. This includes + defining file paths for the error log, general log, slow + query log (including the configuration of seconds it + requires to execute a query), and the binary log. + + MySQL Installer can optionally check for updated components + and download them for you. + +2.3.3.1 MySQL Installer GUI + + Installing MySQL Installer adds a link to the Start menu + under the MySQL group. Click Start, All Programs MySQL, MySQL + Installer to reload the MySQL Installer GUI. + Note + + Files that are generated by MySQL Installer grant full + permissions to the user that executes MySQL Installer, + including my.ini. This does not apply to files and + directories for specific products such as the MySQL Server + data directory in %ProgramData% that is owned by SYSTEM. + + The initial execution of MySQL Installer requires you to + accept the license agreement before installing MySQL + products. + + Figure 2.7 MySQL Installer - License Agreement + MySQL Installer - License Agreement + +Installing New Packages + + Choose the appropriate Setup Type for your system. The + selected type determines which MySQL products are installed + on your system, or select Custom to manually choose + individual products. + + * Developer: Install all products needed to develop + applications with MySQL. This is the default option. + + * Server only: Only install the MySQL server. + + * Client only: Only install the MySQL client products, + which does not include the MySQL server. + + * Full: Install all MySQL products. + + * Custom: Manually select the MySQL products to install. + Note + After the initial installation, you may use MySQL + Installer to manually select MySQL products to install or + remove. In other words, MySQL Installer becomes a MySQL + product management system. + + Figure 2.8 MySQL Installer - Choosing a Setup Type + MySQL Installer - Choosing a Setup Type + + After you select a setup type, the MySQL Installer will check + your system for the necessary external requirements for each + of the selected MySQL products. MySQL Installer will either + download and install the missing components onto your system, + or point you to the download location and set Status to + "Manual". + + The next window lists the MySQL products that are scheduled + to be installed: + + Figure 2.9 MySQL Installer - Installation Progress + MySQL Installer - Installation Progress + + As components are installed, their Status changes from a + progress percentage to "Complete". + + After all components are installed, the next step configures + some of the recently installed MySQL products. The + Configuration Overview window displays the progress and then + loads a configuration window, if required. Our example + configures MySQL Server 5.6.x. + +Configuring MySQL Server + + Configuring the MySQL server begins with defining several + Type and Networking options. + + Figure 2.10 MySQL Installer - Configuration Overview + MySQL Installer - Configuration Overview + + Server Configuration Type + + Choose the MySQL server configuration type that describes + your setup. This setting defines the amount of system + resources that will be assigned to your MySQL server + instance. + + * Developer: A machine that will host many other + applications, and typically this is your personal + workstation. This option configures MySQL to use the + least amount of memory. + + * Server: Several other applications will be running on + this machine, such as a web server. This option + configures MySQL to use a medium amount of memory. + + * Dedicated: A machine that is dedicated to running the + MySQL server. Because no other major applications are + running on the server, such as web servers, this option + configures MySQL to use all available memory. + + Connectivity + + Connectivity options control how you will connect to MySQL. + Options include: + + * TCP/IP: You may enable TCP/IP Networking here as + otherwise only localhost connections are allowed. Also + define the Port Number and whether to open the firewall + port for network access. + + * Named Pipe: Enable and define the pipe name, similar to + using the --enable-named-pipe option. + + * Shared Memory: Enable and then define the memory name, + similar to using the --shared-memory option. + + Advanced Configuration + + Checking the "Advanced Configuration" option provides + additional Logging Options to configure. This includes + defining file paths for the error log, general log, slow + query log (including the configuration of seconds it requires + to execute a query), and the binary log. + + Figure 2.11 MySQL Installer - MySQL Server Configuration: + Type and Networking + MySQL Installer- MySQL Server Configuration: Type and + Networking + +Accounts and Roles + + Next, define your MySQL account information. Assigning a root + password is required. + + Optionally, you can add additional MySQL user accounts with + predefined user roles. Each predefined role, such as "DB + Admin", are configured with their own set of privileges. For + example, the "DB Admin" role has more privileges than the "DB + Designer" role. Click the Role dropdown for a list of role + descriptions. Note - A single host can not have both community and commercial editions - of MySQL Server installed. For example, if you want both MySQL - Server 5.5 and 5.6 installed on a single host, then both must be - the same commercial or community edition. + If the MySQL Server is already installed, then you must also + enter the Current Root Password. + + Figure 2.12 MySQL Installer - MySQL Server Configuration: + User Accounts and Roles + MySQL Installer - MySQL Server Configuration: User Accounts + and Roles + + Figure 2.13 MySQL Installer - MySQL Server Configuration: + User Accounts and Roles: Adding a User + MySQL Installer - MySQL Server Configuration: User Accounts + and Roles: Adding a User + +Windows Service + + Next, configure the Windows Service details. This includes + the service name, whether the MySQL Server should be loaded + at startup, and how the Windows Service for MySQL Server is + executed. + + Figure 2.14 MySQL Installer - MySQL Server Configuration: + Windows Service + MySQL Installer - MySQL Server Configuration: Windows Service + Note + + When configuring Run Windows Services as ... using a Custom + User, the custom user must have privileges to log on to + Microsoft Windows as a service. And the Next button will be + disabled until this user is configured with these user + rights. + + On Microsoft Windows 7, this is configured by loading the + Start Menu, Control Panel, Administrative Tools, Local + Security Policy, Local Policies, User Rights Assignment, then + Log On As A Service. Choose Add User or Group here to add the + custom user, and then OK, OK to save. + +Advanced Options + + The next configuration step is available if the Advanced + Configuration option was checked. This section includes + options that are related to the MySQL log files: + + Figure 2.15 MySQL Installer - MySQL Server Configuration: + Logging Options + MySQL Installer - MySQL Server Configuration: Logging Options + + Click Next to continue on to the final page before all of the + requested changes are applied. This Apply Server + Configuration page details the configuration steps that will + be performed. - MySQL Installer handles the initial configuration and setup of the - applications. For example: + Figure 2.16 MySQL Installer - MySQL Server Configuration: + Apply Server Configuration + MySQL Installer - MySQL Server Configuration: Apply Server + Configuration - 1. It will create MySQL Server connections in MySQL Workbench. + Click Execute to execute the configuration steps. The icon + for each step toggles from white to green on success, or the + process stops on failure. Click the Log tab to view the log. - 2. It creates the configuration file (my.ini) that is used to - configure the MySQL Server. The values written to this file - are influenced by choices you make during the installation - process. + After the MySQL Installer configuration process is finished, + MySQL Installer reloads the opening page where you can + execute other installation and configuration related actions. - 3. It imports example databases. + MySQL Installer is added to the Microsoft Windows Start menu + under the MySQL group. Opening MySQL Installer loads its + dashboard where installed MySQL products are listed, and + other MySQL Installer actions are available: - 4. It creates MySQL Server user accounts with configurable - permissions based on general roles, such as DB Administrator, - DB Designer, and Backup Admin. It optionally creates a Windows - user named MysqlSys with limited privileges, which would then - run the MySQL Server. - This feature is only available during the initial installation - of the MySQL Server, and not during future updates. User - accounts may also be added with MySQL Workbench. + Figure 2.17 MySQL Installer - Main Dashboard + MySQL Installer - Main Dashboard - 5. If the "Advanced Configuration" option is checked, then the - Logging Options are also configured. This includes defining - file paths for the error log, general log, slow query log - (including the configuration of seconds it requires to execute - a query), and the binary log. +Adding MySQL Products - MySQL Installer can optionally check for updated components and - download them for you automatically. + Click Add to add new products. This loads the Select Products + and Features page: -2.3.3.1. MySQL Installer GUI + Figure 2.18 MySQL Installer - Select Products and Features + MySQL Installer - Select Products and Features - After installation of the GUI version, the installer will have add - its own Start Menu item under MySQL. + From here, choose the MySQL products you want to install from + the left Available Products pane, and then click the green + right arrow to queue products for installation. + + Optionally, click Edit to open the product and features + search filter: + + Figure 2.19 MySQL Installer - Select Products and Features + Filter + MySQL Installer - Select Products and Features Filter + + For example, you might choose to include Pre-Release products + in your selections, such as a Beta product that has not yet + reached GA status. Note - Files that are generated by MySQL Installer grant full permissions - to the user that executes MySQL Installer, including my.ini. This - does not apply to files and directories for specific products such - as the MySQL Server data directory in ProgramData, that is owned - by SYSTEM. + The ability to install Pre-Release versions of MySQL products + was added in MySQL Installer 1.4.0. - After the installer itself has been installed and started, the - following screen is displayed: + Select all of the MySQL products you want to install, then + click Next to continue, and then Execute to execute the + installation process to install all of the selected products. - Figure 2.7. MySQL Installer - Welcome Screen - MySQL Installer - Welcome Screen +2.3.3.1.1 MySQL Product Catalog - There are three main options: + MySQL Installer stores a MySQL product catalog. The catalog + can be updated either manually or automatically, and the + catalog change history is also available. + Note - 1. Install MySQL Products - The Installation Wizard. + The MySQL product catalog was added in MySQL Installer 1.4.0. - 2. About MySQL - Learn about MySQL products and features. + Manual updates - 3. Resources - Information to help install and configure MySQL. + You can update the MySQL product catalog at any time by + clicking Catalog on the Installer dashboard. - To Install MySQL Products after executing MySQL Installer for the - first time, you must accept the license agreement before - proceeding with the installation process. + Figure 2.20 MySQL Installer - Open the MySQL Product Catalog + MySQL Installer - Open the MySQL Product Catalog - Figure 2.8. MySQL Installer - License Agreement - MySQL Installer - License Agreement + From there, click Execute to update the product catalog. - If you are connected to the Internet, then the Installer will - search for the latest MySQL components and add them to the - installation bundle. Click Connect to the Internet to complete - this step, or otherwise check the Skip checkbox and then Continue. - - Figure 2.9. MySQL Installer - Find latest products - MySQL Installer - Find latest products - - If you chose "Connect to the Internet," the next page will show - the progress of MySQL Installer's search for available updates. - When the search is complete (or if you opted to skip the search), - you will be taken to the Choose Setup Type page: + Automatic updates - Figure 2.10. MySQL Installer - Choosing a Setup Type - MySQL Installer - Choosing a Setup Type + You can configure MySQL Installer to automatically update the + MySQL product catalog once per day. To enable this feature + and set the update time, click the wrench icon on the + Installer dashboard. - Determine the option most compatible with your preferences by - reading the Setup Type Description descriptions. + The next window configures the Automatic Catalog Update. + Enable or disable this feature, and also set the hour. - The Installation and Data paths are also defined here, and a - caution flag will notify you if the data path you define already - exists. + Figure 2.21 MySQL Installer - Configure the Catalog Scheduler + MySQL Installer - Configure the Catalog Scheduler - After you select a setup type, the MySQL Installer will check your - system for the necessary external requirements and download then - install missing components onto your system. + This option uses the Windows Task Scheduler to schedule a + task named "ManifestUpdate". - Figure 2.11. MySQL Installer - Check Requirements - MySQL Installer - Check Requirements + Change History - The next window lists the MySQL products that are scheduled to be - installed: + MySQL Installer tracks the change history for all of the + MySQL products. Click Catalog from the dashboard, optionally + update the catalog (or, toggle the Do not update at this time + checkbox), click Next/Execute, and then view the change + history. - Figure 2.12. MySQL Installer - Installation Progress - MySQL Installer - Installation Progress + Figure 2.22 MySQL Installer - Catalog Change History + MySQL Installer - Catalog Change History - As components are installed, you'll see their status change from - "to be installed" to "install success." +2.3.3.1.2 Remove MySQL Products - Figure 2.13. MySQL Installer - Installation Progress status - MySQL Installer - Installation Progress status + MySQL Installer can also remove MySQL products from your + system. To remove a MySQL product, click Remove from the + Installer dashboard. This opens a window with a list of + installed MySQL products. Select the MySQL products you want + to remove (uninstall), and then click Execute to begin the + removal process. + Note - After all components are installed, the next step involves - configuring the products. The Configuration Overview window - displays the progress and then loads a configuration window if it - is required. + To select all MySQL products, click the [ ] checkbox to the + left of the Product label. - Figure 2.14. MySQL Installer - Configuration Overview - MySQL Installer - Configuration Overview + Figure 2.23 MySQL Installer - Removing Products: Select + MySQL Installer - Removing Products: Select + + Figure 2.24 MySQL Installer - Removing Products: Executed + MySQL Installer - Removing Products: Executed + +2.3.3.1.3 Alter MySQL Products + + MySQL Installer offers several options to alter your MySQL + product installations. + +Upgrade + + MySQL products with an available upgrade are highlighted on + the main dashboard. Products with available upgrades will + have an upgrade icon next to their version number. + + Figure 2.25 MySQL Installer - Upgrade a MySQL Product + MySQL Installer - Upgrade a MySQL Product + Note + + Available upgrades are determined by having a current + catalog. For information about keeping your MySQL product + catalog current, see Section 2.3.3.1.1, "MySQL Product + Catalog." + + Click Upgrade to view a list upgradable products. Our example + indicates that MySQL server 5.6.19 can be upgraded to version + 5.6.20. + + Figure 2.26 MySQL Installer - Select Products To Upgrade + MySQL Installer - Select Products To Upgrade + + Select (check) the products to upgrade, and optionally click + the changes link to view the product's release notes in your + browser. Click Next to begin the upgrade process. + + Figure 2.27 MySQL Installer - Apply Updates + MySQL Installer - Apply Updates + + A MySQL server upgrade will also check and upgrade the + server's database. Although optional, this step is + recommended. + + Figure 2.28 MySQL Installer - Check and Upgrade Database + MySQL Installer - Check and Upgrade Database + + Upon completion, your upgraded products will be upgraded and + available to use. A MySQL server upgrade also restarts the + MySQL server. - The ideal MySQL Server configuration depends on your intended use, - as explained in the next window. Choose the description that most - closely applies to your machine. - - You may enable TCP/IP Networking here as otherwise only localhost - connections are allowed. - - Checking the "Advanced Configuration" option provides additional - Logging Options to configure. This includes defining file paths - for the error log, general log, slow query log (including the - configuration of seconds it requires to execute a query), and the - binary log. - - Figure 2.15. MySQL Installer - MySQL Server Configuration: Define - platform, networking, and logging options - MySQL Installer- MySQL Server Configuration: Define platform, - networking, and logging options - - Next, choose your account information. Defining a root password is - required, whereas it's optional to create additional users. There - are several different predefined user roles that each have - different permission levels. For example, a "DB Admin" will have - more privileges than a "DB Designer.". - - Figure 2.16. MySQL Installer - MySQL Server Configuration: User - accounts - MySQL Installer - MySQL Server Configuration: User accounts - Note - - If the MySQL Server is already installed, then the Current Root - Password will also be needed. - - Next, configure the Windows Service Details. This includes the - service name, how the MySQL Server should be loaded at startup, - and how the Windows Service for MySQL Server will be run. - - Figure 2.17. MySQL Installer - MySQL Server Configuration: Windows - service details - MySQL Installer - MySQL Server Configuration: Windows service - details - Note - - When configuring Run Windows Services as ... using a Custom User, - the custom user must have privileges to log on to Windows as a - service. And the Next button will be disabled until this user is - given these user rights. - - On Microsoft Windows 7, this is configured by loading the Start - Menu, Control Panel, Administrative Tools, Local Security Policy, - Local Policies, User Rights Assignment, then Log On As A Service. - Choose Add User or Group here to add the custom user, and then OK, - OK to save. - - The final configuration step is available if the Advanced - Configuration option was checked, and it includes configuration - options related to log file names: - - Figure 2.18. MySQL Installer - MySQL Server Configuration: Logging - options - MySQL Installer - MySQL Server Configuration: Logging options - - After the MySQL Installer configuration process is completed, you - may save the installation log, and then load MySQL Workbench if - the Start MySQL Workbench after Setup option is checked: - - Figure 2.19. MySQL Installer - Installation Complete - MySQL Installer - Installation Complete - - You can now open MySQL Installer from the Microsoft Windows Start - menu under the MySQL group, which will load the MySQL Installer - Maintenance Screen. This is used to add, update, and remove - features. - - Figure 2.20. MySQL Installer - Maintenance Screen - MySQL Installer - Maintenance Screen - Note - - An Update Screen screen is shown if MySQL Installer is used on a - machine with older products installed, as opposed to the - Maintenance Screen shown above. However, the functionality remains - the same. - - Add/Modify Products and Features will list all installed and - available MySQL products. - - Figure 2.21. MySQL Installer - Add/Modify Products and Features - MySQL Installer - Add/Modify Products and Features - - The installation is now complete. MySQL Server should be running, - and most MySQL products installed and available for use. - - See also the MySQL Workbench documentation - (http://dev.mysql.com/doc/workbench/en/). - -2.3.3.2. MySQL Installer Console - - MySQLInstallerConsole provides functionality similar to the GUI - version of MySQL Installer, but from the command-line. It is - installed when MySQL Installer is initially executed, and then - available within the MySQL Installer directory. Typically that is - in C:\Program Files (x86)\MySQL\MySQL Installer\, and the console - must be executed with administrative privileges. - - To use, invoke the Command Prompt with administrative privileges - by choosing Start, Accessories, then right-click on Command Prompt - and choose Run as administrator. And from the command-line, - optionally change the directory to where MySQLInstallerConsole is - located: +Reconfigure + + Some MySQL products, such as the MySQL server, include a + Reconfigure option. It opens the same configuration options + that were set when the MySQL product was installed, and is + pre-populated with the current values. + + To execute, click the Reconfigure link under the Quick Action + column on the main dashboard for the MySQL product that you + want to reconfigure. + + Figure 2.29 MySQL Installer - Reconfigure a MySQL Product + MySQL Installer - Reconfigure a MySQL Product + + In the case of the MySQL server, this opens the familiar + configuration wizard. + + Figure 2.30 MySQL Installer - Reconfiguration Wizard + MySQL Installer - Reconfiguration Wizard + +Modify + + Many MySQL products contain feature components that can be + added or removed. For example, Debug binaries and Client + Programs are subcomponents of the MySQL server. + + The modify the features of a product, click Modify on the + main dashboard. + + Figure 2.31 MySQL Installer - Modify Product Features + MySQL Installer - Modify Product Features + + Click Execute to execute the modification request. + +2.3.3.2 MySQL Installer Console + + MySQLInstallerConsole provides functionality similar to the + GUI version of MySQL Installer, but from the command-line. It + is installed when MySQL Installer is initially executed, and + then available within the MySQL Installer directory. + Typically that is in C:\Program Files (x86)\MySQL\MySQL + Installer\, and the console must be executed with + administrative privileges. + + To use, invoke the Command Prompt with administrative + privileges by choosing Start, Accessories, then right-click + on Command Prompt and choose Run as administrator. And from + the command-line, optionally change the directory to where + MySQLInstallerConsole is located: C:\> cd "C:\Program Files (x86)\MySQL\MySQL Installer" +C:\> MySQLInstallerConsole.exe help - MySQLInstallerConsole supports the following options, which are - specified on the command line: +C:\Program Files (x86)\MySQL\MySQL Installer for Windows>MySQLInstalle +rConsole.exe help - * --help, -h, or -? - Displays a help message with usage examples, and then exits. -C:\> MySQLInstallerConsole --help - - * --updates (or -u) - Checks for new products before any further action is taken. - Disabled by default. - - * --nowait - Skips the final pause when the program finishes. Otherwise, a - "Press Enter to continue." dialogue is generated. It is used - in conjunction with other options. - - * --catalog=catalog_name (or -c) - Sets the default catalog. Use --list to view a list of - available catalogs. - - * --type=installation_type (or -t) - Sets the installation type. - The possible values for installation_type are: developer, - server, client, full, and custom. - - * --action=action_name - The action being performed. - The possible values are: install, remove, upgrade, list, and - status. - - + install: Installs a product or products, as defined by - --products - - + upgrade: Upgrades a product or products, as defined by - --products. - - + remove: Removes a product or products, as defined by - --products. - - + list: Lists the product manifest, both installed and - available products. - - + status: Shows the status after another action is - performed. - - * --product=product_name[:feature1],[feature2], [...] (or -p) - Set the feature list of a product. Use --list to view - available products, or pass in --product=* (an asterisk) to - install all available products. - - * --config=product_name:passwd=root_password[;parameter1=value], - [;parameter2=value], ... - The configuration parameters for the most recently listed - products. +The following commands are available: + +Configure - Configures one or more of your installed programs. +Help - Provides list of available commands. +Install - Install and configure one or more available MySQL programs +. +List - Provides an interactive way to list all products available +. +Modify - Modifies the features of installed products. +Remove - Removes one or more products from your system. +Status - Shows the status of all installed products. +Update - Update the current product catalog. +Upgrade - Upgrades one or more of your installed programs. + + MySQLInstallerConsole supports the following options, which + are specified on the command line: + + * configure [product1]:[setting]=[value]; + [product2]:[setting]=[value]; [...] + Configure one or more MySQL products on your system. + Switches include: + + + -showsettings : Displays the available options for + the selected product, by passing in the product name + after -showsettings. + + + -silent : Disable confirmation prompts. +C:\> MySQLInstallerConsole configure -showsettings server +C:\> MySQLInstallerConsole configure server:port=3307 + + + * help [command] + Displays a help message with usage examples, and then + exits. Pass in an additional command to receive help + specific to that command. +C:\> MySQLInstallerConsole help +C:\> MySQLInstallerConsole help install + + + * install [product]:[features]:[config block]:[config + block]:[config block]; [...] + Install one or more MySQL products on your system. + Switches and syntax options include: + + + -type=[SetupType] : Installs a predefined set of + software. The "SetupType" can be one of the + following: + Note + Non-custom setup types can only be chosen if no + other MySQL products are installed. + o Developer: Installs a complete development + environment. + o Server: Installs a single MySQL server + o Client: Installs client programs and libraries + o Full: Installs everything + o Custom: Installs user selected products. This + is the default option. + + + -showsettings : Displays the available options for + the selected product, by passing in the product name + after -showsettings. + + + -silent : Disable confirmation prompts. + + + [config block]: One or more configuration blocks can + be specified. Each configuration block is a + semicolon separated list of key value pairs. A block + can include either a "config" or "user" type key, + where "config" is the default type if one is not + defined. + Only one "config" type block can be defined per + product. A "user" block should be defined for each + user that should be created during the product's + installation. + Note + Adding users is not supported when a product is + being reconfigured. + + + [feature]: The feature block is a semicolon + separated list of features, or '*' to select all + features. +C:\> MySQLInstallerConsole install server;5.6.22:*:port=3307;serverid= +2:type=user;username=foo;password=bar;role=DBManager +C:\> MySQLInstallerConsole install server;5.6.22;x64 -silent + + + * list + Lists an interactive console where all of the available + MySQL products can be searched. Execute + MySQLInstallerConsole list to launch the console, and + enter in a substring to search. +C:\> MySQLInstallerConsole list + + + * modify [product1:-removelist|+addlist] + [product2:-removelist|+addlist] [...] + Modifies or displays features of a previously installed + MySQL product. + + + -silent : Disable confirmation prompts. +C:\> MySQLInstallerConsole modify server +C:\> MySQLInstallerConsole modify server:+documentation +C:\> MySQLInstallerConsole modify server:-debug + + + * remove [product1] [product2] [...] + Removes one ore more products from your system. + + + * : Pass in * to remove all of the MySQL products. + + + -continue : Continue the operation even if an error + occurs. + + + -silent : Disable confirmation prompts. +C:\> MySQLInstallerConsole remove * +C:\> MySQLInstallerConsole remove server + + + * status + Provides a quick overview of the MySQL products that are + installed on the system. Information includes product + name and version, architecture, date installed, and + install location. +C:\> MySQLInstallerConsole status + + + * upgrade [product1:version] [product2:version], [...] + Upgrades one or more products on your system. Syntax + options include: + + + * : Pass in * to upgrade all products to the latest + version, or pass in specific products. + + + ! : Pass in ! as a version number to upgrade the + MySQL product to its latest version. + + + -silent : Disable confirmation prompts. +C:\> MySQLInstallerConsole upgrade * +C:\> MySQLInstallerConsole upgrade workbench:6.2.2 +C:\> MySQLInstallerConsole upgrade workbench:! +C:\> MySQLInstallerConsole upgrade workbench:6.2.2 excel:1.3.2 + + + * update + Downloads the latest MySQL product catalog to your + system. On success, the download catalog will be applied + the next time either MySQLInstaller or + MySQLInstallerConsole is executed. +C:\> MySQLInstallerConsole update + + Note + The Automatic Catalog Update GUI option executes this + command from the Windows Task Scheduler. + +2.3.4 MySQL Notifier - * --user=product_name:name=username,host:hostname,role=rolename, - password=password or - --user=product_name:name=username,host:hostname,role=rolename, - tokens=tokens - Creates a new user. - Requires: name, host, role, and the password or tokens. Tokens - are separated by pipe ("|") characters. - -2.3.4. MySQL Notifier for Microsoft Windows - - The MySQL Notifier for Microsoft Windows is a tool that enables - you to monitor and adjust the status of your local and remote - MySQL Server instances through an indicator that resides in the - system tray. The MySQL Notifier for Microsoft Windows also gives - quick access to several MySQL GUI tools (such as MySQL Workbench) - through its context menu. - - The MySQL Notifier for Microsoft Windows is installed by MySQL - Installer, and (by default) will start-up when Microsoft Windows - is started. + The MySQL Notifier is a tool that enables you to monitor and + adjust the status of your local and remote MySQL Server + instances through an indicator that resides in the system + tray. The MySQL Notifier also gives quick access to several + MySQL GUI tools (such as MySQL Workbench) through its context + menu. + + The MySQL Notifier is installed by MySQL Installer, and (by + default) will start-up when Microsoft Windows is started. Note To install, download and execute the MySQL Installer - (http://dev.mysql.com/downloads/installer/), be sure the MySQL - Notifier for Microsoft Windows product is selected, then proceed - with the installation. See the MySQL Installer manual for - additional details. - - For release notes detailing the changes in each release of MySQL - Notifier for Microsoft Windows, see the MySQL Notifier Release - Notes (http://dev.mysql.com/doc/relnotes/mysql-notifier/en/). + (http://dev.mysql.com/downloads/installer/), be sure the + MySQL Notifier product is selected, then proceed with the + installation. See the MySQL Installer manual for additional + details. + + For notes detailing the changes in each release of MySQL + Notifier, see the MySQL Notifier Release Notes + (http://dev.mysql.com/doc/relnotes/mysql-notifier/en/). Visit the MySQL Notifier forum (http://forums.mysql.com/list.php?173) for additional MySQL - Notifier for Microsoft Windows help and support. + Notifier help and support. Features include: * Start, Stop, and Restart instances of the MySQL Server. - * Automatically detects (and adds) new MySQL Server services. - These are listed under Manage Monitored Items, and may also be - configured. - - * The Tray icon changes, depending on the status. It's green if - all monitored MySQL Server instances are running, or red if at - least one service is stopped. The Update MySQL Notifier tray - icon based on service status option, which dictates this - behavior, is enabled by default for each service. + * Automatically detects (and adds) new MySQL Server + services. These are listed under Manage Monitored Items, + and may also be configured. + + * The Tray icon changes, depending on the status. It's + green if all monitored MySQL Server instances are + running, or red if at least one service is stopped. The + Update MySQL Notifier tray icon based on service status + option, which dictates this behavior, is enabled by + default for each service. * Links to other applications like MySQL Workbench, MySQL Installer, and the MySQL Utilities. For example, choosing @@ -794,463 +1204,481 @@ Administration window for that particular instance. * If MySQL Workbench is also installed, then the Configure - Instance and SQL Editor options are available for local (but - not remote) MySQL instances. + Instance and SQL Editor options are available for local + (but not remote) MySQL instances. * Monitoring of both local and remote MySQL instances. Note - Remote monitoring is available since MySQL Notifier for Microsoft - Windows 1.1.0. + Remote monitoring is available since MySQL Notifier 1.1.0. - The MySQL Notifier for Microsoft Windows resides in the system - tray and provides visual status information for your MySQL Server - instances. A green icon is displayed at the top left corner of the - tray icon if the current MySQL Server is running, or a red icon if + The MySQL Notifier resides in the system tray and provides + visual status information for your MySQL Server instances. A + green icon is displayed at the top left corner of the tray + icon if the current MySQL Server is running, or a red icon if the service is stopped. - The MySQL Notifier for Microsoft Windows automatically adds - discovered MySQL Services on the local machine, and each service - is saved and configurable. By default, the Automatically add new - services whose name contains option is enabled and set to mysql. + The MySQL Notifier automatically adds discovered MySQL + Services on the local machine, and each service is saved and + configurable. By default, the Automatically add new services + whose name contains option is enabled and set to mysql. Related Notifications Options include being notified when new - services are either discovered or experience status changes, and - are also enabled by default. And uninstalling a service will also - remove the service from the MySQL Notifier for Microsoft Windows. + services are either discovered or experience status changes, + and are also enabled by default. And uninstalling a service + will also remove the service from the MySQL Notifier. Note The Automatically add new services whose name contains option - default changed from ".*mysqld.*" to "mysql" in Notifier 1.1.0. - - Clicking the system tray icon will reveal several options, as seen - in the screenshots below: + default changed from ".*mysqld.*" to "mysql" in Notifier + 1.1.0. - The Service Instance menu is the main MySQL Notifier for Microsoft - Windows window, and enables you to Stop, Start, and Restart the - MySQL Server. + Clicking the system tray icon will reveal several options, as + seen in the screenshots below: - Figure 2.22. MySQL Notifier for Microsoft Windows Service Instance - menu - MySQL Notifier for Microsoft Windows Service Instance menu + The Service Instance menu is the main MySQL Notifier window, + and enables you to Stop, Start, and Restart the MySQL Server. - The Actions menu includes several links to external applications - (if they are installed), and a a Refresh Status option to manually - refresh the status of all monitored services (in both local and - remote computers) and MySQL instances. + Figure 2.32 MySQL Notifier Service Instance menu + MySQL Notifier Service Instance menu + + The Actions menu includes several links to external + applications (if they are installed), and a Refresh Status + option to manually refresh the status of all monitored + services (in both local and remote computers) and MySQL + instances. Note - The main menu will not show the Actions menu when there are no - services being monitored by MySQL Notifier for Microsoft Windows. + The main menu will not show the Actions menu when there are + no services being monitored by MySQL Notifier. Note - The Refresh Status feature is available since MySQL Notifier for - Microsoft Windows 1.1.0. - - Figure 2.23. MySQL Notifier for Microsoft Windows Actions menu - MySQL Notifier for Microsoft Windows Actions menu - - The Actions, Options menu configures MySQL Notifier for Microsoft - Windows and includes options to: - - * Use colorful status icons: Enables a colorful style of icons - for the tray of the MySQL Notifier for Microsoft Windows. - - * Run at Windows Startup: Allows the application to be loaded - when Microsoft Windows starts. + The Refresh Status feature is available since MySQL Notifier + 1.1.0. - * Automatically Check For Updates Every # Weeks: Checks for a - new version of MySQL Notifier for Microsoft Windows, and runs - this check every # weeks. - - * Automatically add new services whose name contains: The text - used to filter services and add them automatically to the - monitored list of the local computer running MySQL Notifier, - and on remote computers already monitoring Windows services. - monitored services, and also filters the list of the Microsoft - Windows services for the Add New Service dialog. - Prior to version 1.1.0, this option was named "Automatically - add new services that match this pattern." - - * Notify me when a service is automatically added: Will display - a balloon notification from the taskbar when a newly - discovered service is added to the monitored services list. + Figure 2.33 MySQL Notifier Actions menu + MySQL Notifier Actions menu + + The Actions, Options menu configures MySQL Notifier and + includes options to: + + * Use colorful status icons: Enables a colorful style of + icons for the tray of the MySQL Notifier. + + * Run at Windows Startup: Allows the application to be + loaded when Microsoft Windows starts. + + * Automatically Check For Updates Every # Weeks: Checks for + a new version of MySQL Notifier, and runs this check + every # weeks. + + * Automatically add new services whose name contains: The + text used to filter services and add them automatically + to the monitored list of the local computer running MySQL + Notifier, and on remote computers already monitoring + Windows services. monitored services, and also filters + the list of the Microsoft Windows services for the Add + New Service dialog. + Prior to version 1.1.0, this option was named + "Automatically add new services that match this pattern." + + * Notify me when a service is automatically added: Will + display a balloon notification from the taskbar when a + newly discovered service is added to the monitored + services list. * Notify me when a service changes status: Will display a - balloon notification from the taskbar when a monitored service - changes its status. + balloon notification from the taskbar when a monitored + service changes its status. + + Figure 2.34 MySQL Notifier Options menu + MySQL Notifier Options menu - Figure 2.24. MySQL Notifier for Microsoft Windows Options menu - MySQL Notifier for Microsoft Windows Options menu + The Actions, Manage Monitored Items menu enables you to + configure the monitored services and MySQL instances. First, + with the Services tab open: - The Actions, Manage Monitored Items menu enables you to configure - the monitored services and MySQL instances. First, with the - Services tab open: - - Figure 2.25. MySQL Notifier for Microsoft Windows Manage Services - menu - MySQL Notifier for Microsoft Windows Manage Services menu + Figure 2.35 MySQL Notifier Manage Services menu + MySQL Notifier Manage Services menu The Instances tab is similar: - Figure 2.26. MySQL Notifier for Microsoft Windows Manage Instances - menu - MySQL Notifier for Microsoft Windows Manage Instances menu - - Adding a service or instance (after clicking Add in the Manage - Monitored Items window) enables you to select a running Microsoft - Windows service or instance connection, and configure MySQL - Notifier for Microsoft Windows to monitor it. Add a new service or + Figure 2.36 MySQL Notifier Manage Instances menu + MySQL Notifier Manage Instances menu + + Adding a service or instance (after clicking Add in the + Manage Monitored Items window) enables you to select a + running Microsoft Windows service or instance connection, and + configure MySQL Notifier to monitor it. Add a new service or instance by clicking service name from the list, then OK to accept. Multiple services and instances may be selected. - Figure 2.27. MySQL Notifier for Microsoft Windows Adding new - services - MySQL Notifier for Microsoft Windows Adding new services + Figure 2.37 MySQL Notifier Adding new services + MySQL Notifier Adding new services And instances: - Figure 2.28. MySQL Notifier for Microsoft Windows Adding new - instances - MySQL Notifier for Microsoft Windows Adding new instances + Figure 2.38 MySQL Notifier Adding new instances + MySQL Notifier Adding new instances Note - The Instances tab available since MySQL Notifier for Microsoft - Windows 1.1.0. + The Instances tab available since MySQL Notifier 1.1.0. -2.3.4.1. Remote monitoring set up and installation instructions +2.3.4.1 Remote monitoring set up and installation instructions - The MySQL Notifier for Microsoft Windows uses Windows Management - Instrumentation (WMI) to manage and monitor services in remote - computers running Windows XP or later. This guide explains how it + The MySQL Notifier uses Windows Management Instrumentation + (WMI) to manage and monitor services in remote computers + running Windows XP or later. This guide explains how it works, and how to set up your system to monitor remote MySQL instances. Note - Remote monitoring is available since MySQL Notifier for Microsoft - Windows 1.1.0. + Remote monitoring is available since MySQL Notifier 1.1.0. - In order to configure WMI, it is important to understand that the - underlying Distributed Component Object Model (DCOM) architecture - is doing the WMI work. Specifically, MySQL Notifier for Microsoft - Windows is using asynchronous notification queries on remote + In order to configure WMI, it is important to understand that + the underlying Distributed Component Object Model (DCOM) + architecture is doing the WMI work. Specifically, MySQL + Notifier is using asynchronous notification queries on remote Microsoft Windows hosts as .NET events. These events send an - asynchronous callback to the computer running the MySQL Notifier - for Microsoft Windows so it knows when a service status has - changed on the remote computer. Asynchronous notifications offer - the best performance compared to semi-synchronous notifications or + asynchronous callback to the computer running the MySQL + Notifier so it knows when a service status has changed on the + remote computer. Asynchronous notifications offer the best + performance compared to semisynchronous notifications or synchronous notifications that use timers. - Asynchronous notifications requires the remote computer to send a - callback to the client computer (thus opening a reverse - connection), so the Windows Firewall and DCOM settings must be - properly configured for the communication to function properly. - - Figure 2.29. MySQL Notifier for Microsoft Windows Distributed - Component Object Model (DCOM) - MySQL Notifier for Microsoft Windows Distributed Component Object - Model (DCOM) - - Most of the common errors thrown by asynchronous WMI notifications - are related to Windows Firewall blocking the communication, or to - DCOM / WMI settings not being set up properly. For a list of - common errors with solutions, see Section 2.3.4.1, "." - - The following steps are required to make WMI function. These steps - are divided between two machines. A single host computer that runs - MySQL Notifier for Microsoft Windows (Computer A), and multiple + Asynchronous notifications requires the remote computer to + send a callback to the client computer (thus opening a + reverse connection), so the Windows Firewall and DCOM + settings must be properly configured for the communication to + function properly. + + Figure 2.39 MySQL Notifier Distributed Component Object Model + (DCOM) + MySQL Notifier Distributed Component Object Model (DCOM) + + Most of the common errors thrown by asynchronous WMI + notifications are related to Windows Firewall blocking the + communication, or to DCOM / WMI settings not being set up + properly. For a list of common errors with solutions, see + Section 2.3.4.1, "." + + The following steps are required to make WMI function. These + steps are divided between two machines. A single host + computer that runs MySQL Notifier (Computer A), and multiple remote machines that are being monitored (Computer B). -Computer running MySQL Notifier for Microsoft Windows (Computer A) +Computer running MySQL Notifier (Computer A) - 1. Allow for remote administration by either editing the Group - Policy Editor, or using NETSH: + 1. Allow for remote administration by either editing the + Group Policy Editor, or using NETSH: Using the Group Policy Editor: - a. Click Start, click Run, type GPEDIT.MSC, and then click - OK. - b. Under the Local Computer Policy heading, double-click - Computer Configuration. + a. Click Start, click Run, type GPEDIT.MSC, and then + click OK. + b. Under the Local Computer Policy heading, + double-click Computer Configuration. c. Double-click Administrative Templates, then Network, Network Connections, and then Windows Firewall. d. If the computer is in the domain, then double-click - Domain Profile; otherwise, double-click Standard Profile. + Domain Profile; otherwise, double-click Standard + Profile. e. Click Windows Firewall: Allow inbound remote administration exception. - f. On the Action menu either select Edit, or double-click - the selection from the previous step. + f. On the Action menu either select Edit, or + double-click the selection from the previous step. g. Check the Enabled radio button, and then click OK. Using the NETSH command: - a. Open a command prompt window with Administrative rights - (you can right-click the Command Prompt icon and click - Run as Administrator). + a. Open a command prompt window with Administrative + rights (you can right-click the Command Prompt icon + and click Run as Administrator). b. Execute the following command: NETSH firewall set service RemoteAdmin enable + 2. Open the DCOM port TCP 135: - a. Open a command prompt window with Administrative rights - (you can right-click the Command Prompt icon and click - Run as Administrator) . + a. Open a command prompt window with Administrative + rights (you can right-click the Command Prompt icon + and click Run as Administrator) . b. Execute the following command: NETSH firewall add portopening protocol=tcp port=135 name=DCOM_TCP135 - 3. Add the client application which contains the sink for the - callback (MySqlNotifier.exe) to the Windows Firewall - Exceptions List (use either the Windows Firewall configuration - or NETSH): + + 3. Add the client application which contains the sink for + the callback (MySqlNotifier.exe) to the Windows Firewall + Exceptions List (use either the Windows Firewall + configuration or NETSH): Using the Windows Firewall configuration: a. In the Control Panel, double-click Windows Firewall. - b. In the Windows Firewall window's left panel, click Allow - a program or feature through Windows Firewall. - c. In the Allowed Programs window, click Change Settings. + b. In the Windows Firewall window's left panel, click + Allow a program or feature through Windows Firewall. + c. In the Allowed Programs window, click Change + Settings. d. If MySqlNotifier.exe is in the Allowed programs and - features list, make sure it is checked for the type of - networks the computer connects to (Private, Public or - both). + features list, make sure it is checked for the type + of networks the computer connects to (Private, + Public or both). e. If MySqlNotifier.exe is not in the list, click Allow another program.... - f. In the Add a Program window, select the MySqlNotifier.exe - if it exists in the Programs list, otherwise click - Browse... and go to the directory where MySqlNotifier.exe - was installed to select it, then click Add. - g. Make sure MySqlNotifier.exe is checked for the type of - networks the computer connects to (Private, Public or - both). + f. In the Add a Program window, select the + MySqlNotifier.exe if it exists in the Programs list, + otherwise click Browse... and go to the directory + where MySqlNotifier.exe was installed to select it, + then click Add. + g. Make sure MySqlNotifier.exe is checked for the type + of networks the computer connects to (Private, + Public or both). Using the NETSH command: - a. Open a command prompt window with Administrative rights - (you can right-click the Command Prompt icon and click - Run as Administrator). + a. Open a command prompt window with Administrative + rights (you can right-click the Command Prompt icon + and click Run as Administrator). b. Execute the following command, where you change "[YOUR_INSTALL_DIRECTORY]": -NETSH firewall add allowedprogram program=[YOUR_INSTALL_DIRECTORY]\My -SqlNotifier.exe name=MySqlNotifier +NETSH firewall add allowedprogram program=[YOUR_INSTALL_DIRECTORY]\MyS +qlNotifier.exe name=MySqlNotifier + 4. If Computer B is either a member of WORKGROUP or is in a - different domain that is untrusted by Computer A, then the - callback connection (Connection 2) is created as an Anonymous - connection. To grant Anonymous connections DCOM Remote Access - permissions: - a. Click Start, click Run, type DCOMCNFG, and then click OK. - b. In the Component Services dialog box, expand Component - Services, expand Computers, and then right-click My - Computer and click Properties. - c. In the My Computer Properties dialog box, click the COM - Security tab. + different domain that is untrusted by Computer A, then + the callback connection (Connection 2) is created as an + Anonymous connection. To grant Anonymous connections DCOM + Remote Access permissions: + a. Click Start, click Run, type DCOMCNFG, and then + click OK. + b. In the Component Services dialog box, expand + Component Services, expand Computers, and then + right-click My Computer and click Properties. + c. In the My Computer Properties dialog box, click the + COM Security tab. d. Under Access Permissions, click Edit Limits. - e. In the Access Permission dialog box, select ANONYMOUS - LOGON name in the Group or user names box. In the Allow - column under Permissions for User, select Remote Access, - and then click OK. + e. In the Access Permission dialog box, select + ANONYMOUS LOGON name in the Group or user names box. + In the Allow column under Permissions for User, + select Remote Access, and then click OK. Monitored Remote Computer (Computer B) - If the user account that is logged into the computer running the - MySQL Notifier for Microsoft Windows (Computer A) is a local - administrator on the remote computer (Computer B), such that the - same account is an administrator on Computer B, you can skip to - the "Allow for remote administration" step. - - Setting DCOM security to allow a non-administrator user to access - a computer remotely: - - 1. Grant "DCOM remote launch" and activation permissions for a - user or group: - a. Click Start, click Run, type DCOMCNFG, and then click OK. - b. In the Component Services dialog box, expand Component - Services, expand Computers, and then right-click My - Computer and click Properties. - c. In the My Computer Properties dialog box, click the COM - Security tab. + If the user account that is logged into the computer running + the MySQL Notifier (Computer A) is a local administrator on + the remote computer (Computer B), such that the same account + is an administrator on Computer B, you can skip to the "Allow + for remote administration" step. + + Setting DCOM security to allow a non-administrator user to + access a computer remotely: + + 1. Grant "DCOM remote launch" and activation permissions for + a user or group: + a. Click Start, click Run, type DCOMCNFG, and then + click OK. + b. In the Component Services dialog box, expand + Component Services, expand Computers, and then + right-click My Computer and click Properties. + c. In the My Computer Properties dialog box, click the + COM Security tab. d. Under Access Permissions, click Edit Limits. - e. In the Launch Permission dialog box, follow these steps - if your name or your group does not appear in the Groups - or user names list: + e. In the Launch Permission dialog box, follow these + steps if your name or your group does not appear in + the Groups or user names list: i. In the Launch Permission dialog box, click Add. - ii. In the Select Users, Computers, or Groups dialog - box, add your name and the group in the "Enter the - object names to select" box, and then click OK. - f. In the Launch Permission dialog box, select your user and - group in the Group or user names box. In the Allow column - under Permissions for User, select Remote Launch, select - Remote Activation, and then click OK. + ii. In the Select Users, Computers, or Groups + dialog box, add your name and the group in the + "Enter the object names to select" box, and + then click OK. + f. In the Launch Permission dialog box, select your + user and group in the Group or user names box. In + the Allow column under Permissions for User, select + Remote Launch, select Remote Activation, and then + click OK. Grant DCOM remote access permissions: - a. Click Start, click Run, type DCOMCNFG, and then click OK. - b. In the Component Services dialog box, expand Component - Services, expand Computers, and then right-click My - Computer and click Properties. - c. In the My Computer Properties dialog box, click the COM - Security tab. + a. Click Start, click Run, type DCOMCNFG, and then + click OK. + b. In the Component Services dialog box, expand + Component Services, expand Computers, and then + right-click My Computer and click Properties. + c. In the My Computer Properties dialog box, click the + COM Security tab. d. Under Access Permissions, click Edit Limits. - e. In the Access Permission dialog box, select ANONYMOUS - LOGON name in the Group or user names box. In the Allow - column under Permissions for User, select Remote Access, - and then click OK. + e. In the Access Permission dialog box, select + ANONYMOUS LOGON name in the Group or user names box. + In the Allow column under Permissions for User, + select Remote Access, and then click OK. 2. Allowing non-administrator users access to a specific WMI namespace: - a. In the Control Panel, double-click Administrative Tools. - b. In the Administrative Tools window, double-click Computer - Management. - c. In the Computer Management window, expand the Services - and Applications tree and double-click the WMI Control. - d. Right-click the WMI Control icon and select Properties. - e. In the WMI Control Properties window, click the Security - tab. + a. In the Control Panel, double-click Administrative + Tools. + b. In the Administrative Tools window, double-click + Computer Management. + c. In the Computer Management window, expand the + Services and Applications tree and double-click the + WMI Control. + d. Right-click the WMI Control icon and select + Properties. + e. In the WMI Control Properties window, click the + Security tab. f. In the Security tab, select the namespace and click Security. - g. Locate the appropriate account and check Remote Enable in - the Permissions list. + g. Locate the appropriate account and check Remote + Enable in the Permissions list. - 3. Allow for remote administration by either editing the Group - Policy Editor or using NETSH: + 3. Allow for remote administration by either editing the + Group Policy Editor or using NETSH: Using the Group Policy Editor: - a. Click Start, click Run, type GPEDIT.MSC, and then click - OK. - b. Under the Local Computer Policy heading, double-click - Computer Configuration. + a. Click Start, click Run, type GPEDIT.MSC, and then + click OK. + b. Under the Local Computer Policy heading, + double-click Computer Configuration. c. Double-click Administrative Templates, then Network, Network Connections, and then Windows Firewall. d. If the computer is in the domain, then double-click - Domain Profile; otherwise, double-click Standard Profile. + Domain Profile; otherwise, double-click Standard + Profile. e. Click Windows Firewall: Allow inbound remote administration exception. - f. On the Action menu either select Edit, or double-click - the selection from the previous step. + f. On the Action menu either select Edit, or + double-click the selection from the previous step. g. Check the Enabled radio button, and then click OK. Using the NETSH command: - a. Open a command prompt window with Administrative rights - (you can right-click the Command Prompt icon and click - Run as Administrator). + a. Open a command prompt window with Administrative + rights (you can right-click the Command Prompt icon + and click Run as Administrator). b. Execute the following command: NETSH firewall set service RemoteAdmin enable - 4. Now, be sure the user you are logging in with uses the Name - value and not the Full Name value: - a. In the Control Panel, double-click Administrative Tools. - b. In the Administrative Tools window, double-click Computer - Management. + + 4. Now, be sure the user you are logging in with uses the + Name value and not the Full Name value: + a. In the Control Panel, double-click Administrative + Tools. + b. In the Administrative Tools window, double-click + Computer Management. c. In the Computer Management window, expand the System Tools then Local Users and Groups. - d. Click the Users node, and on the right side panel locate - your user and make sure it uses the Name value to - connect, and not the Full Name value. - - 5. If the remote computer is running on Windows XP Professional, - make sure that remote logins are not being forcefully changed - to the guest account user (also known as ForceGuest), which is - enabled by default on computers that are not attached to a - domain. - a. Click Start, click Run, type SECPOL.MSC, and then click - OK. + d. Click the Users node, and on the right side panel + locate your user and make sure it uses the Name + value to connect, and not the Full Name value. + + 5. If the remote computer is running on Windows XP + Professional, make sure that remote logins are not being + forcefully changed to the guest account user (also known + as ForceGuest), which is enabled by default on computers + that are not attached to a domain. + a. Click Start, click Run, type SECPOL.MSC, and then + click OK. b. Under the Local Policies node, double-click Security Options. - c. Select Network Access: Sharing and security model for - local accounts and save. + c. Select Network Access: Sharing and security model + for local accounts and save. Common Errors * 0x80070005 - + DCOM Security was not configured properly (see Computer - B, the Setting DCOM security... step). + + DCOM Security was not configured properly (see + Computer B, the Setting DCOM security... step). - + The remote computer (Computer B) is a member of WORKGROUP - or is in a domain that is untrusted by the client - computer (Computer A) (see Computer A, the Grant - Anonymous connections DCOM Remote Access permissions - step). + + The remote computer (Computer B) is a member of + WORKGROUP or is in a domain that is untrusted by the + client computer (Computer A) (see Computer A, the + Grant Anonymous connections DCOM Remote Access + permissions step). * 0x8007000E - + The remote computer (Computer B) is a member of WORKGROUP - or is in a domain that is untrusted by the client - computer (Computer A) (see Computer A, the Grant - Anonymous connections DCOM Remote Access permissions - step). + + The remote computer (Computer B) is a member of + WORKGROUP or is in a domain that is untrusted by the + client computer (Computer A) (see Computer A, the + Grant Anonymous connections DCOM Remote Access + permissions step). * 0x80041003 - + Access to the remote WMI namespace was not configured - properly (see Computer B, the Allowing non-administrator - users access to a specific WMI namespace step). + + Access to the remote WMI namespace was not + configured properly (see Computer B, the Allowing + non-administrator users access to a specific WMI + namespace step). * 0x800706BA + The DCOM port is not open on the client computers - (Computer A) firewall. See the Open the DCOM port TCP 135 - step for Computer A. + (Computer A) firewall. See the Open the DCOM port + TCP 135 step for Computer A. - + The remote computer (Computer B) is inaccessible because - its network location is set to Public. Make sure you can - access it through the Windows Explorer. - -2.3.5. Installing MySQL on Microsoft Windows Using an MSI Package - - The MSI package is designed to install and configure MySQL in such - a way that you can immediately get started using MySQL. - - The MySQL Installation Wizard and MySQL Configuration Wizard are - available in the Complete install package, which is recommended - for most standard MySQL installations. Exceptions include users - who need to install multiple instances of MySQL on a single server - host and advanced users who want complete control of server - configuration. + + The remote computer (Computer B) is inaccessible + because its network location is set to Public. Make + sure you can access it through the Windows Explorer. + +2.3.5 Installing MySQL on Microsoft Windows Using an MSI Package + + The MSI package is designed to install and configure MySQL in + such a way that you can immediately get started using MySQL. + + The MySQL Installation Wizard and MySQL Configuration Wizard + are available in the Complete install package, which is + recommended for most standard MySQL installations. Exceptions + include users who need to install multiple instances of MySQL + on a single server host and advanced users who want complete + control of server configuration. * For information on installing using the GUI MSI installer - process, see Section 2.3.5.1, "Using the MySQL Installation - Wizard." + process, see Section 2.3.5.1, "Using the MySQL + Installation Wizard." - * For information on installing using the command line using the - MSI package, see Section 2.3.5.2, "Automating MySQL - Installation on Microsoft Windows Using the MSI Package." - - * If you have previously installed MySQL using the MSI package - and want to remove MySQL, see Section 2.3.5.3, "Removing MySQL - When Installed from the MSI Package." + * For information on installing using the command line + using the MSI package, see Section 2.3.5.2, "Automating + MySQL Installation on Microsoft Windows Using the MSI + Package." + + * If you have previously installed MySQL using the MSI + package and want to remove MySQL, see Section 2.3.5.3, + "Removing MySQL When Installed from the MSI Package." The workflow sequence for using the installer is shown in the figure below: - Figure 2.30. Installation Workflow for Windows Using MSI Installer + Figure 2.40 Installation Workflow for Windows Using MSI + Installer Installation Workflow for Windows using MSI Installer Note Microsoft Windows XP and later include a firewall which - specifically blocks ports. If you plan on using MySQL through a - network port then you should open and create an exception for this - port before performing the installation. To check and if necessary - add an exception to the firewall settings: + specifically blocks ports. If you plan on using MySQL through + a network port then you should open and create an exception + for this port before performing the installation. To check + and if necessary add an exception to the firewall settings: - 1. First ensure that you are logged in as an Administrator or a - user with Administrator privileges. + 1. First ensure that you are logged in as an Administrator + or a user with Administrator privileges. - 2. Go to the Control Panel, and double click the Windows Firewall - icon. + 2. Go to the Control Panel, and double click the Windows + Firewall icon. - 3. Choose the Allow a program through Windows Firewall option and - click the Add port button. + 3. Choose the Allow a program through Windows Firewall + option and click the Add port button. - 4. Enter MySQL into the Name text box and 3306 (or the port of - your choice) into the Port number text box. + 4. Enter MySQL into the Name text box and 3306 (or the port + of your choice) into the Port number text box. - 5. Also ensure that the TCP protocol radio button is selected. + 5. Also ensure that the TCP protocol radio button is + selected. - 6. If you wish, you can also limit access to the MySQL server by - choosing the Change scope button. + 6. If you wish, you can also limit access to the MySQL + server by choosing the Change scope button. 7. Confirm your choices by clicking the OK button. Additionally, when running the MySQL Installation Wizard on - Windows Vista or newer, ensure that you are logged in as a user - with administrative rights. + Windows Vista or newer, ensure that you are logged in as a + user with administrative rights. Note - When using Windows Vista or newer, you may want to disable User - Account Control (UAC) before performing the installation. If you - do not do so, then MySQL may be identified as a security risk, - which will mean that you need to enable MySQL. You can disable the - security checking by following these instructions: + When using Windows Vista or newer, you may want to disable + User Account Control (UAC) before performing the + installation. If you do not do so, then MySQL may be + identified as a security risk, which will mean that you need + to enable MySQL. You can disable the security checking by + following these instructions: 1. Open Control Panel. @@ -1260,199 +1688,213 @@ 3. Click the Got to the main User Accounts page link. 4. Click on Turn User Account Control on or off. You may be - prompted to provide permission to change this setting. Click - Continue. + prompted to provide permission to change this setting. + Click Continue. - 5. Deselect or uncheck the check box next to Use User Account - Control (UAC) to help protect your computer. Click OK to save - the setting. - - You will need to restart to complete the process. Click Restart - Now to reboot the machine and apply the changes. You can then - follow the instructions below for installing Windows. - -2.3.5.1. Using the MySQL Installation Wizard - - MySQL Installation Wizard is an installer for the MySQL server - that uses the latest installer technologies for Microsoft Windows. - The MySQL Installation Wizard, in combination with the MySQL - Configuration Wizard, enables a user to install and configure a - MySQL server that is ready for use immediately after installation. - - The MySQL Installation Wizard is the standard installer for all - MySQL server distributions, version 4.1.5 and higher. Users of - previous versions of MySQL need to shut down and remove their - existing MySQL installations manually before installing MySQL with - the MySQL Installation Wizard. See Section 2.3.5.1.6, "Upgrading - MySQL with the Installation Wizard," for more information on - upgrading from a previous version. + 5. Deselect or uncheck the check box next to Use User + Account Control (UAC) to help protect your computer. + Click OK to save the setting. + + You will need to restart to complete the process. Click + Restart Now to reboot the machine and apply the changes. You + can then follow the instructions below for installing + Windows. + +2.3.5.1 Using the MySQL Installation Wizard + + MySQL Installation Wizard is an installer for the MySQL + server that uses the latest installer technologies for + Microsoft Windows. The MySQL Installation Wizard, in + combination with the MySQL Configuration Wizard, enables a + user to install and configure a MySQL server that is ready + for use immediately after installation. + + The MySQL Installation Wizard is the standard installer for + all MySQL server distributions, version 4.1.5 and higher. + Users of previous versions of MySQL need to shut down and + remove their existing MySQL installations manually before + installing MySQL with the MySQL Installation Wizard. See + Section 2.3.5.1.6, "Upgrading MySQL with the Installation + Wizard," for more information on upgrading from a previous + version. Microsoft has included an improved version of their Microsoft - Windows Installer (MSI) in the recent versions of Windows. MSI has - become the de-facto standard for application installations on - Windows 2000, Windows XP, and Windows Server 2003. The MySQL - Installation Wizard makes use of this technology to provide a - smoother and more flexible installation process. + Windows Installer (MSI) in the recent versions of Windows. + MSI has become the de-facto standard for application + installations on Windows 2000, Windows XP, and Windows Server + 2003. The MySQL Installation Wizard makes use of this + technology to provide a smoother and more flexible + installation process. The Microsoft Windows Installer Engine was updated with the - release of Windows XP; those using a previous version of Windows - can reference this Microsoft Knowledge Base article - (http://support.microsoft.com/default.aspx?scid=kb;EN-US;292539) - for information on upgrading to the latest version of the Windows - Installer Engine. - - In addition, Microsoft has introduced the WiX (Windows Installer - XML) toolkit recently. This is the first highly acknowledged Open - Source project from Microsoft. We have switched to WiX because it - is an Open Source project and it enables us to handle the complete - Windows installation process in a flexible manner using scripts. - - Improving the MySQL Installation Wizard depends on the support and - feedback of users like you. If you find that the MySQL - Installation Wizard is lacking some feature important to you, or - if you discover a bug, please report it in our bugs database using - the instructions given in Section 1.7, "How to Report Bugs or - Problems." + release of Windows XP; those using a previous version of + Windows can reference this Microsoft Knowledge Base article + (http://support.microsoft.com/default.aspx?scid=kb;EN-US;2925 + 39) for information on upgrading to the latest version of the + Windows Installer Engine. + + In addition, Microsoft has introduced the WiX (Windows + Installer XML) toolkit recently. This is the first highly + acknowledged Open Source project from Microsoft. We have + switched to WiX because it is an Open Source project and it + enables us to handle the complete Windows installation + process in a flexible manner using scripts. + + Improving the MySQL Installation Wizard depends on the + support and feedback of users like you. If you find that the + MySQL Installation Wizard is lacking some feature important + to you, or if you discover a bug, please report it in our + bugs database using the instructions given in Section 1.7, + "How to Report Bugs or Problems." -2.3.5.1.1. Downloading and Starting the MySQL Installation Wizard +2.3.5.1.1 Downloading and Starting the MySQL Installation Wizard The MySQL installation packages can be downloaded from - http://dev.mysql.com/downloads/. If the package you download is - contained within a Zip archive, you need to extract the archive - first. - Note - - If you are installing on Windows Vista or newer, it is best to - open a network port before beginning the installation. To do this, - first ensure that you are logged in as an Administrator, go to the - Control Panel, and double-click the Windows Firewall icon. Choose - the Allow a program through Windows Firewall option and click the - Add port button. Enter MySQL into the Name text box and 3306 (or - the port of your choice) into the Port number text box. Also - ensure that the TCP protocol radio button is selected. If you - wish, you can also limit access to the MySQL server by choosing - the Change scope button. Confirm your choices by clicking the OK - button. If you do not open a port prior to installation, you - cannot configure the MySQL server immediately after installation. + http://dev.mysql.com/downloads/. If the package you download + is contained within a Zip archive, you need to extract the + archive first. + Note + + If you are installing on Windows Vista or newer, it is best + to open a network port before beginning the installation. To + do this, first ensure that you are logged in as an + Administrator, go to the Control Panel, and double-click the + Windows Firewall icon. Choose the Allow a program through + Windows Firewall option and click the Add port button. Enter + MySQL into the Name text box and 3306 (or the port of your + choice) into the Port number text box. Also ensure that the + TCP protocol radio button is selected. If you wish, you can + also limit access to the MySQL server by choosing the Change + scope button. Confirm your choices by clicking the OK button. + If you do not open a port prior to installation, you cannot + configure the MySQL server immediately after installation. Additionally, when running the MySQL Installation Wizard on - Windows Vista or newer, ensure that you are logged in as a user - with administrative rights. - - The process for starting the wizard depends on the contents of the - installation package you download. If there is a setup.exe file - present, double-click it to start the installation process. If - there is an .msi file present, double-click it to start the - installation process. - -2.3.5.1.2. Choosing an Install Type + Windows Vista or newer, ensure that you are logged in as a + user with administrative rights. - There are three installation types available: Typical, Complete, - and Custom. + The process for starting the wizard depends on the contents + of the installation package you download. If there is a + setup.exe file present, double-click it to start the + installation process. If there is an .msi file present, + double-click it to start the installation process. + +2.3.5.1.2 Choosing an Install Type + + There are three installation types available: Typical, + Complete, and Custom. + + The Typical installation type installs the MySQL server, the + mysql command-line client, and the command-line utilities. + The command-line clients and utilities include mysqldump, + myisamchk, and several other tools to help you manage the + MySQL server. - The Typical installation type installs the MySQL server, the mysql - command-line client, and the command-line utilities. The - command-line clients and utilities include mysqldump, myisamchk, - and several other tools to help you manage the MySQL server. - - The Complete installation type installs all components included in - the installation package. The full installation package includes - components such as the embedded server library, the benchmark - suite, support scripts, and documentation. - - The Custom installation type gives you complete control over which - packages you wish to install and the installation path that is - used. See Section 2.3.5.1.3, "The Custom Install Dialog," for more - information on performing a custom install. - - If you choose the Typical or Complete installation types and click - the Next button, you advance to the confirmation screen to verify - your choices and begin the installation. If you choose the Custom - installation type and click the Next button, you advance to the - custom installation dialog, described in Section 2.3.5.1.3, "The - Custom Install Dialog." + The Complete installation type installs all components + included in the installation package. The full installation + package includes components such as the embedded server + library, the benchmark suite, support scripts, and + documentation. + + The Custom installation type gives you complete control over + which packages you wish to install and the installation path + that is used. See Section 2.3.5.1.3, "The Custom Install + Dialog," for more information on performing a custom install. + + If you choose the Typical or Complete installation types and + click the Next button, you advance to the confirmation screen + to verify your choices and begin the installation. If you + choose the Custom installation type and click the Next + button, you advance to the custom installation dialog, + described in Section 2.3.5.1.3, "The Custom Install Dialog." -2.3.5.1.3. The Custom Install Dialog +2.3.5.1.3 The Custom Install Dialog If you wish to change the installation path or the specific - components that are installed by the MySQL Installation Wizard, - choose the Custom installation type. + components that are installed by the MySQL Installation + Wizard, choose the Custom installation type. - A tree view on the left side of the custom install dialog lists - all available components. Components that are not installed have a - red X icon; components that are installed have a gray icon. To - change whether a component is installed, click that component's - icon and choose a new option from the drop-down list that appears. + A tree view on the left side of the custom install dialog + lists all available components. Components that are not + installed have a red X icon; components that are installed + have a gray icon. To change whether a component is installed, + click that component's icon and choose a new option from the + drop-down list that appears. You can change the default installation path by clicking the - Change... button to the right of the displayed installation path. + Change... button to the right of the displayed installation + path. - After choosing your installation components and installation path, - click the Next button to advance to the confirmation dialog. - -2.3.5.1.4. The Confirmation Dialog - - Once you choose an installation type and optionally choose your - installation components, you advance to the confirmation dialog. - Your installation type and installation path are displayed for you - to review. - - To install MySQL if you are satisfied with your settings, click - the Install button. To change your settings, click the Back - button. To exit the MySQL Installation Wizard without installing - MySQL, click the Cancel button. + After choosing your installation components and installation + path, click the Next button to advance to the confirmation + dialog. + +2.3.5.1.4 The Confirmation Dialog + + Once you choose an installation type and optionally choose + your installation components, you advance to the confirmation + dialog. Your installation type and installation path are + displayed for you to review. + + To install MySQL if you are satisfied with your settings, + click the Install button. To change your settings, click the + Back button. To exit the MySQL Installation Wizard without + installing MySQL, click the Cancel button. The final screen of the installer provides a summary of the installation and gives you the option to launch the MySQL - Configuration Wizard, which you can use to create a configuration - file, install the MySQL service, and configure security settings. - -2.3.5.1.5. Changes Made by MySQL Installation Wizard - - Once you click the Install button, the MySQL Installation Wizard - begins the installation process and makes certain changes to your - system which are described in the sections that follow. + Configuration Wizard, which you can use to create a + configuration file, install the MySQL service, and configure + security settings. + +2.3.5.1.5 Changes Made by MySQL Installation Wizard + + Once you click the Install button, the MySQL Installation + Wizard begins the installation process and makes certain + changes to your system which are described in the sections + that follow. Changes to the Registry - The MySQL Installation Wizard creates one Windows registry key in - a typical install situation, located in + The MySQL Installation Wizard creates one Windows registry + key in a typical install situation, located in HKEY_LOCAL_MACHINE\SOFTWARE\MySQL AB. - The MySQL Installation Wizard creates a key named after the major - version of the server that is being installed, such as MySQL - Server 5.5. It contains two string values, Location and Version. - The Location string contains the path to the installation - directory. In a default installation it contains C:\Program - Files\MySQL\MySQL Server 5.5\. The Version string contains the - release number. For example, for an installation of MySQL Server - 5.5.36, the key contains a value of 5.5.36. - - These registry keys are used to help external tools identify the - installed location of the MySQL server, preventing a complete scan - of the hard-disk to determine the installation path of the MySQL - server. The registry keys are not required to run the server, and - if you install MySQL using the noinstall Zip archive, the registry - keys are not created. + The MySQL Installation Wizard creates a key named after the + major version of the server that is being installed, such as + MySQL Server 5.5. It contains two string values, Location and + Version. The Location string contains the path to the + installation directory. In a default installation it contains + C:\Program Files\MySQL\MySQL Server 5.5\. The Version string + contains the release number. For example, for an installation + of MySQL Server 5.5.44, the key contains a value of 5.5.44. + + These registry keys are used to help external tools identify + the installed location of the MySQL server, preventing a + complete scan of the hard-disk to determine the installation + path of the MySQL server. The registry keys are not required + to run the server, and if you install MySQL using the + noinstall Zip archive, the registry keys are not created. Changes to the Start Menu - The MySQL Installation Wizard creates a new entry in the Windows - Start menu under a common MySQL menu heading named after the major - version of MySQL that you have installed. For example, if you - install MySQL 5.5, the MySQL Installation Wizard creates a MySQL - Server 5.5 section in the Start menu. + The MySQL Installation Wizard creates a new entry in the + Windows Start menu under a common MySQL menu heading named + after the major version of MySQL that you have installed. For + example, if you install MySQL 5.5, the MySQL Installation + Wizard creates a MySQL Server 5.5 section in the Start menu. The following entries are created within the new Start menu section: - * MySQL Command-Line Client: This is a shortcut to the mysql - command-line client and is configured to connect as the root - user. The shortcut prompts for a root user password when you - connect. - - * MySQL Server Instance Config Wizard: This is a shortcut to the - MySQL Configuration Wizard. Use this shortcut to configure a - newly installed server, or to reconfigure an existing server. + * MySQL Command-Line Client: This is a shortcut to the + mysql command-line client and is configured to connect as + the root user. The shortcut prompts for a root user + password when you connect. + + * MySQL Server Instance Config Wizard: This is a shortcut + to the MySQL Configuration Wizard. Use this shortcut to + configure a newly installed server, or to reconfigure an + existing server. * MySQL Documentation: This is a link to the MySQL server documentation that is stored locally in the MySQL server @@ -1460,118 +1902,122 @@ Changes to the File System - The MySQL Installation Wizard by default installs the MySQL 5.5 - server to C:\Program Files\MySQL\MySQL Server 5.5, where Program - Files is the default location for applications in your system, and - 5.5 is the major version of your MySQL server. This is the - recommended location for the MySQL server, replacing the former - default location C:\mysql. + The MySQL Installation Wizard by default installs the MySQL + 5.5 server to C:\Program Files\MySQL\MySQL Server 5.5, where + Program Files is the default location for applications in + your system, and 5.5 is the major version of your MySQL + server. This is the recommended location for the MySQL + server, replacing the former default location C:\mysql. By default, all MySQL applications are stored in a common - directory at C:\Program Files\MySQL, where Program Files is the - default location for applications in your Windows installation. A - typical MySQL installation on a developer machine might look like - this: + directory at C:\Program Files\MySQL, where Program Files is + the default location for applications in your Windows + installation. A typical MySQL installation on a developer + machine might look like this: C:\Program Files\MySQL\MySQL Server 5.5 C:\Program Files\MySQL\MySQL Workbench 5.1 OSS - This approach makes it easier to manage and maintain all MySQL - applications installed on a particular system. + This approach makes it easier to manage and maintain all + MySQL applications installed on a particular system. The default location of the data directory is the AppData directory configured for the user that installed the MySQL application. -2.3.5.1.6. Upgrading MySQL with the Installation Wizard +2.3.5.1.6 Upgrading MySQL with the Installation Wizard The MySQL Installation Wizard can perform server upgrades - automatically using the upgrade capabilities of MSI. That means - you do not need to remove a previous installation manually before - installing a new release. The installer automatically shuts down - and removes the previous MySQL service before installing the new - version. + automatically using the upgrade capabilities of MSI. That + means you do not need to remove a previous installation + manually before installing a new release. The installer + automatically shuts down and removes the previous MySQL + service before installing the new version. Automatic upgrades are available only when upgrading between - installations that have the same major and minor version numbers. - For example, you can upgrade automatically from MySQL 5.5.5 to - MySQL 5.5.6, but not from MySQL 5.1 to MySQL 5.5. + installations that have the same major and minor version + numbers. For example, you can upgrade automatically from + MySQL 5.5.5 to MySQL 5.5.6, but not from MySQL 5.1 to MySQL + 5.5. See Section 2.3.9, "Upgrading MySQL on Windows." -2.3.5.2. Automating MySQL Installation on Microsoft Windows Using the -MSI Package +2.3.5.2 Automating MySQL Installation on Microsoft Windows Using +the MSI Package The Microsoft Installer (MSI) supports a both a quiet and a passive mode that can be used to install MySQL automatically - without requiring intervention. You can use this either in scripts - to automatically install MySQL or through a terminal connection - such as Telnet where you do not have access to the standard - Windows user interface. The MSI packages can also be used in - combination with Microsoft's Group Policy system (part of Windows - Server 2003 and Windows Server 2008) to install MySQL across - multiple machines. - - To install MySQL from one of the MSI packages automatically from - the command line (or within a script), you need to use the - msiexec.exe tool. For example, to perform a quiet installation - (which shows no dialog boxes or progress): -shell> msiexec /i mysql-5.5.36.msi /quiet - - The /i indicates that you want to perform an installation. The - /quiet option indicates that you want no interactive elements. - - To provide a dialog box showing the progress during installation, - and the dialog boxes providing information on the installation and - registration of MySQL, use /passive mode instead of /quiet: -shell> msiexec /i mysql-5.5.36.msi /passive - - Regardless of the mode of the installation, installing the package - in this manner performs a 'Typical' installation, and installs the - default components into the standard location. + without requiring intervention. You can use this either in + scripts to automatically install MySQL or through a terminal + connection such as Telnet where you do not have access to the + standard Windows user interface. The MSI packages can also be + used in combination with Microsoft's Group Policy system + (part of Windows Server 2003 and Windows Server 2008) to + install MySQL across multiple machines. + + To install MySQL from one of the MSI packages automatically + from the command line (or within a script), you need to use + the msiexec.exe tool. For example, to perform a quiet + installation (which shows no dialog boxes or progress): +shell> msiexec /i mysql-5.5.44.msi /quiet + + The /i indicates that you want to perform an installation. + The /quiet option indicates that you want no interactive + elements. + + To provide a dialog box showing the progress during + installation, and the dialog boxes providing information on + the installation and registration of MySQL, use /passive mode + instead of /quiet: +shell> msiexec /i mysql-5.5.44.msi /passive + + Regardless of the mode of the installation, installing the + package in this manner performs a 'Typical' installation, and + installs the default components into the standard location. You can also use this method to uninstall MySQL by using the /uninstall or /x options: -shell> msiexec /x mysql-5.5.36.msi /uninstall +shell> msiexec /x mysql-5.5.44.msi /uninstall - To install MySQL and configure a MySQL instance from the command - line, see Section 2.3.6.13, "MySQL Server Instance Config Wizard: - Creating an Instance from the Command Line." + To install MySQL and configure a MySQL instance from the + command line, see Section 2.3.6.13, "MySQL Server Instance + Config Wizard: Creating an Instance from the Command Line." For information on using MSI packages to install software - automatically using Group Policy, see How to use Group Policy to - remotely install software in Windows Server 2003 + automatically using Group Policy, see How to use Group Policy + to remotely install software in Windows Server 2003 (http://support.microsoft.com/kb/816102). -2.3.5.3. Removing MySQL When Installed from the MSI Package +2.3.5.3 Removing MySQL When Installed from the MSI Package - To uninstall a MySQL where you have used the MSI packages, you - must use the Add/Remove Programs tool within Control Panel. To do - this: + To uninstall a MySQL where you have used the MSI packages, + you must use the Add/Remove Programs tool within Control + Panel. To do this: 1. Right-click the start menu and choose Control Panel. - 2. If the Control Panel is set to category mode (you will see - Pick a category at the top of the Control Panel window), - double-click Add or Remove Programs. If the Control is set to - classic mode, double-click the Add or Remove Programs icon. - - 3. Find MySQL in the list of installed software. MySQL Server is - installed against major version numbers (MySQL 5.1, MySQL 5.5, - etc.). Select the version that you want to remove and click - Remove. + 2. If the Control Panel is set to category mode (you will + see Pick a category at the top of the Control Panel + window), double-click Add or Remove Programs. If the + Control is set to classic mode, double-click the Add or + Remove Programs icon. + + 3. Find MySQL in the list of installed software. MySQL + Server is installed against major version numbers (MySQL + 5.1, MySQL 5.5, etc.). Select the version that you want + to remove and click Remove. 4. You will be prompted to confirm the removal. Click Yes to remove MySQL. When MySQL is removed using this method, only the installed - components are removed. Any database information (including the - tables and data), import or export files, log files, and binary - logs produced during execution are kept in their configured - location. - - If you try to install MySQL again the information will be retained - and you will be prompted to enter the password configured with the - original installation. + components are removed. Any database information (including + the tables and data), import or export files, log files, and + binary logs produced during execution are kept in their + configured location. + + If you try to install MySQL again the information will be + retained and you will be prompted to enter the password + configured with the original installation. If you want to delete MySQL completely: @@ -1583,86 +2029,92 @@ * On Windows 7 and Windows Server 2008, the default data directory location is C:\ProgramData\Mysql. Note - The C:\ProgramData directory is hidden by default. You must - change your folder options to view the hidden file. Choose - Organize, Folder and search options, Show hidden folders. - -2.3.6. MySQL Server Instance Configuration Wizard - - The MySQL Server Instance Configuration Wizard helps automate the - process of configuring your server. It creates a custom MySQL - configuration file (my.ini or my.cnf) by asking you a series of - questions and then applying your responses to a template to - generate the configuration file that is tuned to your - installation. - - The MySQL Server Instance Configuration Wizard is included with - the MySQL 5.5 server. The MySQL Server Instance Configuration - Wizard is only available for Windows. - -2.3.6.1. Starting the MySQL Server Instance Configuration Wizard - - The MySQL Server Instance Configuration Wizard is normally started - as part of the installation process. You should only need to run - the MySQL Server Instance Configuration Wizard again when you need - to change the configuration parameters of your server. + The C:\ProgramData directory is hidden by default. You + must change your folder options to view the hidden file. + Choose Organize, Folder and search options, Show hidden + folders. + +2.3.6 MySQL Server Instance Configuration Wizard + + The MySQL Server Instance Configuration Wizard helps automate + the process of configuring your server. It creates a custom + MySQL configuration file (my.ini or my.cnf) by asking you a + series of questions and then applying your responses to a + template to generate the configuration file that is tuned to + your installation. + + The MySQL Server Instance Configuration Wizard is included + with the MySQL 5.5 server. The MySQL Server Instance + Configuration Wizard is only available for Windows. + +2.3.6.1 Starting the MySQL Server Instance Configuration Wizard + + The MySQL Server Instance Configuration Wizard is normally + started as part of the installation process. You should only + need to run the MySQL Server Instance Configuration Wizard + again when you need to change the configuration parameters of + your server. If you chose not to open a port prior to installing MySQL on - Windows Vista or newer, you can choose to use the MySQL Server - Configuration Wizard after installation. However, you must open a - port in the Windows Firewall. To do this see the instructions - given in Section 2.3.5.1.1, "Downloading and Starting the MySQL - Installation Wizard." Rather than opening a port, you also have - the option of adding MySQL as a program that bypasses the Windows - Firewall. One or the other option is sufficient---you need not do - both. Additionally, when running the MySQL Server Configuration - Wizard on Windows Vista or newer, ensure that you are logged in as - a user with administrative rights. + Windows Vista or newer, you can choose to use the MySQL + Server Configuration Wizard after installation. However, you + must open a port in the Windows Firewall. To do this see the + instructions given in Section 2.3.5.1.1, "Downloading and + Starting the MySQL Installation Wizard." Rather than opening + a port, you also have the option of adding MySQL as a program + that bypasses the Windows Firewall. One or the other option + is sufficient---you need not do both. Additionally, when + running the MySQL Server Configuration Wizard on Windows + Vista or newer, ensure that you are logged in as a user with + administrative rights. MySQL Server Instance Configuration Wizard You can launch the MySQL Configuration Wizard by clicking the - MySQL Server Instance Config Wizard entry in the MySQL section of - the Windows Start menu. - - Alternatively, you can navigate to the bin directory of your MySQL - installation and launch the MySQLInstanceConfig.exe file directly. - - The MySQL Server Instance Configuration Wizard places the my.ini - file in the installation directory for the MySQL server. This - helps associate configuration files with particular server - instances. + MySQL Server Instance Config Wizard entry in the MySQL + section of the Windows Start menu. - To ensure that the MySQL server knows where to look for the my.ini - file, an argument similar to this is passed to the MySQL server as - part of the service installation: + Alternatively, you can navigate to the bin directory of your + MySQL installation and launch the MySQLInstanceConfig.exe + file directly. + + The MySQL Server Instance Configuration Wizard places the + my.ini file in the installation directory for the MySQL + server. This helps associate configuration files with + particular server instances. + + To ensure that the MySQL server knows where to look for the + my.ini file, an argument similar to this is passed to the + MySQL server as part of the service installation: --defaults-file="C:\Program Files\MySQL\MySQL Server 5.5\my.ini" - Here, C:\Program Files\MySQL\MySQL Server 5.5 is replaced with the - installation path to the MySQL Server. The --defaults-file option - instructs the MySQL server to read the specified file for - configuration options when it starts. - - Apart from making changes to the my.ini file by running the MySQL - Server Instance Configuration Wizard again, you can modify it by - opening it with a text editor and making any necessary changes. - You can also modify the server configuration with the - http://www.mysql.com/products/administrator/ utility. For more - information about server configuration, see Section 5.1.3, "Server - Command Options." + Here, C:\Program Files\MySQL\MySQL Server 5.5 is replaced + with the installation path to the MySQL Server. The + --defaults-file option instructs the MySQL server to read the + specified file for configuration options when it starts. + + Apart from making changes to the my.ini file by running the + MySQL Server Instance Configuration Wizard again, you can + modify it by opening it with a text editor and making any + necessary changes. You can also modify the server + configuration with the + http://www.mysql.com/products/administrator/ utility. For + more information about server configuration, see Section + 5.1.3, "Server Command Options." MySQL clients and utilities such as the mysql and mysqldump command-line clients are not able to locate the my.ini file - located in the server installation directory. To configure the - client and utility applications, create a new my.ini file in the - Windows installation directory (for example, C:\WINDOWS). - - Under Windows Server 2003, Windows Server 2000, Windows XP, and - Windows Vista, MySQL Server Instance Configuration Wizard will - configure MySQL to work as a Windows service. To start and stop - MySQL you use the Services application that is supplied as part of - the Windows Administrator Tools. + located in the server installation directory. To configure + the client and utility applications, create a new my.ini file + in the Windows installation directory (for example, + C:\WINDOWS). + + Under Windows Server 2003, Windows Server 2000, Windows XP, + and Windows Vista, MySQL Server Instance Configuration Wizard + will configure MySQL to work as a Windows service. To start + and stop MySQL you use the Services application that is + supplied as part of the Windows Administrator Tools. -2.3.6.2. Choosing a Maintenance Option +2.3.6.2 Choosing a Maintenance Option If the MySQL Server Instance Configuration Wizard detects an existing configuration file, you have the option of either @@ -1672,118 +2124,119 @@ To reconfigure an existing server, choose the Re-configure Instance option and click the Next button. Any existing - configuration file is not overwritten, but renamed (within the - same directory) using a timestamp (Windows) or sequential number - (Linux). To remove the existing server instance, choose the Remove - Instance option and click the Next button. + configuration file is not overwritten, but renamed (within + the same directory) using a timestamp (Windows) or sequential + number (Linux). To remove the existing server instance, + choose the Remove Instance option and click the Next button. If you choose the Remove Instance option, you advance to a - confirmation window. Click the Execute button. The MySQL Server - Configuration Wizard stops and removes the MySQL service, and then - deletes the configuration file. The server installation and its - data folder are not removed. - - If you choose the Re-configure Instance option, you advance to the - Configuration Type dialog where you can choose the type of - installation that you wish to configure. - -2.3.6.3. Choosing a Configuration Type - - When you start the MySQL Server Instance Configuration Wizard for - a new MySQL installation, or choose the Re-configure Instance - option for an existing installation, you advance to the - Configuration Type dialog. - MySQL Server Instance Configuration Wizard: Configuration Type + confirmation window. Click the Execute button. The MySQL + Server Configuration Wizard stops and removes the MySQL + service, and then deletes the configuration file. The server + installation and its data folder are not removed. + + If you choose the Re-configure Instance option, you advance + to the Configuration Type dialog where you can choose the + type of installation that you wish to configure. + +2.3.6.3 Choosing a Configuration Type + + When you start the MySQL Server Instance Configuration Wizard + for a new MySQL installation, or choose the Re-configure + Instance option for an existing installation, you advance to + the Configuration Type dialog. + MySQL Server Instance Configuration Wizard: Configuration + Type There are two configuration types available: Detailed Configuration and Standard Configuration. The Standard - Configuration option is intended for new users who want to get - started with MySQL quickly without having to make many decisions - about server configuration. The Detailed Configuration option is - intended for advanced users who want more fine-grained control - over server configuration. + Configuration option is intended for new users who want to + get started with MySQL quickly without having to make many + decisions about server configuration. The Detailed + Configuration option is intended for advanced users who want + more fine-grained control over server configuration. If you are new to MySQL and need a server configured as a - single-user developer machine, the Standard Configuration should - suit your needs. Choosing the Standard Configuration option causes - the MySQL Configuration Wizard to set all configuration options - automatically with the exception of Service Options and Security - Options. - - The Standard Configuration sets options that may be incompatible - with systems where there are existing MySQL installations. If you - have an existing MySQL installation on your system in addition to - the installation you wish to configure, the Detailed Configuration - option is recommended. + single-user developer machine, the Standard Configuration + should suit your needs. Choosing the Standard Configuration + option causes the MySQL Configuration Wizard to set all + configuration options automatically with the exception of + Service Options and Security Options. + + The Standard Configuration sets options that may be + incompatible with systems where there are existing MySQL + installations. If you have an existing MySQL installation on + your system in addition to the installation you wish to + configure, the Detailed Configuration option is recommended. To complete the Standard Configuration, please refer to the sections on Service Options and Security Options in Section - 2.3.6.10, "The Service Options Dialog," and Section 2.3.6.11, "The - Security Options Dialog," respectively. + 2.3.6.10, "The Service Options Dialog," and Section 2.3.6.11, + "The Security Options Dialog," respectively. -2.3.6.4. The Server Type Dialog +2.3.6.4 The Server Type Dialog - There are three different server types available to choose from. - The server type that you choose affects the decisions that the - MySQL Server Instance Configuration Wizard makes with regard to - memory, disk, and processor usage. + There are three different server types available to choose + from. The server type that you choose affects the decisions + that the MySQL Server Instance Configuration Wizard makes + with regard to memory, disk, and processor usage. MySQL Server Instance Configuration Wizard: Server Type - * Developer Machine: Choose this option for a typical desktop - workstation where MySQL is intended only for personal use. It - is assumed that many other desktop applications are running. - The MySQL server is configured to use minimal system - resources. - - * Server Machine: Choose this option for a server machine where - the MySQL server is running alongside other server - applications such as FTP, email, and Web servers. The MySQL - server is configured to use a moderate portion of the system - resources. + * Developer Machine: Choose this option for a typical + desktop workstation where MySQL is intended only for + personal use. It is assumed that many other desktop + applications are running. The MySQL server is configured + to use minimal system resources. + + * Server Machine: Choose this option for a server machine + where the MySQL server is running alongside other server + applications such as FTP, email, and Web servers. The + MySQL server is configured to use a moderate portion of + the system resources. * Dedicated MySQL Server Machine: Choose this option for a - server machine that is intended to run only the MySQL server. - It is assumed that no other applications are running. The - MySQL server is configured to use all available system - resources. + server machine that is intended to run only the MySQL + server. It is assumed that no other applications are + running. The MySQL server is configured to use all + available system resources. Note - By selecting one of the preconfigured configurations, the values - and settings of various options in your my.cnf or my.ini will be - altered accordingly. The default values and options as described - in the reference manual may therefore be different to the options - and values that were created during the execution of the - configuration wizard. + By selecting one of the preconfigured configurations, the + values and settings of various options in your my.cnf or + my.ini will be altered accordingly. The default values and + options as described in the reference manual may therefore be + different to the options and values that were created during + the execution of the configuration wizard. -2.3.6.5. The Database Usage Dialog +2.3.6.5 The Database Usage Dialog The Database Usage dialog enables you to indicate the storage - engines that you expect to use when creating MySQL tables. The - option you choose determines whether the InnoDB storage engine is - available and what percentage of the server resources are - available to InnoDB. + engines that you expect to use when creating MySQL tables. + The option you choose determines whether the InnoDB storage + engine is available and what percentage of the server + resources are available to InnoDB. MySQL Server Instance Configuration Wizard: Usage Dialog - * Multifunctional Database: This option enables both the InnoDB - and MyISAM storage engines and divides resources evenly - between the two. This option is recommended for users who use - both storage engines on a regular basis. + * Multifunctional Database: This option enables both the + InnoDB and MyISAM storage engines and divides resources + evenly between the two. This option is recommended for + users who use both storage engines on a regular basis. * Transactional Database Only: This option enables both the - InnoDB and MyISAM storage engines, but dedicates most server - resources to the InnoDB storage engine. This option is - recommended for users who use InnoDB almost exclusively and - make only minimal use of MyISAM. + InnoDB and MyISAM storage engines, but dedicates most + server resources to the InnoDB storage engine. This + option is recommended for users who use InnoDB almost + exclusively and make only minimal use of MyISAM. * Non-Transactional Database Only: This option disables the InnoDB storage engine completely and dedicates all server resources to the MyISAM storage engine. This option is recommended for users who do not use InnoDB. - The Configuration Wizard uses a template to generate the server - configuration file. The Database Usage dialog sets one of the - following option strings: + The Configuration Wizard uses a template to generate the + server configuration file. The Database Usage dialog sets one + of the following option strings: Multifunctional Database: MIXED Transactional Database Only: INNODB Non-Transactional Database Only: MYISAM @@ -1807,213 +2260,229 @@ resources dedicated to MyISAM. The remaining resources are allocated to InnoDB. -2.3.6.6. The InnoDB Tablespace Dialog +2.3.6.6 The InnoDB Tablespace Dialog - Some users may want to locate the InnoDB tablespace files in a - different location than the MySQL server data directory. Placing - the tablespace files in a separate location can be desirable if - your system has a higher capacity or higher performance storage - device available, such as a RAID storage system. - MySQL Server Instance Configuration Wizard: InnoDB Data Tablespace - - To change the default location for the InnoDB tablespace files, - choose a new drive from the drop-down list of drive letters and - choose a new path from the drop-down list of paths. To create a - custom path, click the ... button. - - If you are modifying the configuration of an existing server, you - must click the Modify button before you change the path. In this - situation you must move the existing tablespace files to the new - location manually before starting the server. + Some users may want to locate the InnoDB tablespace files in + a different location than the MySQL server data directory. + Placing the tablespace files in a separate location can be + desirable if your system has a higher capacity or higher + performance storage device available, such as a RAID storage + system. + MySQL Server Instance Configuration Wizard: InnoDB Data + Tablespace + + To change the default location for the InnoDB tablespace + files, choose a new drive from the drop-down list of drive + letters and choose a new path from the drop-down list of + paths. To create a custom path, click the ... button. + + If you are modifying the configuration of an existing server, + you must click the Modify button before you change the path. + In this situation you must move the existing tablespace files + to the new location manually before starting the server. -2.3.6.7. The Concurrent Connections Dialog +2.3.6.7 The Concurrent Connections Dialog To prevent the server from running out of resources, it is - important to limit the number of concurrent connections to the - MySQL server that can be established. The Concurrent Connections - dialog enables you to choose the expected usage of your server, - and sets the limit for concurrent connections accordingly. It is - also possible to set the concurrent connection limit manually. + important to limit the number of concurrent connections to + the MySQL server that can be established. The Concurrent + Connections dialog enables you to choose the expected usage + of your server, and sets the limit for concurrent connections + accordingly. It is also possible to set the concurrent + connection limit manually. MySQL Server Instance Configuration Wizard: Connections - * Decision Support (DSS)/OLAP: Choose this option if your server - does not require a large number of concurrent connections. The - maximum number of connections is set at 100, with an average - of 20 concurrent connections assumed. - - * Online Transaction Processing (OLTP): Choose this option if - your server requires a large number of concurrent connections. - The maximum number of connections is set at 500. - - * Manual Setting: Choose this option to set the maximum number - of concurrent connections to the server manually. Choose the - number of concurrent connections from the drop-down box - provided, or enter the maximum number of connections into the - drop-down box if the number you desire is not listed. + * Decision Support (DSS)/OLAP: Choose this option if your + server does not require a large number of concurrent + connections. The maximum number of connections is set at + 100, with an average of 20 concurrent connections + assumed. + + * Online Transaction Processing (OLTP): Choose this option + if your server requires a large number of concurrent + connections. The maximum number of connections is set at + 500. + + * Manual Setting: Choose this option to set the maximum + number of concurrent connections to the server manually. + Choose the number of concurrent connections from the + drop-down box provided, or enter the maximum number of + connections into the drop-down box if the number you + desire is not listed. -2.3.6.8. The Networking and Strict Mode Options Dialog +2.3.6.8 The Networking and Strict Mode Options Dialog Use the Networking Options dialog to enable or disable TCP/IP networking and to configure the port number that is used to connect to the MySQL server. - MySQL Server Instance Configuration Wizard: Network Configuration + MySQL Server Instance Configuration Wizard: Network + Configuration TCP/IP networking is enabled by default. To disable TCP/IP - networking, uncheck the box next to the Enable TCP/IP Networking - option. + networking, uncheck the box next to the Enable TCP/IP + Networking option. - Port 3306 is used by default. To change the port used to access - MySQL, choose a new port number from the drop-down box or type a - new port number directly into the drop-down box. If the port - number you choose is in use, you are prompted to confirm your - choice of port number. - - Set the Server SQL Mode to either enable or disable strict mode. - Enabling strict mode (default) makes MySQL behave more like other - database management systems. If you run applications that rely on - MySQL's old "forgiving" behavior, make sure to either adapt those - applications or to disable strict mode. For more information about - strict mode, see Section 5.1.7, "Server SQL Modes." + Port 3306 is used by default. To change the port used to + access MySQL, choose a new port number from the drop-down box + or type a new port number directly into the drop-down box. If + the port number you choose is in use, you are prompted to + confirm your choice of port number. + + Set the Server SQL Mode to either enable or disable strict + mode. Enabling strict mode (default) makes MySQL behave more + like other database management systems. If you run + applications that rely on MySQL's old "forgiving" behavior, + make sure to either adapt those applications or to disable + strict mode. For more information about strict mode, see + Section 5.1.7, "Server SQL Modes." -2.3.6.9. The Character Set Dialog +2.3.6.9 The Character Set Dialog The MySQL server supports multiple character sets and it is - possible to set a default server character set that is applied to - all tables, columns, and databases unless overridden. Use the - Character Set dialog to change the default character set of the - MySQL server. + possible to set a default server character set that is + applied to all tables, columns, and databases unless + overridden. Use the Character Set dialog to change the + default character set of the MySQL server. MySQL Server Instance Configuration Wizard: Character Set - * Standard Character Set: Choose this option if you want to use - latin1 as the default server character set. latin1 is used for - English and many Western European languages. - - * Best Support For Multilingualism: Choose this option if you - want to use utf8 as the default server character set. This is - a Unicode character set that can store characters from many - different languages. - - * Manual Selected Default Character Set / Collation: Choose this - option if you want to pick the server's default character set - manually. Choose the desired character set from the provided - drop-down list. + * Standard Character Set: Choose this option if you want to + use latin1 as the default server character set. latin1 is + used for English and many Western European languages. + + * Best Support For Multilingualism: Choose this option if + you want to use utf8 as the default server character set. + This is a Unicode character set that can store characters + from many different languages. + + * Manual Selected Default Character Set / Collation: Choose + this option if you want to pick the server's default + character set manually. Choose the desired character set + from the provided drop-down list. -2.3.6.10. The Service Options Dialog +2.3.6.10 The Service Options Dialog On Windows platforms, the MySQL server can be installed as a - Windows service. When installed this way, the MySQL server can be - started automatically during system startup, and even restarted - automatically by Windows in the event of a service failure. - - The MySQL Server Instance Configuration Wizard installs the MySQL - server as a service by default, using the service name MySQL. If - you do not wish to install the service, uncheck the box next to - the Install As Windows Service option. You can change the service - name by picking a new service name from the drop-down box provided - or by entering a new service name into the drop-down box. - Note - - Service names can include any legal character except forward (/) - or backward (\) slashes, and must be less than 256 characters - long. + Windows service. When installed this way, the MySQL server + can be started automatically during system startup, and even + restarted automatically by Windows in the event of a service + failure. + + The MySQL Server Instance Configuration Wizard installs the + MySQL server as a service by default, using the service name + MySQL. If you do not wish to install the service, uncheck the + box next to the Install As Windows Service option. You can + change the service name by picking a new service name from + the drop-down box provided or by entering a new service name + into the drop-down box. + Note + + Service names can include any legal character except forward + (/) or backward (\) slashes, and must be less than 256 + characters long. Warning - If you are installing multiple versions of MySQL onto the same - machine, you must choose a different service name for each version - that you install. If you do not choose a different service for - each installed version then the service manager information will - be inconsistent and this will cause problems when you try to - uninstall a previous version. - - If you have already installed multiple versions using the same - service name, you must manually edit the contents of the - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services parameters - within the Windows registry to update the association of the - service name with the correct server version. - - Typically, when installing multiple versions you create a service - name based on the version information. For example, you might - install MySQL 5.x as mysql5, or specific versions such as MySQL - 5.5.0 as mysql50500. - - To install the MySQL server as a service but not have it started - automatically at startup, uncheck the box next to the Launch the - MySQL Server Automatically option. - -2.3.6.11. The Security Options Dialog - - The content of the security options portion of the MySQL Server - Instance Configuration Wizard will depend on whether this is a new - installation, or modifying an existing installation. + If you are installing multiple versions of MySQL onto the + same machine, you must choose a different service name for + each version that you install. If you do not choose a + different service for each installed version then the service + manager information will be inconsistent and this will cause + problems when you try to uninstall a previous version. + + If you have already installed multiple versions using the + same service name, you must manually edit the contents of the + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services + parameters within the Windows registry to update the + association of the service name with the correct server + version. + + Typically, when installing multiple versions you create a + service name based on the version information. For example, + you might install MySQL 5.x as mysql5, or specific versions + such as MySQL 5.5.0 as mysql50500. + + To install the MySQL server as a service but not have it + started automatically at startup, uncheck the box next to the + Launch the MySQL Server Automatically option. + +2.3.6.11 The Security Options Dialog + + The content of the security options portion of the MySQL + Server Instance Configuration Wizard will depend on whether + this is a new installation, or modifying an existing + installation. * Setting the root password for a new installation - It is strongly recommended that you set a root password for - your MySQL server, and the MySQL Server Instance Config Wizard - requires by default that you do so. If you do not wish to set - a root password, uncheck the box next to the Modify Security - Settings option. + It is strongly recommended that you set a root password + for your MySQL server, and the MySQL Server Instance + Config Wizard requires by default that you do so. If you + do not wish to set a root password, uncheck the box next + to the Modify Security Settings option. MySQL Server Instance Config Wizard: Security - * To set the root password, enter the desired password into both - the New root password and Confirm boxes. + * To set the root password, enter the desired password into + both the New root password and Confirm boxes. Setting the root password for an existing installation If you are modifying the configuration of an existing - configuration, or you are installing an upgrade and the MySQL - Server Instance Configuration Wizard has detected an existing - MySQL system, then you must enter the existing password for - root before changing the configuration information. + configuration, or you are installing an upgrade and the + MySQL Server Instance Configuration Wizard has detected + an existing MySQL system, then you must enter the + existing password for root before changing the + configuration information. MySQL Server Instance Config Wizard: Security (Existing Installation) - If you want to change the current root password, enter the - desired new password into both the New root password and - Confirm boxes. - - To permit root logins from across the network, check the box next - to the Enable root access from remote machines option. This - decreases the security of your root account. - - To create an anonymous user account, check the box next to the - Create An Anonymous Account option. Creating an anonymous account - can decrease server security and cause login and permission - difficulties. For this reason, it is not recommended. - -2.3.6.12. The Confirmation Dialog - - The final dialog in the MySQL Server Instance Configuration Wizard - is the Confirmation Dialog. To start the configuration process, - click the Execute button. To return to a previous dialog, click - the Back button. To exit the MySQL Server Instance Configuration - Wizard without configuring the server, click the Cancel button. + If you want to change the current root password, enter + the desired new password into both the New root password + and Confirm boxes. + + To permit root logins from across the network, check the box + next to the Enable root access from remote machines option. + This decreases the security of your root account. + + To create an anonymous user account, check the box next to + the Create An Anonymous Account option. Creating an anonymous + account can decrease server security and cause login and + permission difficulties. For this reason, it is not + recommended. + +2.3.6.12 The Confirmation Dialog + + The final dialog in the MySQL Server Instance Configuration + Wizard is the Confirmation Dialog. To start the configuration + process, click the Execute button. To return to a previous + dialog, click the Back button. To exit the MySQL Server + Instance Configuration Wizard without configuring the server, + click the Cancel button. MySQL Server Instance Configuration Wizard: Confirmation After you click the Execute button, the MySQL Server Instance - Configuration Wizard performs a series of tasks and displays the - progress onscreen as the tasks are performed. + Configuration Wizard performs a series of tasks and displays + the progress onscreen as the tasks are performed. - The MySQL Server Instance Configuration Wizard first determines - configuration file options based on your choices using a template - prepared by MySQL developers and engineers. This template is named - my-template.ini and is located in your server installation - directory. - - The MySQL Configuration Wizard then writes these options to the - corresponding configuration file. - - If you chose to create a service for the MySQL server, the MySQL - Server Instance Configuration Wizard creates and starts the - service. If you are reconfiguring an existing service, the MySQL - Server Instance Configuration Wizard restarts the service to apply - your configuration changes. + The MySQL Server Instance Configuration Wizard first + determines configuration file options based on your choices + using a template prepared by MySQL developers and engineers. + This template is named my-template.ini and is located in your + server installation directory. + + The MySQL Configuration Wizard then writes these options to + the corresponding configuration file. + + If you chose to create a service for the MySQL server, the + MySQL Server Instance Configuration Wizard creates and starts + the service. If you are reconfiguring an existing service, + the MySQL Server Instance Configuration Wizard restarts the + service to apply your configuration changes. If you chose to set a root password, the MySQL Configuration - Wizard connects to the server, sets your new root password, and - applies any other security settings you may have selected. - - After the MySQL Server Instance Configuration Wizard has completed - its tasks, it displays a summary. Click the Finish button to exit - the MySQL Server Configuration Wizard. + Wizard connects to the server, sets your new root password, + and applies any other security settings you may have + selected. + + After the MySQL Server Instance Configuration Wizard has + completed its tasks, it displays a summary. Click the Finish + button to exit the MySQL Server Configuration Wizard. -2.3.6.13. MySQL Server Instance Config Wizard: Creating an Instance +2.3.6.13 MySQL Server Instance Config Wizard: Creating an Instance from the Command Line In addition to using the GUI interface to the MySQL Server @@ -2021,25 +2490,27 @@ automatically from the command line. To use the MySQL Server Instance Config Wizard on the command - line, you need to use the MySQLInstanceConfig.exe command that is - installed with MySQL in the bin directory within the installation - directory. MySQLInstanceConfig.exe takes a number of command-line - arguments the set the properties that would normally be selected - through the GUI interface, and then creates a new configuration - file (my.ini) by combining these selections with a template - configuration file to produce the working configuration file. + line, you need to use the MySQLInstanceConfig.exe command + that is installed with MySQL in the bin directory within the + installation directory. MySQLInstanceConfig.exe takes a + number of command-line arguments the set the properties that + would normally be selected through the GUI interface, and + then creates a new configuration file (my.ini) by combining + these selections with a template configuration file to + produce the working configuration file. + + The main command line options are provided in the table + below. Some of the options are required, while some options + are optional. - The main command line options are provided in the table below. - Some of the options are required, while some options are optional. - - Table 2.5. MySQL Server Instance Config Wizard Command Line + Table 2.5 MySQL Server Instance Config Wizard Command Line Options Option Description Required Parameters -nPRODUCTNAME The name of the instance when installed -pPATH Path of the base directory for installation. This is - equivalent to the directory when using the basedir configuration - parameter + equivalent to the directory when using the basedir + configuration parameter -vVERSION The version tag to use for this installation Action to Perform -i Install an instance @@ -2048,95 +2519,97 @@ -q Perform the operation quietly -lFILENAME Sae the installation progress in a logfile Config File to Use - -tFILENAME Path to the template config file that will be used to - generate the installed configuration file + -tFILENAME Path to the template config file that will be used + to generate the installed configuration file -cFILENAME Path to a config file to be generated The -t and -c options work together to set the configuration parameters for a new instance. The -t option specifies the - template configuration file to use as the basic configuration, - which are then merged with the configuration parameters generated - by the MySQL Server Instance Config Wizard into the configuration - file specified by the -c option. + template configuration file to use as the basic + configuration, which are then merged with the configuration + parameters generated by the MySQL Server Instance Config + Wizard into the configuration file specified by the -c + option. A sample template file, my-template.ini is provided in the - toplevel MySQL installation directory. The file contains elements - are replaced automatically by the MySQL Server Instance Config - Wizard during configuration. + toplevel MySQL installation directory. The file contains + elements are replaced automatically by the MySQL Server + Instance Config Wizard during configuration. If you specify a configuration file that already exists, the - existing configuration file will be saved in the file with the - original, with the date and time added. For example, the mysql.ini - will be copied to mysql 2009-10-27 1646.ini.bak. + existing configuration file will be saved in the file with + the original, with the date and time added. For example, the + mysql.ini will be copied to mysql 2009-10-27 1646.ini.bak. - The parameters that you can specify on the command line are listed - in the table below. + The parameters that you can specify on the command line are + listed in the table below. - Table 2.6. MySQL Server Instance Config Wizard Parameters + Table 2.6 MySQL Server Instance Config Wizard Parameters Parameter Description ServiceName=$ Specify the name of the service to be created AddBinToPath={yes | no} Specifies whether to add the binary directory of MySQL to the standard PATH environment variable - ServerType={DEVELOPMENT | SERVER | DEDICATED} Specify the server - type. For more information, see Section 2.3.6.4, "The Server Type - Dialog" + ServerType={DEVELOPMENT | SERVER | DEDICATED} Specify the + server type. For more information, see Section 2.3.6.4, "The + Server Type Dialog" DatabaseType={MIXED | INNODB | MYISAM} Specify the default - database type. For more information, see Section 2.3.6.5, "The - Database Usage Dialog" + database type. For more information, see Section 2.3.6.5, + "The Database Usage Dialog" ConnectionUsage={DSS | OLTP} Specify the type of connection - support, this automates the setting for the number of concurrent - connections (see the ConnectionCount parameter). For more - information, see Section 2.3.6.7, "The Concurrent Connections - Dialog" - ConnectionCount=# Specify the number of concurrent connections to - support. For more information, see Section 2.3.6.4, "The Server - Type Dialog" - SkipNetworking={yes | no} Specify whether network support should - be supported. Specifying yes disables network access altogether + support, this automates the setting for the number of + concurrent connections (see the ConnectionCount parameter). + For more information, see Section 2.3.6.7, "The Concurrent + Connections Dialog" + ConnectionCount=# Specify the number of concurrent + connections to support. For more information, see Section + 2.3.6.4, "The Server Type Dialog" + SkipNetworking={yes | no} Specify whether network support + should be supported. Specifying yes disables network access + altogether Port=# Specify the network port number to use for network connections. For more information, see Section 2.3.6.8, "The Networking and Strict Mode Options Dialog" - StrictMode={yes | no} Specify whether to use the strict SQL mode. - For more information, see Section 2.3.6.8, "The Networking and - Strict Mode Options Dialog" - Charset=$ Specify the default character set. For more information, - see Section 2.3.6.9, "The Character Set Dialog" + StrictMode={yes | no} Specify whether to use the strict SQL + mode. For more information, see Section 2.3.6.8, "The + Networking and Strict Mode Options Dialog" + Charset=$ Specify the default character set. For more + information, see Section 2.3.6.9, "The Character Set Dialog" RootPassword=$ Specify the root password RootCurrentPassword=$ Specify the current root password then stopping or reconfiguring an existing service Note - When specifying options on the command line, you can enclose the - entire command-line option and the value you are specifying using - double quotation marks. This enables you to use spaces in the - options. For example, "-cC:\mysql.ini". - - The following command installs a MySQL Server 5.5 instance from - the directory C:\Program Files\MySQL\MySQL Server 5.5 using the - service name MySQL55 and setting the root password to 1234. + When specifying options on the command line, you can enclose + the entire command-line option and the value you are + specifying using double quotation marks. This enables you to + use spaces in the options. For example, "-cC:\mysql.ini". + + The following command installs a MySQL Server 5.5 instance + from the directory C:\Program Files\MySQL\MySQL Server 5.5 + using the service name MySQL55 and setting the root password + to 1234. shell> MySQLInstanceConfig.exe -i -q "-lC:\mysql_install_log.txt" » - "-nMySQL Server 5.5" "-pC:\Program Files\MySQL\MySQL Server 5.5" - -v5.5.36 » - "-tmy-template.ini" "-cC:\mytest.ini" ServerType=DEVELOPMENT Datab -aseType=MIXED » - ConnectionUsage=DSS Port=3311 ServiceName=MySQL55 RootPassword=123 -4 + "-nMySQL Server 5.5" "-pC:\Program Files\MySQL\MySQL Server 5.5" -v +5.5.44 » + "-tmy-template.ini" "-cC:\mytest.ini" ServerType=DEVELOPMENT Databa +seType=MIXED » + ConnectionUsage=DSS Port=3311 ServiceName=MySQL55 RootPassword=1234 In the above example, a log file will be generated in mysql_install_log.txt containing the information about the - instance creation process. The log file generated by the above - example is shown below: + instance creation process. The log file generated by the + above example is shown below: Welcome to the MySQL Server Instance Configuration Wizard 1.0.16.0 Date: 2009-10-27 17:07:21 Installing service ... Product Name: MySQL Server 5.5 -Version: 5.5.36 +Version: 5.5.44 Installation Path: C:\Program Files\MySQL\MySQL Server 5.5\ -Creating configuration file C:\mytest.ini using template my-template. -ini. +Creating configuration file C:\mytest.ini using template my-template.i +ni. Options: DEVELOPMENT MIXED @@ -2152,14 +2625,16 @@ Creating Windows service entry. Service name: "MySQL55" -Parameters: "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld" -- -defaults-file="C:\mytest.ini" MySQL55. +Parameters: "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld" --d +efaults-file="C:\mytest.ini" MySQL55. Windows service MySQL55 installed. - When using the command line, the return values in the following - table indicate an error performing the specified option. + When using the command line, the return values in the + following table indicate an error performing the specified + option. - Table 2.7. Return Value from MySQL Server Instance Config Wizard + Table 2.7 Return Value from MySQL Server Instance Config + Wizard Value Description 2 Configuration template file cannot be found 3 The Windows service entry cannot be created @@ -2170,17 +2645,18 @@ 8 The configuration file cannot be written 9 The Windows service entry cannot be removed - You can perform an installation of MySQL automatically using the - MSI package. For more information, see Section 2.3.5.2, - "Automating MySQL Installation on Microsoft Windows Using the MSI - Package." + You can perform an installation of MySQL automatically using + the MSI package. For more information, see Section 2.3.5.2, + "Automating MySQL Installation on Microsoft Windows Using the + MSI Package." -2.3.7. Installing MySQL on Microsoft Windows Using a noinstall Zip +2.3.7 Installing MySQL on Microsoft Windows Using a noinstall Zip Archive - Users who are installing from the noinstall package can use the - instructions in this section to manually install MySQL. The - process for installing MySQL from a Zip archive is as follows: + Users who are installing from the noinstall package can use + the instructions in this section to manually install MySQL. + The process for installing MySQL from a Zip archive is as + follows: 1. Extract the archive to the desired install directory @@ -2194,195 +2670,208 @@ This process is described in the sections that follow. -2.3.7.1. Extracting the Install Archive +2.3.7.1 Extracting the Install Archive To install MySQL manually, do the following: - 1. If you are upgrading from a previous version please refer to - Section 2.3.9, "Upgrading MySQL on Windows," before beginning - the upgrade process. + 1. If you are upgrading from a previous version please refer + to Section 2.3.9, "Upgrading MySQL on Windows," before + beginning the upgrade process. - 2. Make sure that you are logged in as a user with administrator - privileges. + 2. Make sure that you are logged in as a user with + administrator privileges. 3. Choose an installation location. Traditionally, the MySQL - server is installed in C:\mysql. The MySQL Installation Wizard - installs MySQL under C:\Program Files\MySQL. If you do not - install MySQL at C:\mysql, you must specify the path to the - install directory during startup or in an option file. See - Section 2.3.7.2, "Creating an Option File." + server is installed in C:\mysql. The MySQL Installation + Wizard installs MySQL under C:\Program Files\MySQL. If + you do not install MySQL at C:\mysql, you must specify + the path to the install directory during startup or in an + option file. See Section 2.3.7.2, "Creating an Option + File." + Note + The MySQL Installer installs MySQL under C:\Program + Files\MySQL. 4. Extract the install archive to the chosen installation - location using your preferred Zip archive tool. Some tools may - extract the archive to a folder within your chosen - installation location. If this occurs, you can move the - contents of the subfolder into the chosen installation - location. - -2.3.7.2. Creating an Option File - - If you need to specify startup options when you run the server, - you can indicate them on the command line or place them in an - option file. For options that are used every time the server - starts, you may find it most convenient to use an option file to - specify your MySQL configuration. This is particularly true under - the following circumstances: - - * The installation or data directory locations are different - from the default locations (C:\Program Files\MySQL\MySQL - Server 5.5 and C:\Program Files\MySQL\MySQL Server 5.5\data). - - * You need to tune the server settings, such as memory, cache, - or InnoDB configuration information. - - When the MySQL server starts on Windows, it looks for option files - in several locations, such as the Windows directory, C:\, and the - MySQL installation directory (for the full list of locations, see - Section 4.2.3.3, "Using Option Files"). The Windows directory - typically is named something like C:\WINDOWS. You can determine - its exact location from the value of the WINDIR environment - variable using the following command: + location using your preferred Zip archive tool. Some + tools may extract the archive to a folder within your + chosen installation location. If this occurs, you can + move the contents of the subfolder into the chosen + installation location. + +2.3.7.2 Creating an Option File + + If you need to specify startup options when you run the + server, you can indicate them on the command line or place + them in an option file. For options that are used every time + the server starts, you may find it most convenient to use an + option file to specify your MySQL configuration. This is + particularly true under the following circumstances: + + * The installation or data directory locations are + different from the default locations (C:\Program + Files\MySQL\MySQL Server 5.5 and C:\Program + Files\MySQL\MySQL Server 5.5\data). + + * You need to tune the server settings, such as memory, + cache, or InnoDB configuration information. + + When the MySQL server starts on Windows, it looks for option + files in several locations, such as the Windows directory, + C:\, and the MySQL installation directory (for the full list + of locations, see Section 4.2.6, "Using Option Files"). The + Windows directory typically is named something like + C:\WINDOWS. You can determine its exact location from the + value of the WINDIR environment variable using the following + command: C:\> echo %WINDIR% - MySQL looks for options in each location first in the my.ini file, - and then in the my.cnf file. However, to avoid confusion, it is - best if you use only one file. If your PC uses a boot loader where - C: is not the boot drive, your only option is to use the my.ini - file. Whichever option file you use, it must be a plain text file. - Note - - When using the MySQL Installer to install MySQL Server, it will - create the my.ini at the default location. And as of MySQL Server - 5.5.27, the user running MySQL Installer is granted full - permissions to this new my.ini. - - In other words, be sure that the MySQL Server user has permission - to read the my.ini file. - - You can also make use of the example option files included with - your MySQL distribution; see Section 5.1.2, "Server Configuration - Defaults." - - An option file can be created and modified with any text editor, - such as Notepad. For example, if MySQL is installed in E:\mysql - and the data directory is in E:\mydata\data, you can create an - option file containing a [mysqld] section to specify values for - the basedir and datadir options: + MySQL looks for options in each location first in the my.ini + file, and then in the my.cnf file. However, to avoid + confusion, it is best if you use only one file. If your PC + uses a boot loader where C: is not the boot drive, your only + option is to use the my.ini file. Whichever option file you + use, it must be a plain text file. + Note + + When using the MySQL Installer to install MySQL Server, it + will create the my.ini at the default location. And as of + MySQL Server 5.5.27, the user running MySQL Installer is + granted full permissions to this new my.ini. + + In other words, be sure that the MySQL Server user has + permission to read the my.ini file. + + You can also make use of the example option files included + with your MySQL distribution; see Section 5.1.2, "Server + Configuration Defaults." + + An option file can be created and modified with any text + editor, such as Notepad. For example, if MySQL is installed + in E:\mysql and the data directory is in E:\mydata\data, you + can create an option file containing a [mysqld] section to + specify values for the basedir and datadir options: [mysqld] # set basedir to your installation path basedir=E:/mysql # set datadir to the location of your data directory datadir=E:/mydata/data - Note that Windows path names are specified in option files using - (forward) slashes rather than backslashes. If you do use - backslashes, double them: + Microsoft Windows path names are specified in option files + using (forward) slashes rather than backslashes. If you do + use backslashes, double them: [mysqld] # set basedir to your installation path basedir=E:\\mysql # set datadir to the location of your data directory datadir=E:\\mydata\\data - The rules for use of backslash in option file values are given in - Section 4.2.3.3, "Using Option Files." + The rules for use of backslash in option file values are + given in Section 4.2.6, "Using Option Files." - The data directory is located within the AppData directory for the - user running MySQL. + The data directory is located within the AppData directory + for the user running MySQL. - If you would like to use a data directory in a different location, - you should copy the entire contents of the data directory to the - new location. For example, if you want to use E:\mydata as the - data directory instead, you must do two things: - - 1. Move the entire data directory and all of its contents from - the default location (for example C:\Program Files\MySQL\MySQL - Server 5.5\data) to E:\mydata. + If you would like to use a data directory in a different + location, you should copy the entire contents of the data + directory to the new location. For example, if you want to + use E:\mydata as the data directory instead, you must do two + things: + + 1. Move the entire data directory and all of its contents + from the default location (for example C:\Program + Files\MySQL\MySQL Server 5.5\data) to E:\mydata. 2. Use a --datadir option to specify the new data directory location each time you start the server. -2.3.7.3. Selecting a MySQL Server Type +2.3.7.3 Selecting a MySQL Server Type - The following table shows the available servers for Windows in - MySQL 5.5. + The following table shows the available servers for Windows + in MySQL 5.5. Binary Description mysqld Optimized binary with named-pipe support - mysqld-debug Like mysqld, but compiled with full debugging and - automatic memory allocation checking + mysqld-debug Like mysqld, but compiled with full debugging + and automatic memory allocation checking All of the preceding binaries are optimized for modern Intel processors, but should work on any Intel i386-class or higher processor. Each of the servers in a distribution support the same set of - storage engines. The SHOW ENGINES statement displays which engines - a given server supports. + storage engines. The SHOW ENGINES statement displays which + engines a given server supports. - All Windows MySQL 5.5 servers have support for symbolic linking of - database directories. + All Windows MySQL 5.5 servers have support for symbolic + linking of database directories. - MySQL supports TCP/IP on all Windows platforms. MySQL servers on - Windows support named pipes as indicated in the following list. - However, the default is to use TCP/IP regardless of platform. - (Named pipes are slower than TCP/IP in many Windows - configurations.) - - Named pipes are enabled only if you start the server with the - --enable-named-pipe option. It is necessary to use this option - explicitly because some users have experienced problems with - shutting down the MySQL server when named pipes were used. + MySQL supports TCP/IP on all Windows platforms. MySQL servers + on Windows also support named pipes, if you start the server + with the --enable-named-pipe option. It is necessary to use + this option explicitly because some users have experienced + problems with shutting down the MySQL server when named pipes + were used. The default is to use TCP/IP regardless of + platform because named pipes are slower than TCP/IP in many + Windows configurations. -2.3.7.4. Starting the Server for the First Time +2.3.7.4 Starting the Server for the First Time This section gives a general overview of starting the MySQL - server. The following sections provide more specific information - for starting the MySQL server from the command line or as a - Windows service. + server. The following sections provide more specific + information for starting the MySQL server from the command + line or as a Windows service. The information here applies primarily if you installed MySQL - using the Noinstall version, or if you wish to configure and test - MySQL manually rather than with the GUI tools. + using the Noinstall version, or if you wish to configure and + test MySQL manually rather than with the GUI tools. + Note + + The MySQL server will automatically start after using the + MySQL Installer, and the MySQL Notifier GUI can be used to + start/stop/restart at any time. The examples in these sections assume that MySQL is installed - under the default location of C:\Program Files\MySQL\MySQL Server - 5.5. Adjust the path names shown in the examples if you have MySQL - installed in a different location. - - Clients have two options. They can use TCP/IP, or they can use a - named pipe if the server supports named-pipe connections. - - MySQL for Windows also supports shared-memory connections if the - server is started with the --shared-memory option. Clients can - connect through shared memory by using the --protocol=MEMORY - option. + under the default location of C:\Program Files\MySQL\MySQL + Server 5.5. Adjust the path names shown in the examples if + you have MySQL installed in a different location. + + Clients have two options. They can use TCP/IP, or they can + use a named pipe if the server supports named-pipe + connections. + + MySQL for Windows also supports shared-memory connections if + the server is started with the --shared-memory option. + Clients can connect through shared memory by using the + --protocol=MEMORY option. For information about which server binary to run, see Section 2.3.7.3, "Selecting a MySQL Server Type." - Testing is best done from a command prompt in a console window (or - "DOS window"). In this way you can have the server display status - messages in the window where they are easy to see. If something is - wrong with your configuration, these messages make it easier for - you to identify and fix any problems. + Testing is best done from a command prompt in a console + window (or "DOS window"). In this way you can have the server + display status messages in the window where they are easy to + see. If something is wrong with your configuration, these + messages make it easier for you to identify and fix any + problems. To start the server, enter this command: C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld" --console For a server that includes InnoDB support, you should see the - messages similar to those following as it starts (the path names - and sizes may differ): + messages similar to those following as it starts (the path + names and sizes may differ): InnoDB: The first specified datafile c:\ibdata\ibdata1 did not exist: InnoDB: a new database to be created! InnoDB: Setting file c:\ibdata\ibdata1 size to 209715200 InnoDB: Database physically writes the file full: wait... -InnoDB: Log file c:\iblogs\ib_logfile0 did not exist: new to be creat -ed +InnoDB: Log file c:\iblogs\ib_logfile0 did not exist: new to be create +d InnoDB: Setting log file c:\iblogs\ib_logfile0 size to 31457280 -InnoDB: Log file c:\iblogs\ib_logfile1 did not exist: new to be creat -ed +InnoDB: Log file c:\iblogs\ib_logfile1 did not exist: new to be create +d InnoDB: Setting log file c:\iblogs\ib_logfile1 size to 31457280 -InnoDB: Log file c:\iblogs\ib_logfile2 did not exist: new to be creat -ed +InnoDB: Log file c:\iblogs\ib_logfile2 did not exist: new to be create +d InnoDB: Setting log file c:\iblogs\ib_logfile2 size to 31457280 InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created @@ -2391,151 +2880,170 @@ 011024 10:58:25 InnoDB: Started When the server finishes its startup sequence, you should see - something like this, which indicates that the server is ready to - service client connections: + something like this, which indicates that the server is ready + to service client connections: mysqld: ready for connections -Version: '5.5.36' socket: '' port: 3306 +Version: '5.5.44' socket: '' port: 3306 The server continues to write to the console any further - diagnostic output it produces. You can open a new console window - in which to run client programs. + diagnostic output it produces. You can open a new console + window in which to run client programs. - If you omit the --console option, the server writes diagnostic - output to the error log in the data directory (C:\Program - Files\MySQL\MySQL Server 5.5\data by default). The error log is - the file with the .err extension, or may be specified by passing - in the --log-error option. + If you omit the --console option, the server writes + diagnostic output to the error log in the data directory + (C:\Program Files\MySQL\MySQL Server 5.5\data by default). + The error log is the file with the .err extension, and may be + set using the --log-error option. Note - The accounts that are listed in the MySQL grant tables initially - have no passwords. After starting the server, you should set up - passwords for them using the instructions in Section 2.11.2, - "Securing the Initial MySQL Accounts." + The accounts that are listed in the MySQL grant tables + initially have no passwords. After starting the server, you + should set up passwords for them using the instructions in + Section 2.10.2, "Securing the Initial MySQL Accounts." -2.3.7.5. Starting MySQL from the Windows Command Line +2.3.7.5 Starting MySQL from the Windows Command Line - The MySQL server can be started manually from the command line. - This can be done on any version of Windows. + The MySQL server can be started manually from the command + line. This can be done on any version of Windows. + Note + + The MySQL Notifier GUI can also be used to start/stop/restart + the MySQL server. - To start the mysqld server from the command line, you should start - a console window (or "DOS window") and enter this command: + To start the mysqld server from the command line, you should + start a console window (or "DOS window") and enter this + command: C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld" - The path to mysqld may vary depending on the install location of - MySQL on your system. + The path to mysqld may vary depending on the install location + of MySQL on your system. You can stop the MySQL server by executing this command: C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqladmin" -u root - shutdown +shutdown Note - If the MySQL root user account has a password, you need to invoke - mysqladmin with the -p option and supply the password when - prompted. - - This command invokes the MySQL administrative utility mysqladmin - to connect to the server and tell it to shut down. The command - connects as the MySQL root user, which is the default - administrative account in the MySQL grant system. Note that users - in the MySQL grant system are wholly independent from any login - users under Windows. - - If mysqld doesn't start, check the error log to see whether the - server wrote any messages there to indicate the cause of the - problem. By default, the error log is located in the C:\Program - Files\MySQL\MySQL Server 5.5\data directory. It is the file with a - suffix of .err, or may be specified by passing in the --log-error - option. Alternatively, you can try to start the server as mysqld - --console; in this case, you may get some useful information on - the screen that may help solve the problem. + If the MySQL root user account has a password, you need to + invoke mysqladmin with the -p option and supply the password + when prompted. + + This command invokes the MySQL administrative utility + mysqladmin to connect to the server and tell it to shut down. + The command connects as the MySQL root user, which is the + default administrative account in the MySQL grant system. + Note + + Users in the MySQL grant system are wholly independent from + any login users under Microsoft Windows. + + If mysqld doesn't start, check the error log to see whether + the server wrote any messages there to indicate the cause of + the problem. By default, the error log is located in the + C:\Program Files\MySQL\MySQL Server 5.5\data directory. It is + the file with a suffix of .err, or may be specified by + passing in the --log-error option. Alternatively, you can try + to start the server with the --console option; in this case, + the server may display some useful information on the screen + that will help solve the problem. The last option is to start mysqld with the --standalone and --debug options. In this case, mysqld writes a log file - C:\mysqld.trace that should contain the reason why mysqld doesn't - start. See Section 23.4.3, "The DBUG Package." + C:\mysqld.trace that should contain the reason why mysqld + doesn't start. See Section 24.4.3, "The DBUG Package." - Use mysqld --verbose --help to display all the options that mysqld - supports. + Use mysqld --verbose --help to display all the options that + mysqld supports. -2.3.7.6. Customizing the PATH for MySQL Tools +2.3.7.6 Customizing the PATH for MySQL Tools - To make it easier to invoke MySQL programs, you can add the path - name of the MySQL bin directory to your Windows system PATH - environment variable: + To make it easier to invoke MySQL programs, you can add the + path name of the MySQL bin directory to your Windows system + PATH environment variable: - * On the Windows desktop, right-click the My Computer icon, and - select Properties. + * On the Windows desktop, right-click the My Computer icon, + and select Properties. - * Next select the Advanced tab from the System Properties menu - that appears, and click the Environment Variables button. + * Next select the Advanced tab from the System Properties + menu that appears, and click the Environment Variables + button. - * Under System Variables, select Path, and then click the Edit - button. The Edit System Variable dialogue should appear. + * Under System Variables, select Path, and then click the + Edit button. The Edit System Variable dialogue should + appear. * Place your cursor at the end of the text appearing in the - space marked Variable Value. (Use the End key to ensure that - your cursor is positioned at the very end of the text in this - space.) Then enter the complete path name of your MySQL bin - directory (for example, C:\Program Files\MySQL\MySQL Server - 5.5\bin) + space marked Variable Value. (Use the End key to ensure + that your cursor is positioned at the very end of the + text in this space.) Then enter the complete path name of + your MySQL bin directory (for example, C:\Program + Files\MySQL\MySQL Server 5.5\bin) Note - There must be a semicolon separating this path from any values - present in this field. - Dismiss this dialogue, and each dialogue in turn, by clicking - OK until all of the dialogues that were opened have been - dismissed. You should now be able to invoke any MySQL - executable program by typing its name at the DOS prompt from - any directory on the system, without having to supply the - path. This includes the servers, the mysql client, and all - MySQL command-line utilities such as mysqladmin and mysqldump. - You should not add the MySQL bin directory to your Windows - PATH if you are running multiple MySQL servers on the same - machine. + There must be a semicolon separating this path from any + values present in this field. + Dismiss this dialogue, and each dialogue in turn, by + clicking OK until all of the dialogues that were opened + have been dismissed. You should now be able to invoke any + MySQL executable program by typing its name at the DOS + prompt from any directory on the system, without having + to supply the path. This includes the servers, the mysql + client, and all MySQL command-line utilities such as + mysqladmin and mysqldump. + You should not add the MySQL bin directory to your + Windows PATH if you are running multiple MySQL servers on + the same machine. Warning You must exercise great care when editing your system PATH by - hand; accidental deletion or modification of any portion of the - existing PATH value can leave you with a malfunctioning or even - unusable system. - -2.3.7.7. Starting MySQL as a Windows Service - - On Windows, the recommended way to run MySQL is to install it as a - Windows service, so that MySQL starts and stops automatically when - Windows starts and stops. A MySQL server installed as a service - can also be controlled from the command line using NET commands, - or with the graphical Services utility. Generally, to install - MySQL as a Windows service you should be logged in using an - account that has administrator rights. - - The Services utility (the Windows Service Control Manager) can be - found in the Windows Control Panel (under Administrative Tools on - Windows 2000, XP, Vista, and Server 2003). To avoid conflicts, it - is advisable to close the Services utility while performing server - installation or removal operations from the command line. + hand; accidental deletion or modification of any portion of + the existing PATH value can leave you with a malfunctioning + or even unusable system. + +2.3.7.7 Starting MySQL as a Windows Service + + On Windows, the recommended way to run MySQL is to install it + as a Windows service, so that MySQL starts and stops + automatically when Windows starts and stops. A MySQL server + installed as a service can also be controlled from the + command line using NET commands, or with the graphical + Services utility. Generally, to install MySQL as a Windows + service you should be logged in using an account that has + administrator rights. + Note + + The MySQL Notifier GUI can also be used to monitor the status + of the MySQL service. + + The Services utility (the Windows Service Control Manager) + can be found in the Windows Control Panel (under + Administrative Tools on Windows 2000, XP, Vista, and Server + 2003). To avoid conflicts, it is advisable to close the + Services utility while performing server installation or + removal operations from the command line. Installing the service - Before installing MySQL as a Windows service, you should first - stop the current server if it is running by using the following - command: + Before installing MySQL as a Windows service, you should + first stop the current server if it is running by using the + following command: C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqladmin" -u root shutdown Note - If the MySQL root user account has a password, you need to invoke - mysqladmin with the -p option and supply the password when - prompted. - - This command invokes the MySQL administrative utility mysqladmin - to connect to the server and tell it to shut down. The command - connects as the MySQL root user, which is the default - administrative account in the MySQL grant system. Note that users - in the MySQL grant system are wholly independent from any login - users under Windows. + If the MySQL root user account has a password, you need to + invoke mysqladmin with the -p option and supply the password + when prompted. + + This command invokes the MySQL administrative utility + mysqladmin to connect to the server and tell it to shut down. + The command connects as the MySQL root user, which is the + default administrative account in the MySQL grant system. + Note + + Users in the MySQL grant system are wholly independent from + any login users under Windows. Install the server as a service using this command: C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld" --install @@ -2543,381 +3051,451 @@ The service-installation command does not start the server. Instructions for that are given later in this section. - To make it easier to invoke MySQL programs, you can add the path - name of the MySQL bin directory to your Windows system PATH - environment variable: - - * On the Windows desktop, right-click the My Computer icon, and - select Properties. - - * Next select the Advanced tab from the System Properties menu - that appears, and click the Environment Variables button. - - * Under System Variables, select Path, and then click the Edit - button. The Edit System Variable dialogue should appear. + To make it easier to invoke MySQL programs, you can add the + path name of the MySQL bin directory to your Windows system + PATH environment variable: + + * On the Windows desktop, right-click the My Computer icon, + and select Properties. + + * Next select the Advanced tab from the System Properties + menu that appears, and click the Environment Variables + button. + + * Under System Variables, select Path, and then click the + Edit button. The Edit System Variable dialogue should + appear. * Place your cursor at the end of the text appearing in the - space marked Variable Value. (Use the End key to ensure that - your cursor is positioned at the very end of the text in this - space.) Then enter the complete path name of your MySQL bin - directory (for example, C:\Program Files\MySQL\MySQL Server - 5.5\bin), Note that there should be a semicolon separating - this path from any values present in this field. Dismiss this - dialogue, and each dialogue in turn, by clicking OK until all - of the dialogues that were opened have been dismissed. You - should now be able to invoke any MySQL executable program by - typing its name at the DOS prompt from any directory on the - system, without having to supply the path. This includes the - servers, the mysql client, and all MySQL command-line - utilities such as mysqladmin and mysqldump. - You should not add the MySQL bin directory to your Windows - PATH if you are running multiple MySQL servers on the same - machine. + space marked Variable Value. (Use the End key to ensure + that your cursor is positioned at the very end of the + text in this space.) Then enter the complete path name of + your MySQL bin directory (for example, C:\Program + Files\MySQL\MySQL Server 5.5\bin), and there should be a + semicolon separating this path from any values present in + this field. Dismiss this dialogue, and each dialogue in + turn, by clicking OK until all of the dialogues that were + opened have been dismissed. You should now be able to + invoke any MySQL executable program by typing its name at + the DOS prompt from any directory on the system, without + having to supply the path. This includes the servers, the + mysql client, and all MySQL command-line utilities such + as mysqladmin and mysqldump. + You should not add the MySQL bin directory to your + Windows PATH if you are running multiple MySQL servers on + the same machine. Warning You must exercise great care when editing your system PATH by - hand; accidental deletion or modification of any portion of the - existing PATH value can leave you with a malfunctioning or even - unusable system. + hand; accidental deletion or modification of any portion of + the existing PATH value can leave you with a malfunctioning + or even unusable system. - The following additional arguments can be used when installing the - service: + The following additional arguments can be used when + installing the service: * You can specify a service name immediately following the --install option. The default service name is MySQL. - * If a service name is given, it can be followed by a single - option. By convention, this should be - --defaults-file=file_name to specify the name of an option - file from which the server should read options when it starts. + * If a service name is given, it can be followed by a + single option. By convention, this should be + --defaults-file=file_name to specify the name of an + option file from which the server should read options + when it starts. The use of a single option other than --defaults-file is - possible but discouraged. --defaults-file is more flexible - because it enables you to specify multiple startup options for - the server by placing them in the named option file. + possible but discouraged. --defaults-file is more + flexible because it enables you to specify multiple + startup options for the server by placing them in the + named option file. - * You can also specify a --local-service option following the - service name. This causes the server to run using the + * You can also specify a --local-service option following + the service name. This causes the server to run using the LocalService Windows account that has limited system - privileges. This account is available only for Windows XP or - newer. If both --defaults-file and --local-service are given - following the service name, they can be in any order. - - For a MySQL server that is installed as a Windows service, the - following rules determine the service name and option files that - the server uses: - - * If the service-installation command specifies no service name - or the default service name (MySQL) following the --install - option, the server uses the a service name of MySQL and reads - options from the [mysqld] group in the standard option files. - - * If the service-installation command specifies a service name - other than MySQL following the --install option, the server - uses that service name. It reads options from the [mysqld] - group and the group that has the same name as the service in - the standard option files. This enables you to use the - [mysqld] group for options that should be used by all MySQL - services, and an option group with the service name for use by - the server installed with that service name. + privileges. This account is available only for Windows XP + or newer. If both --defaults-file and --local-service are + given following the service name, they can be in any + order. + + For a MySQL server that is installed as a Windows service, + the following rules determine the service name and option + files that the server uses: + + * If the service-installation command specifies no service + name or the default service name (MySQL) following the + --install option, the server uses the a service name of + MySQL and reads options from the [mysqld] group in the + standard option files. + + * If the service-installation command specifies a service + name other than MySQL following the --install option, the + server uses that service name. It reads options from the + [mysqld] group and the group that has the same name as + the service in the standard option files. This enables + you to use the [mysqld] group for options that should be + used by all MySQL services, and an option group with the + service name for use by the server installed with that + service name. * If the service-installation command specifies a --defaults-file option after the service name, the server - reads options the same way as described in the previous item, - except that it reads options only from the the named file and - ignores the standard option files. + reads options the same way as described in the previous + item, except that it reads options only from the named + file and ignores the standard option files. As a more complex example, consider the following command: C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld" --install MySQL --defaults-file=C:\my-opts.cnf Here, the default service name (MySQL) is given after the - --install option. If no --defaults-file option had been given, - this command would have the effect of causing the server to read - the [mysqld] group from the standard option files. However, - because the --defaults-file option is present, the server reads - options from the [mysqld] option group, and only from the named - file. + --install option. If no --defaults-file option had been + given, this command would have the effect of causing the + server to read the [mysqld] group from the standard option + files. However, because the --defaults-file option is + present, the server reads options from the [mysqld] option + group, and only from the named file. Note - On Windows, if the server is started with the --defaults-file and - --install options, --install must be first. Otherwise, mysqld.exe - will attempt to start the MySQL server. + On Windows, if the server is started with the --defaults-file + and --install options, --install must be first. Otherwise, + mysqld.exe will attempt to start the MySQL server. - You can also specify options as Start parameters in the Windows - Services utility before you start the MySQL service. + You can also specify options as Start parameters in the + Windows Services utility before you start the MySQL service. Starting the service Once a MySQL server has been installed as a service, Windows starts the service automatically whenever Windows starts. The - service also can be started immediately from the Services utility, - or by using a NET START MySQL command. The NET command is not case - sensitive. - - When run as a service, mysqld has no access to a console window, - so no messages can be seen there. If mysqld does not start, check - the error log to see whether the server wrote any messages there - to indicate the cause of the problem. The error log is located in - the MySQL data directory (for example, C:\Program - Files\MySQL\MySQL Server 5.5\data). It is the file with a suffix - of .err. + service also can be started immediately from the Services + utility, or by using a NET START MySQL command. The NET + command is not case sensitive. + + When run as a service, mysqld has no access to a console + window, so no messages can be seen there. If mysqld does not + start, check the error log to see whether the server wrote + any messages there to indicate the cause of the problem. The + error log is located in the MySQL data directory (for + example, C:\Program Files\MySQL\MySQL Server 5.5\data). It is + the file with a suffix of .err. When a MySQL server has been installed as a service, and the - service is running, Windows stops the service automatically when - Windows shuts down. The server also can be stopped manually by - using the Services utility, the NET STOP MySQL command, or the - mysqladmin shutdown command. + service is running, Windows stops the service automatically + when Windows shuts down. The server also can be stopped + manually by using the Services utility, the NET STOP MySQL + command, or the mysqladmin shutdown command. You also have the choice of installing the server as a manual service if you do not wish for the service to be started automatically during the boot process. To do this, use the --install-manual option rather than the --install option: -C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld" --install-m -anual +C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld" --install-ma +nual Removing the service - To remove a server that is installed as a service, first stop it - if it is running by executing NET STOP MySQL. Then use the + To remove a server that is installed as a service, first stop + it if it is running by executing NET STOP MySQL. Then use the --remove option to remove it: C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld" --remove - If mysqld is not running as a service, you can start it from the - command line. For instructions, see Section 2.3.7.5, "Starting - MySQL from the Windows Command Line." + If mysqld is not running as a service, you can start it from + the command line. For instructions, see Section 2.3.7.5, + "Starting MySQL from the Windows Command Line." + + If you encounter difficulties during installation. see + Section 2.3.8, "Troubleshooting a Microsoft Windows MySQL + Server Installation." - Please see Section 2.3.8, "Troubleshooting a Microsoft Windows - MySQL Server Installation," if you encounter difficulties during - installation. - -2.3.7.8. Testing The MySQL Installation +2.3.7.8 Testing The MySQL Installation - You can test whether the MySQL server is working by executing any - of the following commands: + You can test whether the MySQL server is working by executing + any of the following commands: C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqlshow" -C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqlshow" -u root -mysql +C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqlshow" -u root m +ysql C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqladmin" version - status proc +status proc C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysql" test - If mysqld is slow to respond to TCP/IP connections from client - programs, there is probably a problem with your DNS. In this case, - start mysqld with the --skip-name-resolve option and use only - localhost and IP addresses in the Host column of the MySQL grant - tables. - - You can force a MySQL client to use a named-pipe connection rather - than TCP/IP by specifying the --pipe or --protocol=PIPE option, or - by specifying . (period) as the host name. Use the --socket option - to specify the name of the pipe if you do not want to use the - default pipe name. - - Note that if you have set a password for the root account, deleted - the anonymous account, or created a new user account, then you - must use the appropriate -u and -p options with the commands shown - above to connect with the MySQL Server. See Section 4.2.2, - "Connecting to the MySQL Server." + If mysqld is slow to respond to TCP/IP connections from + client programs, there is probably a problem with your DNS. + In this case, start mysqld with the --skip-name-resolve + option and use only localhost and IP addresses in the Host + column of the MySQL grant tables. + + You can force a MySQL client to use a named-pipe connection + rather than TCP/IP by specifying the --pipe or + --protocol=PIPE option, or by specifying . (period) as the + host name. Use the --socket option to specify the name of the + pipe if you do not want to use the default pipe name. + + If you have set a password for the root account, deleted the + anonymous account, or created a new user account, then to + connect to the MySQL server you must use the appropriate -u + and -p options with the commands shown previously. See + Section 4.2.2, "Connecting to the MySQL Server." For more information about mysqlshow, see Section 4.5.6, - "mysqlshow --- Display Database, Table, and Column Information." + "mysqlshow --- Display Database, Table, and Column + Information." -2.3.8. Troubleshooting a Microsoft Windows MySQL Server Installation +2.3.8 Troubleshooting a Microsoft Windows MySQL Server Installation When installing and running MySQL for the first time, you may encounter certain errors that prevent the MySQL server from - starting. The purpose of this section is to help you diagnose and - correct some of these errors. + starting. This section helps you diagnose and correct some of + these errors. Your first resource when troubleshooting server issues is the error log. The MySQL server uses the error log to record - information relevant to the error that prevents the server from - starting. The error log is located in the data directory specified - in your my.ini file. The default data directory location is - C:\Program Files\MySQL\MySQL Server 5.5\data, or - C:\ProgramData\Mysql on Windows 7 and Windows Server 2008. The - C:\ProgramData directory is hidden by default. You need to change - your folder options to see the directory and contents. For more - information on the error log and understanding the content, see - Section 5.2.2, "The Error Log." - - Another source of information regarding possible errors is the - console messages displayed when the MySQL service is starting. Use - the NET START MySQL command from the command line after installing - mysqld as a service to see any error messages regarding the - starting of the MySQL server as a service. See Section 2.3.7.7, - "Starting MySQL as a Windows Service." - - The following examples show other common error messages you may - encounter when installing MySQL and starting the server for the - first time: + information relevant to the error that prevents the server + from starting. The error log is located in the data directory + specified in your my.ini file. The default data directory + location is C:\Program Files\MySQL\MySQL Server 5.5\data, or + C:\ProgramData\Mysql on Windows 7 and Windows Server 2008. + The C:\ProgramData directory is hidden by default. You need + to change your folder options to see the directory and + contents. For more information on the error log and + understanding the content, see Section 5.2.2, "The Error + Log." + + For information regarding possible errors, also consult the + console messages displayed when the MySQL service is + starting. Use the NET START MySQL command from the command + line after installing mysqld as a service to see any error + messages regarding the starting of the MySQL server as a + service. See Section 2.3.7.7, "Starting MySQL as a Windows + Service." - * If the MySQL server cannot find the mysql privileges database - or other critical files, you may see these messages: + The following examples show other common error messages you + might encounter when installing MySQL and starting the server + for the first time: + + * If the MySQL server cannot find the mysql privileges + database or other critical files, it displays these + messages: System error 1067 has occurred. -Fatal error: Can't open privilege tables: Table 'mysql.host' doesn't -exist +Fatal error: Can't open and lock privilege tables: +Table 'mysql.user' doesn't exist + These messages often occur when the MySQL base or data directories are installed in different locations than the - default locations (C:\Program Files\MySQL\MySQL Server 5.5 and - C:\Program Files\MySQL\MySQL Server 5.5\data, respectively). - This situation may occur when MySQL is upgraded and installed - to a new location, but the configuration file is not updated - to reflect the new location. In addition, there may be old and - new configuration files that conflict. Be sure to delete or - rename any old configuration files when upgrading MySQL. + default locations (C:\Program Files\MySQL\MySQL Server + 5.5 and C:\Program Files\MySQL\MySQL Server 5.5\data, + respectively). + This situation can occur when MySQL is upgraded and + installed to a new location, but the configuration file + is not updated to reflect the new location. In addition, + old and new configuration files might conflict. Be sure + to delete or rename any old configuration files when + upgrading MySQL. If you have installed MySQL to a directory other than - C:\Program Files\MySQL\MySQL Server 5.5, you need to ensure - that the MySQL server is aware of this through the use of a - configuration (my.ini) file. The my.ini file needs to be - located in your Windows directory, typically C:\WINDOWS. You - can determine its exact location from the value of the WINDIR - environment variable by issuing the following command from the - command prompt: + C:\Program Files\MySQL\MySQL Server 5.5, ensure that the + MySQL server is aware of this through the use of a + configuration (my.ini) file. Put the my.ini file in your + Windows directory, typically C:\WINDOWS. To determine its + exact location from the value of the WINDIR environment + variable, issue the following command from the command + prompt: C:\> echo %WINDIR% - An option file can be created and modified with any text - editor, such as Notepad. For example, if MySQL is installed in - E:\mysql and the data directory is D:\MySQLdata, you can - create the option file and set up a [mysqld] section to - specify values for the basedir and datadir options: + + You can create or modify an option file with any text + editor, such as Notepad. For example, if MySQL is + installed in E:\mysql and the data directory is + D:\MySQLdata, you can create the option file and set up a + [mysqld] section to specify values for the basedir and + datadir options: [mysqld] # set basedir to your installation path basedir=E:/mysql # set datadir to the location of your data directory datadir=D:/MySQLdata - Note that Windows path names are specified in option files - using (forward) slashes rather than backslashes. If you do use - backslashes, double them: + + Microsoft Windows path names are specified in option + files using (forward) slashes rather than backslashes. If + you do use backslashes, double them: [mysqld] # set basedir to your installation path basedir=C:\\Program Files\\MySQL\\MySQL Server 5.5 # set datadir to the location of your data directory datadir=D:\\MySQLdata - The rules for use of backslash in option file values are given - in Section 4.2.3.3, "Using Option Files." - If you change the datadir value in your MySQL configuration - file, you must move the contents of the existing MySQL data - directory before restarting the MySQL server. + + The rules for use of backslash in option file values are + given in Section 4.2.6, "Using Option Files." + If you change the datadir value in your MySQL + configuration file, you must move the contents of the + existing MySQL data directory before restarting the MySQL + server. See Section 2.3.7.2, "Creating an Option File." - * If you reinstall or upgrade MySQL without first stopping and - removing the existing MySQL service and install MySQL using - the MySQL Configuration Wizard, you may see this error: + * If you reinstall or upgrade MySQL without first stopping + and removing the existing MySQL service and install MySQL + using the MySQL Installer, you might see this error: Error: Cannot create Windows service for MySql. Error: 0 - This occurs when the Configuration Wizard tries to install the - service and finds an existing service with the same name. - One solution to this problem is to choose a service name other - than mysql when using the configuration wizard. This enables - the new service to be installed correctly, but leaves the - outdated service in place. Although this is harmless, it is - best to remove old services that are no longer in use. + + This occurs when the Configuration Wizard tries to + install the service and finds an existing service with + the same name. + One solution to this problem is to choose a service name + other than mysql when using the configuration wizard. + This enables the new service to be installed correctly, + but leaves the outdated service in place. Although this + is harmless, it is best to remove old services that are + no longer in use. To permanently remove the old mysql service, execute the - following command as a user with administrative privileges, on - the command-line: + following command as a user with administrative + privileges, on the command line: C:\> sc delete mysql [SC] DeleteService SUCCESS + If the sc utility is not available for your version of Windows, download the delsrv utility from - http://www.microsoft.com/windows2000/techinfo/reskit/tools/exi - sting/delsrv-o.asp and use the delsrv mysql syntax. + http://www.microsoft.com/windows2000/techinfo/reskit/tool + s/existing/delsrv-o.asp and use the delsrv mysql syntax. -2.3.9. Upgrading MySQL on Windows +2.3.9 Upgrading MySQL on Windows - This section lists some of the steps you should take when - upgrading MySQL on Windows. + To upgrade MySQL on Windows, follow these steps: - 1. Review Section 2.12.1, "Upgrading MySQL," for additional + 1. Review Section 2.11.1, "Upgrading MySQL," for additional information on upgrading MySQL that is not specific to Windows. - 2. You should always back up your current MySQL installation - before performing an upgrade. See Section 7.2, "Database - Backup Methods." + 2. Always back up your current MySQL installation before + performing an upgrade. See Section 7.2, "Database Backup + Methods." 3. Download the latest Windows distribution of MySQL from http://dev.mysql.com/downloads/. - 4. Before upgrading MySQL, you must stop the server. If the - server is installed as a service, stop the service with the + 4. Before upgrading MySQL, stop the server. If the server is + installed as a service, stop the service with the following command from the command prompt: C:\> NET STOP MySQL + If you are not running the MySQL server as a service, use mysqladmin to stop it. For example, before upgrading from - MySQL 5.1 to 5.5, use mysqladmin from MySQL 5.1 as follows: + MySQL 5.1 to 5.5, use mysqladmin from MySQL 5.1 as + follows: C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqladmin" -u root - shutdown +shutdown + Note - If the MySQL root user account has a password, you need to - invoke mysqladmin with the -p option and supply the password - when prompted. - - 5. Before upgrading a MySQL service from MySQL 5.1 to 5.5, you - should stop the 5.1 server and remove the instance. Run the - MySQL Instance Configuration Wizard, choose the Remove - Instance option and in the next screen, confirm removal. After - that it is safe to uninstall MySQL Server 5.1. - - 6. Before upgrading to MySQL 5.5 from a version previous to - 4.1.5, or from a version of MySQL installed from a Zip archive - to a version of MySQL installed with the MySQL Installation - Wizard, you must first manually remove the previous - installation and MySQL service (if the server is installed as - a service). + If the MySQL root user account has a password, invoke + mysqladmin with the -p option and enter the password when + prompted. + + 5. Before upgrading to MySQL 5.5 from a version previous to + 4.1.5, or from a version of MySQL installed from a Zip + archive to a version of MySQL installed with the MySQL + Installation Wizard, you must first manually remove the + previous installation and MySQL service (if the server is + installed as a service). To remove the MySQL service, use the following command: C:\> C:\mysql\bin\mysqld --remove + If you do not remove the existing service, the MySQL - Installation Wizard may fail to properly install the new MySQL - service. + Installation Wizard may fail to properly install the new + MySQL service. - 7. If you are using the MySQL Installation Wizard, start the + 6. If you are using the MySQL Installer, start it as + described in Section 2.3.3, "Installing MySQL on + Microsoft Windows Using MySQL Installer." + If you are using the MySQL Installation Wizard, start the wizard as described in Section 2.3.5.1, "Using the MySQL Installation Wizard." - 8. If you are installing MySQL from a Zip archive, extract the - archive. You may either overwrite your existing MySQL - installation (usually located at C:\mysql), or install it into - a different directory, such as C:\mysql5. Overwriting the - existing installation is recommended. - - 9. If you were running MySQL as a Windows service and you had to - remove the service earlier in this procedure, reinstall the - service. (See Section 2.3.7.7, "Starting MySQL as a Windows - Service.") - 10. Restart the server. For example, use NET START MySQL if you - run MySQL as a service, or invoke mysqld directly otherwise. - 11. As Administrator, run mysql_upgrade to check your tables, - attempt to repair them if necessary, and update your grant - tables if they have changed so that you can take advantage of - any new capabilities. See Section 4.4.7, "mysql_upgrade --- - Check and Upgrade MySQL Tables." - 12. If you encounter errors, see Section 2.3.8, "Troubleshooting a - Microsoft Windows MySQL Server Installation." - -2.3.10. Windows Postinstallation Procedures - - On Windows, you need not create the data directory and the grant - tables. MySQL Windows distributions include the grant tables with - a set of preinitialized accounts in the mysql database under the - data directory. Regarding passwords, if you installed MySQL using - the Windows Installation Wizard, you may have already assigned - passwords to the accounts. (See Section 2.3.5.1, "Using the MySQL - Installation Wizard.") Otherwise, use the password-assignment - procedure given in Section 2.11.2, "Securing the Initial MySQL + 7. If you are upgrading MySQL from a Zip archive, extract + the archive. You may either overwrite your existing MySQL + installation (usually located at C:\mysql), or install it + into a different directory, such as C:\mysql5. + Overwriting the existing installation is recommended. + However, for upgrades (as opposed to installing for the + first time), you must remove the data directory from your + existing MySQL installation to avoid replacing your + current data files. To do so, follow these steps: + a. Unzip the Zip archive in some location other than + your current MySQL installation + b. Remove the data directory + c. Rezip the Zip archive + d. Unzip the modified Zip archive on top of your + existing installation + Alternatively: + a. Unzip the Zip archive in some location other than + your current MySQL installation + b. Remove the data directory + c. Move the data directory from the current MySQL + installation to the location of the just-removed + data directory + d. Remove the current MySQL installation + e. Move the unzipped installation to the location of + the just-removed installation + + 8. If you were running MySQL as a Windows service and you + had to remove the service earlier in this procedure, + reinstall the service. (See Section 2.3.7.7, "Starting + MySQL as a Windows Service.") + + 9. Restart the server. For example, use NET START MySQL if + you run MySQL as a service, or invoke mysqld directly + otherwise. + 10. As Administrator, run mysql_upgrade to check your tables, + attempt to repair them if necessary, and update your + grant tables if they have changed so that you can take + advantage of any new capabilities. See Section 4.4.7, + "mysql_upgrade --- Check and Upgrade MySQL Tables." + 11. If you encounter errors, see Section 2.3.8, + "Troubleshooting a Microsoft Windows MySQL Server + Installation." + +2.3.10 Windows Postinstallation Procedures + + GUI tools exist that perform most of the tasks described + below, including: + + * MySQL Installer: Used to install and upgrade MySQL + products. + + * MySQL Workbench: Manages the MySQL server and edits SQL + statements. + + * MySQL Notifier: Starts, stops, or restarts the MySQL + server, and monitors its status. + + * MySQL for Excel + (http://dev.mysql.com/doc/mysql-for-excel/en/index.html): + Edits MySQL data with Microsoft Excel. + + On Windows, you need not create the data directory and the + grant tables. MySQL Windows distributions include the grant + tables with a set of preinitialized accounts in the mysql + database under the data directory. Regarding passwords, if + you installed MySQL using the MySQL Installer, you may have + already assigned passwords to the accounts. (See Section + 2.3.3, "Installing MySQL on Microsoft Windows Using MySQL + Installer.") Otherwise, use the password-assignment procedure + given in Section 2.10.2, "Securing the Initial MySQL Accounts." - Before setting up passwords, you might want to try running some - client programs to make sure that you can connect to the server - and that it is operating properly. Make sure that the server is - running (see Section 2.3.7.4, "Starting the Server for the First - Time"), and then issue the following commands to verify that you - can retrieve information from the server. You may need to specify - directory different from C:\mysql\bin on the command line. If you - used the Windows Installation Wizard, the default directory is - C:\Program Files\MySQL\MySQL Server 5.5, and the mysql and - mysqlshow client programs are in C:\Program Files\MySQL\MySQL - Server 5.5\bin. See Section 2.3.5.1, "Using the MySQL Installation - Wizard," for more information. + Before setting up passwords, you might want to try running + some client programs to make sure that you can connect to the + server and that it is operating properly. Make sure that the + server is running (see Section 2.3.7.4, "Starting the Server + for the First Time"). If you are running a version of Windows + that supports services, you can set up the MySQL server to + run automatically when Windows starts (see Section 2.3.7.7, + "Starting MySQL as a Windows Service"). + + With the server running, issue the following commands to + verify that you can retrieve information from the server. You + may need to specify a directory different from C:\mysql\bin + on the command line. If you installed MySQL using MySQL + Installer, the default directory is C:\Program + Files\MySQL\MySQL Server 5.5, and the mysql and mysqlshow + client programs are in C:\Program Files\MySQL\MySQL Server + 5.5\bin. See Section 2.3.3, "Installing MySQL on Microsoft + Windows Using MySQL Installer," for more information. Use mysqlshow to see what databases exist: C:\> C:\mysql\bin\mysqlshow @@ -2929,20 +3507,21 @@ | test | +--------------------+ - The list of installed databases may vary, but will always include - the minimum of mysql and information_schema. In most cases, the - test database will also be installed automatically. - - The preceding command (and commands for other MySQL programs such - as mysql) may not work if the correct MySQL account does not - exist. For example, the program may fail with an error, or you may - not be able to view all databases. If you installed using the MSI - packages and used the MySQL Server Instance Config Wizard, then - the root user will have been created automatically with the - password you supplied. In this case, you should use the -u root - and -p options. (You will also need to use the -u root and -p - options if you have already secured the initial MySQL accounts.) - With -p, you will be prompted for the root password. For example: + The list of installed databases may vary, but will always + include the minimum of mysql and information_schema. In most + cases, the test database will also be installed + automatically. + + The preceding command (and commands for other MySQL programs + such as mysql) may not work if the correct MySQL account does + not exist. For example, the program may fail with an error, + or you may not be able to view all databases. If you + installed MySQL using MySQL Installer, the root user will + have been created automatically with the password you + supplied. In this case, you should use the -u root and -p + options. (You must use those options if you have already + secured the initial MySQL accounts.) With -p, the client + program prompts for the root password. For example: C:\> C:\mysql\bin\mysqlshow -u root -p Enter password: (enter root password here) +--------------------+ @@ -2953,8 +3532,8 @@ | test | +--------------------+ - If you specify a database name, mysqlshow displays a list of the - tables within the database: + If you specify a database name, mysqlshow displays a list of + the tables within the database: C:\> C:\mysql\bin\mysqlshow mysql Database: mysql +---------------------------+ @@ -2982,8 +3561,8 @@ | user | +---------------------------+ - Use the mysql program to select information from a table in the - mysql database: + Use the mysql program to select information from a table in + the mysql database: C:\> C:\mysql\bin\mysql -e "SELECT Host,Db,User FROM mysql.db" +------+--------+------+ | host | db | user | @@ -2992,14 +3571,7 @@ | % | test_% | | +------+--------+------+ - For more information about mysqlshow and mysql, see Section 4.5.6, - "mysqlshow --- Display Database, Table, and Column Information," - and Section 4.5.1, "mysql --- The MySQL Command-Line Tool." - - If you are running a version of Windows that supports services, - you can set up the MySQL server to run automatically when Windows - starts. See Section 2.3.7.7, "Starting MySQL as a Windows - Service." - - Copyright (c) 1997, 2013, Oracle and/or its affiliates. All rights - reserved. Legal Notices + For more information about mysqlshow and mysql, see Section + 4.5.6, "mysqlshow --- Display Database, Table, and Column + Information," and Section 4.5.1, "mysql --- The MySQL + Command-Line Tool." diff -Nru mysql-5.5-5.5.35+dfsg/extra/replace.c mysql-5.5-5.5.43/extra/replace.c --- mysql-5.5-5.5.35+dfsg/extra/replace.c 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/replace.c 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License @@ -1020,7 +1020,7 @@ updated=retain=0; reset_buffer(); - while ((error=fill_buffer_retaining(fileno(in),retain)) > 0) + while ((error=fill_buffer_retaining(my_fileno(in),retain)) > 0) { end_of_line=buffer ; buffer[bufbytes]=0; /* Sentinel */ diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/certs/ca-cert.pem mysql-5.5-5.5.43/extra/yassl/certs/ca-cert.pem --- mysql-5.5-5.5.35+dfsg/extra/yassl/certs/ca-cert.pem 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/certs/ca-cert.pem 2015-02-27 08:30:34.000000000 +0000 @@ -1,56 +1,87 @@ +-----BEGIN CERTIFICATE----- +MIIEqjCCA5KgAwIBAgIJAJpBR82hFGKMMA0GCSqGSIb3DQEBBQUAMIGUMQswCQYD +VQQGEwJVUzEQMA4GA1UECAwHTW9udGFuYTEQMA4GA1UEBwwHQm96ZW1hbjERMA8G +A1UECgwIU2F3dG9vdGgxEzARBgNVBAsMCkNvbnN1bHRpbmcxGDAWBgNVBAMMD3d3 +dy53b2xmc3NsLmNvbTEfMB0GCSqGSIb3DQEJARYQaW5mb0B3b2xmc3NsLmNvbTAe +Fw0xNDA3MTEwMzIwMDhaFw0xNzA0MDYwMzIwMDhaMIGUMQswCQYDVQQGEwJVUzEQ +MA4GA1UECAwHTW9udGFuYTEQMA4GA1UEBwwHQm96ZW1hbjERMA8GA1UECgwIU2F3 +dG9vdGgxEzARBgNVBAsMCkNvbnN1bHRpbmcxGDAWBgNVBAMMD3d3dy53b2xmc3Ns +LmNvbTEfMB0GCSqGSIb3DQEJARYQaW5mb0B3b2xmc3NsLmNvbTCCASIwDQYJKoZI +hvcNAQEBBQADggEPADCCAQoCggEBAL8Myi0Ush6EQlvNOB9K8k11EPG2NZ/fyn0D +mNOs3gNm7irx2LB9bgdUCxCYIU2AyxIg58xP3kV9yXJ3MurKkLtpUhADL6jzlcXx +i2JWG+9nb6QQQZWtCpvjpcCw0nB2UDBbqOgILHztp6J6jTgpHKzH7fJ8lbCVgn1J +XDjNdyXvvYB1U5Q8PcpjW58VtdMdEy8Z0TzbdjrMuH3J5cLX2kBv2CHccxtCLVOc +/hr8fat6Nj+Y3oR8BWfOahQ4h6nxjLVoy2h/cSAr9aBj9VYvoybSt2+xWhfXOJkI +/pNYb/7DE0kIFgunTWcAUjFnI06Y7VFFHbkE2Qvs2CizS73tNnkCAwEAAaOB/DCB ++TAdBgNVHQ4EFgQUJ45nEXTDJh0/7TNjs6TYHTDl6NUwgckGA1UdIwSBwTCBvoAU +J45nEXTDJh0/7TNjs6TYHTDl6NWhgZqkgZcwgZQxCzAJBgNVBAYTAlVTMRAwDgYD +VQQIDAdNb250YW5hMRAwDgYDVQQHDAdCb3plbWFuMREwDwYDVQQKDAhTYXd0b290 +aDETMBEGA1UECwwKQ29uc3VsdGluZzEYMBYGA1UEAwwPd3d3LndvbGZzc2wuY29t +MR8wHQYJKoZIhvcNAQkBFhBpbmZvQHdvbGZzc2wuY29tggkAmkFHzaEUYowwDAYD +VR0TBAUwAwEB/zANBgkqhkiG9w0BAQUFAAOCAQEAeXgMbXmIkfw6FZz5J2IW8CEf ++n0/oqgyHvfyEal0FnRe3BjK8AAq1QMGJjDxR4P9Mm787apPfQxjYDEvfAy/mWaH +7ScIhi3EM+iYIxz+o9uaSU78WkLvccM/rdxKqNKjHQmsMwR7hvNtAFmjyNvRPHP2 +DpDWXkngvzZjCHulsI81O1aMETVJBBzQ57pWxQ0KkY3Wt2IZNBJSTNJtfMU9DxiB +VMv2POWE0tZxFewaNAvwoCF0Q8ijsN/ZZ9rirZNI+KCHvXkU4GIK3/cxLjF70TIq +Cv5dFO/ZZFDkg5G8cA3XiI3ZvIQOxRqzv2QCTlGRpKKFFYOv8FubKElfsrMD2A== +-----END CERTIFICATE----- Certificate: Data: Version: 3 (0x2) Serial Number: - 8a:37:22:65:73:f5:aa:e8 - Signature Algorithm: md5WithRSAEncryption - Issuer: C=US, ST=Montana, L=Bozeman, O=sawtooth, OU=consulting, CN=www.sawtooth-consulting.com/emailAddress=info@yassl.com + 9a:41:47:cd:a1:14:62:8c + Signature Algorithm: sha1WithRSAEncryption + Issuer: C=US, ST=Montana, L=Bozeman, O=Sawtooth, OU=Consulting, CN=www.wolfssl.com/emailAddress=info@wolfssl.com Validity - Not Before: Jun 30 18:47:10 2010 GMT - Not After : Mar 26 18:47:10 2013 GMT - Subject: C=US, ST=Montana, L=Bozeman, O=sawtooth, OU=consulting, CN=www.sawtooth-consulting.com/emailAddress=info@yassl.com + Not Before: Jul 11 03:20:08 2014 GMT + Not After : Apr 6 03:20:08 2017 GMT + Subject: C=US, ST=Montana, L=Bozeman, O=Sawtooth, OU=Consulting, CN=www.wolfssl.com/emailAddress=info@wolfssl.com Subject Public Key Info: Public Key Algorithm: rsaEncryption - RSA Public Key: (512 bit) - Modulus (512 bit): - 00:97:30:b9:1a:92:ef:25:4f:ca:4c:11:31:95:1a: - e1:c0:10:19:0a:20:b9:37:80:1a:57:38:02:4e:1b: - c5:0f:28:4f:da:e3:c9:16:aa:50:bd:4a:fb:b7:71: - c7:35:cc:63:81:c1:dd:9d:33:f9:38:16:88:32:a0: - aa:56:23:03:a3 + Public-Key: (2048 bit) + Modulus: + 00:bf:0c:ca:2d:14:b2:1e:84:42:5b:cd:38:1f:4a: + f2:4d:75:10:f1:b6:35:9f:df:ca:7d:03:98:d3:ac: + de:03:66:ee:2a:f1:d8:b0:7d:6e:07:54:0b:10:98: + 21:4d:80:cb:12:20:e7:cc:4f:de:45:7d:c9:72:77: + 32:ea:ca:90:bb:69:52:10:03:2f:a8:f3:95:c5:f1: + 8b:62:56:1b:ef:67:6f:a4:10:41:95:ad:0a:9b:e3: + a5:c0:b0:d2:70:76:50:30:5b:a8:e8:08:2c:7c:ed: + a7:a2:7a:8d:38:29:1c:ac:c7:ed:f2:7c:95:b0:95: + 82:7d:49:5c:38:cd:77:25:ef:bd:80:75:53:94:3c: + 3d:ca:63:5b:9f:15:b5:d3:1d:13:2f:19:d1:3c:db: + 76:3a:cc:b8:7d:c9:e5:c2:d7:da:40:6f:d8:21:dc: + 73:1b:42:2d:53:9c:fe:1a:fc:7d:ab:7a:36:3f:98: + de:84:7c:05:67:ce:6a:14:38:87:a9:f1:8c:b5:68: + cb:68:7f:71:20:2b:f5:a0:63:f5:56:2f:a3:26:d2: + b7:6f:b1:5a:17:d7:38:99:08:fe:93:58:6f:fe:c3: + 13:49:08:16:0b:a7:4d:67:00:52:31:67:23:4e:98: + ed:51:45:1d:b9:04:d9:0b:ec:d8:28:b3:4b:bd:ed: + 36:79 Exponent: 65537 (0x10001) X509v3 extensions: X509v3 Subject Key Identifier: - 3B:66:FD:A0:40:C6:F4:E2:70:CF:21:1A:0C:4F:67:FE:B7:4B:42:09 + 27:8E:67:11:74:C3:26:1D:3F:ED:33:63:B3:A4:D8:1D:30:E5:E8:D5 X509v3 Authority Key Identifier: - keyid:3B:66:FD:A0:40:C6:F4:E2:70:CF:21:1A:0C:4F:67:FE:B7:4B:42:09 - DirName:/C=US/ST=Montana/L=Bozeman/O=sawtooth/OU=consulting/CN=www.sawtooth-consulting.com/emailAddress=info@yassl.com - serial:8A:37:22:65:73:F5:AA:E8 + keyid:27:8E:67:11:74:C3:26:1D:3F:ED:33:63:B3:A4:D8:1D:30:E5:E8:D5 + DirName:/C=US/ST=Montana/L=Bozeman/O=Sawtooth/OU=Consulting/CN=www.wolfssl.com/emailAddress=info@wolfssl.com + serial:9A:41:47:CD:A1:14:62:8C X509v3 Basic Constraints: CA:TRUE - Signature Algorithm: md5WithRSAEncryption - 32:65:a2:b1:dc:6d:e0:8d:8b:c8:58:29:8e:b8:18:4b:62:88: - 13:67:f8:6c:75:46:75:8f:8a:19:a6:a3:d5:3c:fc:57:4e:7a: - 68:a9:fc:93:dc:ae:29:7d:bb:4e:ec:ea:55:fa:a4:e3:00:61: - f4:b0:34:6d:d1:d5:a4:64:24:f8 ------BEGIN CERTIFICATE----- -MIIDQDCCAuqgAwIBAgIJAIo3ImVz9aroMA0GCSqGSIb3DQEBBAUAMIGeMQswCQYD -VQQGEwJVUzEQMA4GA1UECBMHTW9udGFuYTEQMA4GA1UEBxMHQm96ZW1hbjERMA8G -A1UEChMIc2F3dG9vdGgxEzARBgNVBAsTCmNvbnN1bHRpbmcxJDAiBgNVBAMTG3d3 -dy5zYXd0b290aC1jb25zdWx0aW5nLmNvbTEdMBsGCSqGSIb3DQEJARYOaW5mb0B5 -YXNzbC5jb20wHhcNMTAwNjMwMTg0NzEwWhcNMTMwMzI2MTg0NzEwWjCBnjELMAkG -A1UEBhMCVVMxEDAOBgNVBAgTB01vbnRhbmExEDAOBgNVBAcTB0JvemVtYW4xETAP -BgNVBAoTCHNhd3Rvb3RoMRMwEQYDVQQLEwpjb25zdWx0aW5nMSQwIgYDVQQDExt3 -d3cuc2F3dG9vdGgtY29uc3VsdGluZy5jb20xHTAbBgkqhkiG9w0BCQEWDmluZm9A -eWFzc2wuY29tMFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBAJcwuRqS7yVPykwRMZUa -4cAQGQoguTeAGlc4Ak4bxQ8oT9rjyRaqUL1K+7dxxzXMY4HB3Z0z+TgWiDKgqlYj -A6MCAwEAAaOCAQcwggEDMB0GA1UdDgQWBBQ7Zv2gQMb04nDPIRoMT2f+t0tCCTCB -0wYDVR0jBIHLMIHIgBQ7Zv2gQMb04nDPIRoMT2f+t0tCCaGBpKSBoTCBnjELMAkG -A1UEBhMCVVMxEDAOBgNVBAgTB01vbnRhbmExEDAOBgNVBAcTB0JvemVtYW4xETAP -BgNVBAoTCHNhd3Rvb3RoMRMwEQYDVQQLEwpjb25zdWx0aW5nMSQwIgYDVQQDExt3 -d3cuc2F3dG9vdGgtY29uc3VsdGluZy5jb20xHTAbBgkqhkiG9w0BCQEWDmluZm9A -eWFzc2wuY29tggkAijciZXP1qugwDAYDVR0TBAUwAwEB/zANBgkqhkiG9w0BAQQF -AANBADJlorHcbeCNi8hYKY64GEtiiBNn+Gx1RnWPihmmo9U8/FdOemip/JPcril9 -u07s6lX6pOMAYfSwNG3R1aRkJPg= ------END CERTIFICATE----- + Signature Algorithm: sha1WithRSAEncryption + 79:78:0c:6d:79:88:91:fc:3a:15:9c:f9:27:62:16:f0:21:1f: + fa:7d:3f:a2:a8:32:1e:f7:f2:11:a9:74:16:74:5e:dc:18:ca: + f0:00:2a:d5:03:06:26:30:f1:47:83:fd:32:6e:fc:ed:aa:4f: + 7d:0c:63:60:31:2f:7c:0c:bf:99:66:87:ed:27:08:86:2d:c4: + 33:e8:98:23:1c:fe:a3:db:9a:49:4e:fc:5a:42:ef:71:c3:3f: + ad:dc:4a:a8:d2:a3:1d:09:ac:33:04:7b:86:f3:6d:00:59:a3: + c8:db:d1:3c:73:f6:0e:90:d6:5e:49:e0:bf:36:63:08:7b:a5: + b0:8f:35:3b:56:8c:11:35:49:04:1c:d0:e7:ba:56:c5:0d:0a: + 91:8d:d6:b7:62:19:34:12:52:4c:d2:6d:7c:c5:3d:0f:18:81: + 54:cb:f6:3c:e5:84:d2:d6:71:15:ec:1a:34:0b:f0:a0:21:74: + 43:c8:a3:b0:df:d9:67:da:e2:ad:93:48:f8:a0:87:bd:79:14: + e0:62:0a:df:f7:31:2e:31:7b:d1:32:2a:0a:fe:5d:14:ef:d9: + 64:50:e4:83:91:bc:70:0d:d7:88:8d:d9:bc:84:0e:c5:1a:b3: + bf:64:02:4e:51:91:a4:a2:85:15:83:af:f0:5b:9b:28:49:5f: + b2:b3:03:d8 diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/certs/ca-key.pem mysql-5.5-5.5.43/extra/yassl/certs/ca-key.pem --- mysql-5.5-5.5.35+dfsg/extra/yassl/certs/ca-key.pem 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/certs/ca-key.pem 2015-02-27 08:30:34.000000000 +0000 @@ -1,9 +1,27 @@ -----BEGIN RSA PRIVATE KEY----- -MIIBOQIBAAJBAJcwuRqS7yVPykwRMZUa4cAQGQoguTeAGlc4Ak4bxQ8oT9rjyRaq -UL1K+7dxxzXMY4HB3Z0z+TgWiDKgqlYjA6MCAwEAAQJAEQ9TY7c+uuQU/J5YDO4a -mRR37tegbq3Kyxqrz+p8QuhqLDtVh13GaF7rVU70vyNHm+cgihUyzho/PViAkPBo -qQIhAMU8/RDhDLgL5BxID4sxKIVBtg+imFSbyKVyg7oQLUcXAiEAxDu94O45Cf4a -np9R0thumY/QqWpCkycWAB7fFEuaf1UCIEH+bg4/vqm2ENUFp23DPPOZUPlaRe3J -UhFJh5mx3/RxAiBq++8vfHFYg1Lb/BxOCXVy/zdRxf753ytdcXdJx1Y56QIgVgpN -FNfYJofQfWaP96sjlc0usrT28uceHx0QmHqolVc= +MIIEpAIBAAKCAQEAvwzKLRSyHoRCW804H0ryTXUQ8bY1n9/KfQOY06zeA2buKvHY +sH1uB1QLEJghTYDLEiDnzE/eRX3Jcncy6sqQu2lSEAMvqPOVxfGLYlYb72dvpBBB +la0Km+OlwLDScHZQMFuo6AgsfO2nonqNOCkcrMft8nyVsJWCfUlcOM13Je+9gHVT +lDw9ymNbnxW10x0TLxnRPNt2Osy4fcnlwtfaQG/YIdxzG0ItU5z+Gvx9q3o2P5je +hHwFZ85qFDiHqfGMtWjLaH9xICv1oGP1Vi+jJtK3b7FaF9c4mQj+k1hv/sMTSQgW +C6dNZwBSMWcjTpjtUUUduQTZC+zYKLNLve02eQIDAQABAoIBAD1uTmAahH+dhXzh +Swd84NaZKt6d+TY0DncOPgjqT+UGJtT2OPffDQ8cLgai9CponGNy4zXmBJGRtcGx +pFSs18b7QaDWdW+9C06/sVLoX0kmmFZHx97p6jxgAb8o3DG/SV+TSYd6gVuWS03K +XDhPt+Gy08ch2jwShwfkG9xD7OjsVGHn9u2mCy7134J/xh9hGZykgznfIYWJb3ev +hhUyCKJaCyZh+3AMypw4fbwi7uujqBYA+YqAHgCEqEpB+IQDZy8jWy+baybDBzSU +owM7ctWfcuCtzDSrvcfV9SYwhQ8wIzlS/zzLmSFNiKWr7mK5x+C7R4fBac9z8zC+ +zjkEnOUCgYEA4XZFgFm200nfCu8S1g/wt8sqN7+n+LVN9TE1reSjlKHb8ZattQVk +hYP8G1spqr74Jj92fq0c8MvXJrQbBY5Whn4IYiHBhtZHeT63XaTGOtexdCD2UJdB +BFPtPybWb5H6aCbsKtya8efc+3PweUMbIaNZBGNSB8nX5tEbXV6W+lMCgYEA2O1O +ZGFrkQxhAbUPu0RnUx7cB8Qkfp5shCORDOQSBBZNeJjMlj0gTg9Fmrb4s5MNsqIb +KfImecjF0nh+XnPy13Bhu0DOYQX+aR6CKeYUuKHnltAjPwWTAPLhTX7tt5Zs9/Dk +0c8BmE/cdFSqbV5aQTH+/5q2oAXdqRBU+GvQqoMCgYAh0wSKROtQt3xmv4cr5ihO +6oPi6TXh8hFH/6H1/J8t5TqB/AEDb1OtVCe2Uu7lVtETq+GzD3WQCoS0ocCMDNae +RrorPrUx7WO7pNUNj3LN0R4mNeu+G3L9mzm0h7cT9eqDRZOYuo/kSsy0TKh/CLpB +SahJKD1ePcHONwDL+SzdUQKBgQChV58+udavg22DP4/70NyozgMJI7GhG2PKxElW +NSvRLmVglQVVmRE1/dXfRMeliHJfsoJRqHFFkzbPXB9hUQwFgOivxXu6XiLjPHXD +hAVVbdY6LYSJkzPLONqqMQXNzmwt3VXTVwvwpTVqsK4xukOWygDHS+MZEkPTQvpv +6oDA0QKBgQC524kgNCdwYjTqXyViEvOdgb9I7poOwY0Q/2WanS0aipRayMClpYRh +ntQkue+pncl3C8dwZj26yFTf0jPh9X/5J2G+V0Xdt0UXJPUj5DgOkSfu4yDYFMiU +R3dAd0UYng3OeT9XMVYJSWe+lFhP9sSr4onj44rABVUsJMBKlwQnmg== -----END RSA PRIVATE KEY----- Binary files /tmp/MslfMd0v5_/mysql-5.5-5.5.35+dfsg/extra/yassl/certs/client-cert.der and /tmp/NaaegeSpl1/mysql-5.5-5.5.43/extra/yassl/certs/client-cert.der differ diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/certs/client-cert.pem mysql-5.5-5.5.43/extra/yassl/certs/client-cert.pem --- mysql-5.5-5.5.35+dfsg/extra/yassl/certs/client-cert.pem 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/certs/client-cert.pem 2015-02-27 08:30:34.000000000 +0000 @@ -2,54 +2,86 @@ Data: Version: 3 (0x2) Serial Number: - c5:d7:6c:11:36:f0:35:e1 - Signature Algorithm: md5WithRSAEncryption - Issuer: C=US, ST=Oregon, L=Portland, O=yaSSL, OU=programming, CN=www.yassl.com/emailAddress=info@yassl.com + b6:63:af:8f:5d:62:57:a0 + Signature Algorithm: sha1WithRSAEncryption + Issuer: C=US, ST=Montana, L=Bozeman, O=wolfSSL, OU=Programming, CN=www.wolfssl.com/emailAddress=info@wolfssl.com Validity - Not Before: Jun 30 18:39:39 2010 GMT - Not After : Mar 26 18:39:40 2013 GMT - Subject: C=US, ST=Oregon, L=Portland, O=yaSSL, OU=programming, CN=www.yassl.com/emailAddress=info@yassl.com + Not Before: Jul 11 17:39:44 2014 GMT + Not After : Apr 6 17:39:44 2017 GMT + Subject: C=US, ST=Montana, L=Bozeman, O=wolfSSL, OU=Programming, CN=www.wolfssl.com/emailAddress=info@wolfssl.com Subject Public Key Info: Public Key Algorithm: rsaEncryption - RSA Public Key: (512 bit) - Modulus (512 bit): - 00:bd:51:4a:14:fd:6a:19:84:0c:33:38:fc:27:32: - 9c:97:0b:fc:a4:18:60:69:4e:d9:d8:78:50:0b:e9: - 20:5d:d6:1d:70:1c:0c:24:9f:23:82:cc:3a:01:d5: - 97:17:b2:73:6c:86:cf:b5:f1:e5:ce:68:0c:d9:a2: - 12:39:7c:f2:53 + Public-Key: (2048 bit) + Modulus: + 00:c3:03:d1:2b:fe:39:a4:32:45:3b:53:c8:84:2b: + 2a:7c:74:9a:bd:aa:2a:52:07:47:d6:a6:36:b2:07: + 32:8e:d0:ba:69:7b:c6:c3:44:9e:d4:81:48:fd:2d: + 68:a2:8b:67:bb:a1:75:c8:36:2c:4a:d2:1b:f7:8b: + ba:cf:0d:f9:ef:ec:f1:81:1e:7b:9b:03:47:9a:bf: + 65:cc:7f:65:24:69:a6:e8:14:89:5b:e4:34:f7:c5: + b0:14:93:f5:67:7b:3a:7a:78:e1:01:56:56:91:a6: + 13:42:8d:d2:3c:40:9c:4c:ef:d1:86:df:37:51:1b: + 0c:a1:3b:f5:f1:a3:4a:35:e4:e1:ce:96:df:1b:7e: + bf:4e:97:d0:10:e8:a8:08:30:81:af:20:0b:43:14: + c5:74:67:b4:32:82:6f:8d:86:c2:88:40:99:36:83: + ba:1e:40:72:22:17:d7:52:65:24:73:b0:ce:ef:19: + cd:ae:ff:78:6c:7b:c0:12:03:d4:4e:72:0d:50:6d: + 3b:a3:3b:a3:99:5e:9d:c8:d9:0c:85:b3:d9:8a:d9: + 54:26:db:6d:fa:ac:bb:ff:25:4c:c4:d1:79:f4:71: + d3:86:40:18:13:b0:63:b5:72:4e:30:c4:97:84:86: + 2d:56:2f:d7:15:f7:7f:c0:ae:f5:fc:5b:e5:fb:a1: + ba:d3 Exponent: 65537 (0x10001) X509v3 extensions: X509v3 Subject Key Identifier: - 5C:F7:29:21:69:7A:09:78:9E:7B:CD:53:42:02:EC:CE:29:0D:11:DF + 33:D8:45:66:D7:68:87:18:7E:54:0D:70:27:91:C7:26:D7:85:65:C0 X509v3 Authority Key Identifier: - keyid:5C:F7:29:21:69:7A:09:78:9E:7B:CD:53:42:02:EC:CE:29:0D:11:DF - DirName:/C=US/ST=Oregon/L=Portland/O=yaSSL/OU=programming/CN=www.yassl.com/emailAddress=info@yassl.com - serial:C5:D7:6C:11:36:F0:35:E1 + keyid:33:D8:45:66:D7:68:87:18:7E:54:0D:70:27:91:C7:26:D7:85:65:C0 + DirName:/C=US/ST=Montana/L=Bozeman/O=wolfSSL/OU=Programming/CN=www.wolfssl.com/emailAddress=info@wolfssl.com + serial:B6:63:AF:8F:5D:62:57:A0 X509v3 Basic Constraints: CA:TRUE - Signature Algorithm: md5WithRSAEncryption - b4:a5:f1:71:26:4d:b9:ff:54:f3:09:1f:ac:e1:19:59:e5:ec: - 57:e3:f1:0b:b2:8f:f3:29:eb:6b:c6:fa:27:33:3e:91:d0:77: - 43:c9:ce:1e:0f:71:07:a9:f7:26:e0:7e:ff:30:7d:52:0a:e1: - 80:48:46:bb:99:e9:d9:77:ce:75 + Signature Algorithm: sha1WithRSAEncryption + 85:10:90:c5:5d:de:25:8c:f2:57:7b:2d:14:1c:05:f9:71:63: + 40:b0:e3:c1:c1:2e:13:2a:7a:b7:d6:24:58:87:eb:03:fb:0d: + af:e0:f4:d0:c8:bc:51:36:10:4f:79:cc:4f:66:7d:af:99:cb: + 7b:ce:68:94:c6:36:aa:42:6e:8c:78:5b:b2:85:ca:d1:e1:a8: + 31:d1:81:d9:f9:c1:a3:9e:34:43:ef:0a:79:7d:3e:83:61:fc: + 14:5c:d1:dd:bc:0e:d7:51:b7:71:6e:41:7e:8b:2c:5a:9a:cb: + 77:4b:6a:f5:06:ff:02:af:1e:e6:63:4f:bc:44:d9:3f:56:9e: + 09:9c:43:f9:55:21:32:46:82:09:86:a9:7b:74:1c:9e:5a:2a: + bf:03:79:91:cb:f2:29:7f:c9:15:82:89:b9:53:cd:7e:07:90: + a9:5d:76:e1:19:5e:0d:58:b8:59:d5:0d:df:23:ab:6b:63:76: + 19:9e:9c:df:b0:57:49:6c:d0:86:97:c3:6c:3c:fa:e0:56:c2: + 1b:e3:a1:42:1a:58:62:85:9d:74:19:83:08:af:59:90:f8:99: + bd:67:d3:4a:ea:0e:c9:ca:61:8a:0d:8a:42:cc:90:e9:2e:c2: + 54:73:7f:5e:af:8d:e2:32:cb:45:20:d6:19:4d:5b:77:31:cc: + 0f:2d:c0:7e -----BEGIN CERTIFICATE----- -MIIDDjCCArigAwIBAgIJAMXXbBE28DXhMA0GCSqGSIb3DQEBBAUAMIGOMQswCQYD -VQQGEwJVUzEPMA0GA1UECBMGT3JlZ29uMREwDwYDVQQHEwhQb3J0bGFuZDEOMAwG -A1UEChMFeWFTU0wxFDASBgNVBAsTC3Byb2dyYW1taW5nMRYwFAYDVQQDEw13d3cu -eWFzc2wuY29tMR0wGwYJKoZIhvcNAQkBFg5pbmZvQHlhc3NsLmNvbTAeFw0xMDA2 -MzAxODM5MzlaFw0xMzAzMjYxODM5NDBaMIGOMQswCQYDVQQGEwJVUzEPMA0GA1UE -CBMGT3JlZ29uMREwDwYDVQQHEwhQb3J0bGFuZDEOMAwGA1UEChMFeWFTU0wxFDAS -BgNVBAsTC3Byb2dyYW1taW5nMRYwFAYDVQQDEw13d3cueWFzc2wuY29tMR0wGwYJ -KoZIhvcNAQkBFg5pbmZvQHlhc3NsLmNvbTBcMA0GCSqGSIb3DQEBAQUAA0sAMEgC -QQC9UUoU/WoZhAwzOPwnMpyXC/ykGGBpTtnYeFAL6SBd1h1wHAwknyOCzDoB1ZcX -snNshs+18eXOaAzZohI5fPJTAgMBAAGjgfYwgfMwHQYDVR0OBBYEFFz3KSFpegl4 -nnvNU0IC7M4pDRHfMIHDBgNVHSMEgbswgbiAFFz3KSFpegl4nnvNU0IC7M4pDRHf -oYGUpIGRMIGOMQswCQYDVQQGEwJVUzEPMA0GA1UECBMGT3JlZ29uMREwDwYDVQQH -EwhQb3J0bGFuZDEOMAwGA1UEChMFeWFTU0wxFDASBgNVBAsTC3Byb2dyYW1taW5n -MRYwFAYDVQQDEw13d3cueWFzc2wuY29tMR0wGwYJKoZIhvcNAQkBFg5pbmZvQHlh -c3NsLmNvbYIJAMXXbBE28DXhMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQEEBQAD -QQC0pfFxJk25/1TzCR+s4RlZ5exX4/ELso/zKetrxvonMz6R0HdDyc4eD3EHqfcm -4H7/MH1SCuGASEa7menZd851 +MIIEqjCCA5KgAwIBAgIJALZjr49dYlegMA0GCSqGSIb3DQEBBQUAMIGUMQswCQYD +VQQGEwJVUzEQMA4GA1UECAwHTW9udGFuYTEQMA4GA1UEBwwHQm96ZW1hbjEQMA4G +A1UECgwHd29sZlNTTDEUMBIGA1UECwwLUHJvZ3JhbW1pbmcxGDAWBgNVBAMMD3d3 +dy53b2xmc3NsLmNvbTEfMB0GCSqGSIb3DQEJARYQaW5mb0B3b2xmc3NsLmNvbTAe +Fw0xNDA3MTExNzM5NDRaFw0xNzA0MDYxNzM5NDRaMIGUMQswCQYDVQQGEwJVUzEQ +MA4GA1UECAwHTW9udGFuYTEQMA4GA1UEBwwHQm96ZW1hbjEQMA4GA1UECgwHd29s +ZlNTTDEUMBIGA1UECwwLUHJvZ3JhbW1pbmcxGDAWBgNVBAMMD3d3dy53b2xmc3Ns +LmNvbTEfMB0GCSqGSIb3DQEJARYQaW5mb0B3b2xmc3NsLmNvbTCCASIwDQYJKoZI +hvcNAQEBBQADggEPADCCAQoCggEBAMMD0Sv+OaQyRTtTyIQrKnx0mr2qKlIHR9am +NrIHMo7Quml7xsNEntSBSP0taKKLZ7uhdcg2LErSG/eLus8N+e/s8YEee5sDR5q/ +Zcx/ZSRppugUiVvkNPfFsBST9Wd7Onp44QFWVpGmE0KN0jxAnEzv0YbfN1EbDKE7 +9fGjSjXk4c6W3xt+v06X0BDoqAgwga8gC0MUxXRntDKCb42GwohAmTaDuh5AciIX +11JlJHOwzu8Zza7/eGx7wBID1E5yDVBtO6M7o5lencjZDIWz2YrZVCbbbfqsu/8l +TMTRefRx04ZAGBOwY7VyTjDEl4SGLVYv1xX3f8Cu9fxb5fuhutMCAwEAAaOB/DCB ++TAdBgNVHQ4EFgQUM9hFZtdohxh+VA1wJ5HHJteFZcAwgckGA1UdIwSBwTCBvoAU +M9hFZtdohxh+VA1wJ5HHJteFZcChgZqkgZcwgZQxCzAJBgNVBAYTAlVTMRAwDgYD +VQQIDAdNb250YW5hMRAwDgYDVQQHDAdCb3plbWFuMRAwDgYDVQQKDAd3b2xmU1NM +MRQwEgYDVQQLDAtQcm9ncmFtbWluZzEYMBYGA1UEAwwPd3d3LndvbGZzc2wuY29t +MR8wHQYJKoZIhvcNAQkBFhBpbmZvQHdvbGZzc2wuY29tggkAtmOvj11iV6AwDAYD +VR0TBAUwAwEB/zANBgkqhkiG9w0BAQUFAAOCAQEAhRCQxV3eJYzyV3stFBwF+XFj +QLDjwcEuEyp6t9YkWIfrA/sNr+D00Mi8UTYQT3nMT2Z9r5nLe85olMY2qkJujHhb +soXK0eGoMdGB2fnBo540Q+8KeX0+g2H8FFzR3bwO11G3cW5BfossWprLd0tq9Qb/ +Aq8e5mNPvETZP1aeCZxD+VUhMkaCCYape3QcnloqvwN5kcvyKX/JFYKJuVPNfgeQ +qV124RleDVi4WdUN3yOra2N2GZ6c37BXSWzQhpfDbDz64FbCG+OhQhpYYoWddBmD +CK9ZkPiZvWfTSuoOycphig2KQsyQ6S7CVHN/Xq+N4jLLRSDWGU1bdzHMDy3Afg== -----END CERTIFICATE----- Binary files /tmp/MslfMd0v5_/mysql-5.5-5.5.35+dfsg/extra/yassl/certs/client-key.der and /tmp/NaaegeSpl1/mysql-5.5-5.5.43/extra/yassl/certs/client-key.der differ diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/certs/client-keyEnc.pem mysql-5.5-5.5.43/extra/yassl/certs/client-keyEnc.pem --- mysql-5.5-5.5.35+dfsg/extra/yassl/certs/client-keyEnc.pem 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/certs/client-keyEnc.pem 2015-02-27 08:30:34.000000000 +0000 @@ -1,12 +1,12 @@ -----BEGIN RSA PRIVATE KEY----- Proc-Type: 4,ENCRYPTED -DEK-Info: DES-CBC,B9D8FB94E38635AB +DEK-Info: DES-EDE3-CBC,BDE979D13CCC0ABD -e7bVyzL1RF6p7hl8GDaOrRTcgB4ip+pWWUcnNf6y2tsuAQx/c/Bd5c9ZDc3L5AXC -oOAzWYB+ay1vWkmAQB4ivFS5QzGDf8870d4FbOejwmgPhiHdZNw5xNwscAN6ps0v -dFaUrR9nzWmbycsQCjXZGIZtGFCtXkA8Gdl5OMO4o+rzM0muNPS5fb++x7oNl1YG -gjReu2sQ85dPfMlnoHhr8Pz9LBcxVyOmcqtmT0SOSuPcoj6aDtcZ+EY9MQf6SR9E -ysmrJKMtp+ABgXglAj5hbT0dMpoJ2KpJYk62JAh/A6DDyv5YYUI0W57xY5+QzaV+ -YXnIvqwLjJ3cXEV4YH7ozLHAESgnAAUoQsin42rrRKt7GxjSdBoFhWjH69V2nl65 -LYRNjE1O5BBEX+rz0S+fe2ZZgT17kUr7eLZCq15J+L5xWQ7R4ERc0w== +N7yz2JV13EmQ7MZPL5wamid5+G1V1gp8FKqMemAC5JDxonS/W9oViMLUcxbfPTDx +FznKdYSVTIQ7vv3ofmDG4MEyV/2C568N2kdtAw+jTfrZFN+IU9CI+W+In/nacirF +02sAcvDMofustnooKNOO7/iyb5+3vRvEt5vSSRQn5WuSQ9sUKjuzoLs/lbf7fyAt +4NeqfI3rYBZXxiUOLITOGXzGNRuFoY+o2uDCfelLAJ8uhiVG6ME3LeJEo1dT5lZ8 +CSJOLPasKg0iG4V7olM4j9FvAfZr48RRsSfUen756Jo2HpI4bad8LKhFYIdNs2Au +WwKLmjpo6QB9hBmRshR04rEXPdrgTqLBExCE08PyaGYnWU8ggWritCeBzDQFj/n4 +sI+NO0Mymuvg98e5RpO52lg3Xnqv9RIK3guLFOmI6aEHC0PS4WwOEQ== -----END RSA PRIVATE KEY----- diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/certs/client-key.pem mysql-5.5-5.5.43/extra/yassl/certs/client-key.pem --- mysql-5.5-5.5.35+dfsg/extra/yassl/certs/client-key.pem 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/certs/client-key.pem 2015-02-27 08:30:34.000000000 +0000 @@ -1,9 +1,27 @@ -----BEGIN RSA PRIVATE KEY----- -MIIBPAIBAAJBAL1RShT9ahmEDDM4/CcynJcL/KQYYGlO2dh4UAvpIF3WHXAcDCSf -I4LMOgHVlxeyc2yGz7Xx5c5oDNmiEjl88lMCAwEAAQJAVGHWLlLhpqvXsEEXCvWh -HCYono+K8YVGzhiaPSTU212fCoQryIxsXQKGBjhFdZm96DZWp+Vd/t/u+B4ZeaqY -+QIhAOBEfbFtdZqk5OmbbRsRVPI7+YYmubgY1TVIPqmxHQ4NAiEA2BrTQkjOb3ul -A/SZO04fJUZsm7Ng92FWHDJsRancSd8CIQCmGbQqZBK1TamJZ6dAY+7RViAx/p6Q -vjuzMeXPUrFdRQIhAMkfBhg9bCqjFyt8PBPOm/vz8+ZgZlE0/JAXeV7IPCVfAiEA -gZwCFm1ghGxmaoB424YC4DHeDeN/g9xwJHT7EuM9Mvc= +MIIEpAIBAAKCAQEAwwPRK/45pDJFO1PIhCsqfHSavaoqUgdH1qY2sgcyjtC6aXvG +w0Se1IFI/S1oootnu6F1yDYsStIb94u6zw357+zxgR57mwNHmr9lzH9lJGmm6BSJ +W+Q098WwFJP1Z3s6enjhAVZWkaYTQo3SPECcTO/Rht83URsMoTv18aNKNeThzpbf +G36/TpfQEOioCDCBryALQxTFdGe0MoJvjYbCiECZNoO6HkByIhfXUmUkc7DO7xnN +rv94bHvAEgPUTnINUG07ozujmV6dyNkMhbPZitlUJttt+qy7/yVMxNF59HHThkAY +E7BjtXJOMMSXhIYtVi/XFfd/wK71/Fvl+6G60wIDAQABAoIBAQCi5thfEHFkCJ4u +bdFtHoXSCrGMR84sUWqgEp5T3pFMHW3qWXvyd6rZxtmKq9jhFuRjJv+1bBNZuOOl +yHIXLgyfb+VZP3ZvSbERwlouFikN3reO3EDVou7gHqH0vpfbhmOWFM2YCWAtMHac +PM3miO5HknkLWgDiXl8RfH35CLcgBokqXf0AqyLh8LO8JKleJg4fAC3+IZpTW23T +K6uUgmhDNtj2L8Yi/LVBXQ0zYOqkfX7oS1WRVtNcV48flBcvqt7pnqj0z4pMjqDk +VnOyz0+GxWk88yQgi1yWDPprEjuaZ8HfxpaypdWSDZsJQmgkEEXUUOQXOUjQNYuU +bRHej8pZAoGBAOokp/lpM+lx3FJ9iCEoL0neunIW6cxHeogNlFeEWBY6gbA/os+m +bB6wBikAj+d3dqzbysfZXps/JpBSrvw4kAAUu7QPWJTnL2p+HE9BIdQxWR9OihqN +p1dsItjl9H4yphDLZKVVA4emJwWMw9e2J7JNujDaR49U0z2LhI2UmFilAoGBANU4 +G8OPxZMMRwtvNZLFsI1GyJIYj/WACvfvof6AubUqusoYsF2lB9CTjdicBBzUYo6m +JoEB/86KKmM0NUCqbYDeiSNqV02ebq2TTlaQC22dc4sMric93k7wqsVseGdslFKc +N2dsLe+7r9+mkDzER8+Nlp6YqbSfxaZQ3LPw+3QXAoGAXoMJYr26fKK/QnT1fBzS +ackEDYV+Pj0kEsMYe/Mp818OdmxZdeRBhGmdMvPNIquwNbpKsjzl2Vi2Yk9d3uWe +CspTsiz3nrNrClt5ZexukU6SIPb8/Bbt03YM4ux/smkTa3gOWkZktF63JaBadTpL +78c8Pvf9JrggxJkKmnO+wxkCgYEAukSTFKw0GTtfkWCs97TWgQU2UVM96GXcry7c +YT7Jfbh/h/A7mwOCKTfOck4R1bHBDAegmZFKjX/sec/xObXphexi99p9vGRNIjwO +8tZR9YfYmcARIF0PKf1b4q7ZHNkhVm38hNBf7RAVHBgh58Q9S9fQnmqVzyLJA3ue +42AB/C8CgYAR0EvPG2e5nxB1R4ZlrjHCxjCsWQZQ2Q+1cAb38NPIYnyo2m72IT/T +f1/qiqs/2Spe81HSwjA34y2jdQ0eTSE01VdwXIm/cuxKbmjVzRh0M06MOkWP5pZA +62P5GYY6Ud2JS7Dz+Z9dKJU4vjWrylznk1M0oUVdEzllQkahn831vw== -----END RSA PRIVATE KEY----- Binary files /tmp/MslfMd0v5_/mysql-5.5-5.5.35+dfsg/extra/yassl/certs/dsa1024.der and /tmp/NaaegeSpl1/mysql-5.5-5.5.43/extra/yassl/certs/dsa1024.der differ diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/certs/dsa1024.pem mysql-5.5-5.5.43/extra/yassl/certs/dsa1024.pem --- mysql-5.5-5.5.35+dfsg/extra/yassl/certs/dsa1024.pem 1970-01-01 00:00:00.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/certs/dsa1024.pem 2015-02-27 08:30:34.000000000 +0000 @@ -0,0 +1,12 @@ +-----BEGIN DSA PRIVATE KEY----- +MIIBvAIBAAKBgQC9Ue5KMuCKx+rG4epwxFFDzyoH4ccSwlglXsRdvqswDRK/oQvT +NNNoWiVxTn3kvQ8qDlhWy9KjGTrqr/ttgmh56FFpe6tz4yTgCNyR9D+eGclD7lNf +dPUc4E3SA6efopG6+ymI55bS+9xUFTG402UCrYSKT59zI2HBfuI6dltsxQIVAJHJ +7WDQ+jBn/nmMyCQzdi+0qJx1AoGBAJJacRK36s5yGY1b6qhxWqvpoAC+SfEKylZn +YWGYf2PM+Iwo6AgPKEw6BSsX+7Nmc4Gjyr4JWhComKi6onPamO/A2CbMM0DCxb47 +BeLBWfqWAgXVj0CODT4MQos5yugnviR/YpEgbzLxvrXr469lKWsAyB19/gFmGmQW +cCgAwGm6AoGBAJ3LY89yHyvQ/TsQ6zlYbovjbk/ogndsMqPdNUvL4RuPTgJP/caa +DDa0XJ7ak6A7TJ+QheLNwOXoZPYJC4EGFSDAXpYniGhbWIrVTCGe6lmZDfnx40WX +S0kk3m/DHaC03ElLAiybxVGxyqoUfbT3Zv1JwftWMuiqHH5uADhdXuXVAhQ01VXa +Rr8IPem35lKghVKnq/kGQw== +-----END DSA PRIVATE KEY----- Binary files /tmp/MslfMd0v5_/mysql-5.5-5.5.35+dfsg/extra/yassl/certs/dsa512.der and /tmp/NaaegeSpl1/mysql-5.5-5.5.43/extra/yassl/certs/dsa512.der differ diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/certs/dsa512.pem mysql-5.5-5.5.43/extra/yassl/certs/dsa512.pem --- mysql-5.5-5.5.35+dfsg/extra/yassl/certs/dsa512.pem 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/certs/dsa512.pem 1970-01-01 00:00:00.000000000 +0000 @@ -1,8 +0,0 @@ ------BEGIN DSA PRIVATE KEY----- -MIH3AgEAAkEAmSlpgMk8mGhFqYL+Z+uViMW0DNYmRZUZLKAgW37faencww/zYQol -m/IhAWrNqow358pm21b0D3160Ri5Qv0bEQIVAK0lKasKnwkcwa0DIHZ/prfdTQMJ -AkASiJna59ALk5vm7jwhf5yztI2ljOI3gD8X0YFPvfBxtjIIVN2/AeKzdwZkdYoE -1nk5sQIDA8YGdOWQBQoQRhkxAkAEhKAmMXIM6E9dUxdisYDKwBZfwx7qxdmYOPm+ -VlNHaM4IIlccuw13kc9bNu3zJIKQis2QfNt3+Rctc3Pvu7mCAhQjg+e+aqykxwwc -E2V27tjDFY02uA== ------END DSA PRIVATE KEY----- diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/certs/dsa-cert.pem mysql-5.5-5.5.43/extra/yassl/certs/dsa-cert.pem --- mysql-5.5-5.5.35+dfsg/extra/yassl/certs/dsa-cert.pem 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/certs/dsa-cert.pem 2015-02-27 08:30:34.000000000 +0000 @@ -1,70 +1,22 @@ -Certificate: - Data: - Version: 3 (0x2) - Serial Number: - ce:df:23:31:64:b4:13:da - Signature Algorithm: dsaWithSHA1 - Issuer: C=US, ST=Oregon, L=Portland, O=yaSSL, OU=testing, CN=www.yassl.com/emailAddress=info@yassl.com - Validity - Not Before: Jun 30 18:56:38 2010 GMT - Not After : Mar 26 18:56:39 2013 GMT - Subject: C=US, ST=Oregon, L=Portland, O=yaSSL, OU=testing, CN=www.yassl.com/emailAddress=info@yassl.com - Subject Public Key Info: - Public Key Algorithm: dsaEncryption - DSA Public Key: - pub: - 04:84:a0:26:31:72:0c:e8:4f:5d:53:17:62:b1:80: - ca:c0:16:5f:c3:1e:ea:c5:d9:98:38:f9:be:56:53: - 47:68:ce:08:22:57:1c:bb:0d:77:91:cf:5b:36:ed: - f3:24:82:90:8a:cd:90:7c:db:77:f9:17:2d:73:73: - ef:bb:b9:82 - P: - 00:99:29:69:80:c9:3c:98:68:45:a9:82:fe:67:eb: - 95:88:c5:b4:0c:d6:26:45:95:19:2c:a0:20:5b:7e: - df:69:e9:dc:c3:0f:f3:61:0a:25:9b:f2:21:01:6a: - cd:aa:8c:37:e7:ca:66:db:56:f4:0f:7d:7a:d1:18: - b9:42:fd:1b:11 - Q: - 00:ad:25:29:ab:0a:9f:09:1c:c1:ad:03:20:76:7f: - a6:b7:dd:4d:03:09 - G: - 12:88:99:da:e7:d0:0b:93:9b:e6:ee:3c:21:7f:9c: - b3:b4:8d:a5:8c:e2:37:80:3f:17:d1:81:4f:bd:f0: - 71:b6:32:08:54:dd:bf:01:e2:b3:77:06:64:75:8a: - 04:d6:79:39:b1:02:03:03:c6:06:74:e5:90:05:0a: - 10:46:19:31 - X509v3 extensions: - X509v3 Subject Key Identifier: - BE:F9:8C:5D:D6:1C:B4:EE:81:DD:36:56:0A:21:E4:61:44:73:E9:E2 - X509v3 Authority Key Identifier: - keyid:BE:F9:8C:5D:D6:1C:B4:EE:81:DD:36:56:0A:21:E4:61:44:73:E9:E2 - DirName:/C=US/ST=Oregon/L=Portland/O=yaSSL/OU=testing/CN=www.yassl.com/emailAddress=info@yassl.com - serial:CE:DF:23:31:64:B4:13:DA - - X509v3 Basic Constraints: - CA:TRUE - Signature Algorithm: dsaWithSHA1 - 30:2d:02:14:00:a3:21:20:34:6a:2c:f9:fb:76:d7:20:c9:c0: - 35:1b:64:9a:c2:83:02:15:00:a4:59:ac:6d:da:85:48:ff:f5: - 0d:49:72:c8:cd:91:fc:ec:2f:5c:63 -----BEGIN CERTIFICATE----- -MIIDfjCCAz2gAwIBAgIJAM7fIzFktBPaMAkGByqGSM44BAMwgYoxCzAJBgNVBAYT -AlVTMQ8wDQYDVQQIEwZPcmVnb24xETAPBgNVBAcTCFBvcnRsYW5kMQ4wDAYDVQQK -EwV5YVNTTDEQMA4GA1UECxMHdGVzdGluZzEWMBQGA1UEAxMNd3d3Lnlhc3NsLmNv -bTEdMBsGCSqGSIb3DQEJARYOaW5mb0B5YXNzbC5jb20wHhcNMTAwNjMwMTg1NjM4 -WhcNMTMwMzI2MTg1NjM5WjCBijELMAkGA1UEBhMCVVMxDzANBgNVBAgTBk9yZWdv -bjERMA8GA1UEBxMIUG9ydGxhbmQxDjAMBgNVBAoTBXlhU1NMMRAwDgYDVQQLEwd0 -ZXN0aW5nMRYwFAYDVQQDEw13d3cueWFzc2wuY29tMR0wGwYJKoZIhvcNAQkBFg5p -bmZvQHlhc3NsLmNvbTCB8DCBqAYHKoZIzjgEATCBnAJBAJkpaYDJPJhoRamC/mfr -lYjFtAzWJkWVGSygIFt+32np3MMP82EKJZvyIQFqzaqMN+fKZttW9A99etEYuUL9 -GxECFQCtJSmrCp8JHMGtAyB2f6a33U0DCQJAEoiZ2ufQC5Ob5u48IX+cs7SNpYzi -N4A/F9GBT73wcbYyCFTdvwHis3cGZHWKBNZ5ObECAwPGBnTlkAUKEEYZMQNDAAJA -BISgJjFyDOhPXVMXYrGAysAWX8Me6sXZmDj5vlZTR2jOCCJXHLsNd5HPWzbt8ySC -kIrNkHzbd/kXLXNz77u5gqOB8jCB7zAdBgNVHQ4EFgQUvvmMXdYctO6B3TZWCiHk -YURz6eIwgb8GA1UdIwSBtzCBtIAUvvmMXdYctO6B3TZWCiHkYURz6eKhgZCkgY0w -gYoxCzAJBgNVBAYTAlVTMQ8wDQYDVQQIEwZPcmVnb24xETAPBgNVBAcTCFBvcnRs -YW5kMQ4wDAYDVQQKEwV5YVNTTDEQMA4GA1UECxMHdGVzdGluZzEWMBQGA1UEAxMN -d3d3Lnlhc3NsLmNvbTEdMBsGCSqGSIb3DQEJARYOaW5mb0B5YXNzbC5jb22CCQDO -3yMxZLQT2jAMBgNVHRMEBTADAQH/MAkGByqGSM44BAMDMAAwLQIUAKMhIDRqLPn7 -dtcgycA1G2SawoMCFQCkWaxt2oVI//UNSXLIzZH87C9cYw== +MIIDqzCCA2ugAwIBAgIJAMGqrgDU6DyhMAkGByqGSM44BAMwgY4xCzAJBgNVBAYT +AlVTMQ8wDQYDVQQIDAZPcmVnb24xETAPBgNVBAcMCFBvcnRsYW5kMRAwDgYDVQQK +DAd3b2xmU1NMMRAwDgYDVQQLDAd0ZXN0aW5nMRYwFAYDVQQDDA13d3cueWFzc2wu +Y29tMR8wHQYJKoZIhvcNAQkBFhBpbmZvQHdvbGZzc2wuY29tMB4XDTEzMDQyMjIw +MDk0NFoXDTE2MDExNzIwMDk0NFowgY4xCzAJBgNVBAYTAlVTMQ8wDQYDVQQIDAZP +cmVnb24xETAPBgNVBAcMCFBvcnRsYW5kMRAwDgYDVQQKDAd3b2xmU1NMMRAwDgYD +VQQLDAd0ZXN0aW5nMRYwFAYDVQQDDA13d3cueWFzc2wuY29tMR8wHQYJKoZIhvcN +AQkBFhBpbmZvQHdvbGZzc2wuY29tMIIBuDCCASwGByqGSM44BAEwggEfAoGBAL1R +7koy4IrH6sbh6nDEUUPPKgfhxxLCWCVexF2+qzANEr+hC9M002haJXFOfeS9DyoO +WFbL0qMZOuqv+22CaHnoUWl7q3PjJOAI3JH0P54ZyUPuU1909RzgTdIDp5+ikbr7 +KYjnltL73FQVMbjTZQKthIpPn3MjYcF+4jp2W2zFAhUAkcntYND6MGf+eYzIJDN2 +L7SonHUCgYEAklpxErfqznIZjVvqqHFaq+mgAL5J8QrKVmdhYZh/Y8z4jCjoCA8o +TDoFKxf7s2ZzgaPKvglaEKiYqLqic9qY78DYJswzQMLFvjsF4sFZ+pYCBdWPQI4N +PgxCiznK6Ce+JH9ikSBvMvG+tevjr2UpawDIHX3+AWYaZBZwKADAaboDgYUAAoGB +AJ3LY89yHyvQ/TsQ6zlYbovjbk/ogndsMqPdNUvL4RuPTgJP/caaDDa0XJ7ak6A7 +TJ+QheLNwOXoZPYJC4EGFSDAXpYniGhbWIrVTCGe6lmZDfnx40WXS0kk3m/DHaC0 +3ElLAiybxVGxyqoUfbT3Zv1JwftWMuiqHH5uADhdXuXVo1AwTjAdBgNVHQ4EFgQU +IJjk416o4v8qpH9LBtXlR9v8gccwHwYDVR0jBBgwFoAUIJjk416o4v8qpH9LBtXl +R9v8gccwDAYDVR0TBAUwAwEB/zAJBgcqhkjOOAQDAy8AMCwCFCjGKIdOSV12LcTu +k08owGM6YkO1AhQe+K173VuaO/OsDNsxZlKpyH8+1g== -----END CERTIFICATE----- diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/certs/server-cert.pem mysql-5.5-5.5.43/extra/yassl/certs/server-cert.pem --- mysql-5.5-5.5.35+dfsg/extra/yassl/certs/server-cert.pem 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/certs/server-cert.pem 2015-02-27 08:30:34.000000000 +0000 @@ -1,39 +1,173 @@ Certificate: Data: - Version: 1 (0x0) + Version: 3 (0x2) Serial Number: 1 (0x1) - Signature Algorithm: md5WithRSAEncryption - Issuer: C=US, ST=Montana, L=Bozeman, O=sawtooth, OU=consulting, CN=www.sawtooth-consulting.com/emailAddress=info@yassl.com + Signature Algorithm: sha1WithRSAEncryption + Issuer: C=US, ST=Montana, L=Bozeman, O=Sawtooth, OU=Consulting, CN=www.wolfssl.com/emailAddress=info@wolfssl.com Validity - Not Before: Jun 30 18:52:17 2010 GMT - Not After : Mar 26 18:52:17 2013 GMT - Subject: C=US, ST=Montana, L=Bozeman, O=yaSSL, OU=support, CN=www.yassl.com/emailAddress=info@yassl.com + Not Before: Jul 11 17:20:14 2014 GMT + Not After : Apr 6 17:20:14 2017 GMT + Subject: C=US, ST=Montana, L=Bozeman, O=wolfSSL, OU=Support, CN=www.wolfssl.com/emailAddress=info@wolfssl.com Subject Public Key Info: Public Key Algorithm: rsaEncryption - RSA Public Key: (512 bit) - Modulus (512 bit): - 00:c6:7b:c0:68:81:2f:de:82:3f:f9:ac:c3:86:4a: - 66:b7:ec:d4:f1:f6:64:21:ff:f5:a2:34:42:d0:38: - 9f:c6:dd:3b:6e:26:65:6a:54:96:dd:d2:7b:eb:36: - a2:ae:7e:2a:9e:7e:56:a5:b6:87:9f:15:c7:18:66: - 7e:16:77:e2:a7 + Public-Key: (2048 bit) + Modulus: + 00:c0:95:08:e1:57:41:f2:71:6d:b7:d2:45:41:27: + 01:65:c6:45:ae:f2:bc:24:30:b8:95:ce:2f:4e:d6: + f6:1c:88:bc:7c:9f:fb:a8:67:7f:fe:5c:9c:51:75: + f7:8a:ca:07:e7:35:2f:8f:e1:bd:7b:c0:2f:7c:ab: + 64:a8:17:fc:ca:5d:7b:ba:e0:21:e5:72:2e:6f:2e: + 86:d8:95:73:da:ac:1b:53:b9:5f:3f:d7:19:0d:25: + 4f:e1:63:63:51:8b:0b:64:3f:ad:43:b8:a5:1c:5c: + 34:b3:ae:00:a0:63:c5:f6:7f:0b:59:68:78:73:a6: + 8c:18:a9:02:6d:af:c3:19:01:2e:b8:10:e3:c6:cc: + 40:b4:69:a3:46:33:69:87:6e:c4:bb:17:a6:f3:e8: + dd:ad:73:bc:7b:2f:21:b5:fd:66:51:0c:bd:54:b3: + e1:6d:5f:1c:bc:23:73:d1:09:03:89:14:d2:10:b9: + 64:c3:2a:d0:a1:96:4a:bc:e1:d4:1a:5b:c7:a0:c0: + c1:63:78:0f:44:37:30:32:96:80:32:23:95:a1:77: + ba:13:d2:97:73:e2:5d:25:c9:6a:0d:c3:39:60:a4: + b4:b0:69:42:42:09:e9:d8:08:bc:33:20:b3:58:22: + a7:aa:eb:c4:e1:e6:61:83:c5:d2:96:df:d9:d0:4f: + ad:d7 Exponent: 65537 (0x10001) - Signature Algorithm: md5WithRSAEncryption - 58:a9:98:e7:16:52:4c:40:e7:e1:47:92:19:1b:3a:8f:97:6c: - 7b:b7:b0:cb:20:6d:ad:b5:d3:47:58:d8:e4:f2:3e:32:e9:ef: - 87:77:e5:54:36:f4:8d:50:8d:07:b4:77:45:ea:9d:a4:33:36: - 9b:0b:e0:74:58:11:c5:01:7b:4d + X509v3 extensions: + X509v3 Subject Key Identifier: + B3:11:32:C9:92:98:84:E2:C9:F8:D0:3B:6E:03:42:CA:1F:0E:8E:3C + X509v3 Authority Key Identifier: + keyid:27:8E:67:11:74:C3:26:1D:3F:ED:33:63:B3:A4:D8:1D:30:E5:E8:D5 + DirName:/C=US/ST=Montana/L=Bozeman/O=Sawtooth/OU=Consulting/CN=www.wolfssl.com/emailAddress=info@wolfssl.com + serial:9A:41:47:CD:A1:14:62:8C + + X509v3 Basic Constraints: + CA:TRUE + Signature Algorithm: sha1WithRSAEncryption + 3d:8c:70:05:5b:62:4b:bf:6c:b6:48:61:01:10:1d:5e:05:ba: + 55:94:2c:ae:59:6f:97:80:5d:6c:86:ec:9a:eb:15:45:44:e4: + 56:f8:75:ca:8a:45:32:f4:c7:e1:fa:f2:98:1c:91:d3:3f:e8: + 0e:c9:1b:fa:e1:79:99:67:0e:0d:6b:8a:ec:1a:2c:59:c4:34: + 04:8d:39:77:cd:b5:e9:60:5b:82:bf:34:ce:ed:c6:4f:3f:b4: + 5c:4d:8a:b4:f4:0a:04:12:a0:56:c1:e1:33:37:a1:54:87:48: + e9:81:c2:0f:8f:6f:d3:52:4c:4c:32:4c:6b:9f:3a:04:8f:77: + 5d:ad:dc:3d:2b:f2:c9:df:3c:60:5d:d8:fc:86:72:7c:3d:d0: + 84:4b:8c:df:26:43:fe:c0:cc:5b:e1:36:b3:3d:32:28:a3:ef: + 0c:20:d6:b1:50:39:d6:67:a9:8b:84:bc:92:34:eb:19:23:e8: + 10:8f:ea:bd:18:8c:93:27:3c:74:75:8e:58:04:fa:2a:74:44: + 7d:fc:4d:39:df:54:17:ba:78:e1:5d:6a:70:d3:7c:a2:80:81: + e6:19:51:91:c3:44:51:ec:bb:88:a9:53:e1:d7:a9:8c:28:f4: + 21:1c:42:51:09:b4:12:6d:a0:d6:25:09:85:c6:2a:0c:af:a7: + 58:e6:52:8b -----BEGIN CERTIFICATE----- -MIICFDCCAb4CAQEwDQYJKoZIhvcNAQEEBQAwgZ4xCzAJBgNVBAYTAlVTMRAwDgYD -VQQIEwdNb250YW5hMRAwDgYDVQQHEwdCb3plbWFuMREwDwYDVQQKEwhzYXd0b290 -aDETMBEGA1UECxMKY29uc3VsdGluZzEkMCIGA1UEAxMbd3d3LnNhd3Rvb3RoLWNv -bnN1bHRpbmcuY29tMR0wGwYJKoZIhvcNAQkBFg5pbmZvQHlhc3NsLmNvbTAeFw0x -MDA2MzAxODUyMTdaFw0xMzAzMjYxODUyMTdaMIGKMQswCQYDVQQGEwJVUzEQMA4G -A1UECBMHTW9udGFuYTEQMA4GA1UEBxMHQm96ZW1hbjEOMAwGA1UEChMFeWFTU0wx -EDAOBgNVBAsTB3N1cHBvcnQxFjAUBgNVBAMTDXd3dy55YXNzbC5jb20xHTAbBgkq -hkiG9w0BCQEWDmluZm9AeWFzc2wuY29tMFwwDQYJKoZIhvcNAQEBBQADSwAwSAJB -AMZ7wGiBL96CP/msw4ZKZrfs1PH2ZCH/9aI0QtA4n8bdO24mZWpUlt3Se+s2oq5+ -Kp5+VqW2h58VxxhmfhZ34qcCAwEAATANBgkqhkiG9w0BAQQFAANBAFipmOcWUkxA -5+FHkhkbOo+XbHu3sMsgba2100dY2OTyPjLp74d35VQ29I1QjQe0d0XqnaQzNpsL -4HRYEcUBe00= +MIIEnjCCA4agAwIBAgIBATANBgkqhkiG9w0BAQUFADCBlDELMAkGA1UEBhMCVVMx +EDAOBgNVBAgMB01vbnRhbmExEDAOBgNVBAcMB0JvemVtYW4xETAPBgNVBAoMCFNh +d3Rvb3RoMRMwEQYDVQQLDApDb25zdWx0aW5nMRgwFgYDVQQDDA93d3cud29sZnNz +bC5jb20xHzAdBgkqhkiG9w0BCQEWEGluZm9Ad29sZnNzbC5jb20wHhcNMTQwNzEx +MTcyMDE0WhcNMTcwNDA2MTcyMDE0WjCBkDELMAkGA1UEBhMCVVMxEDAOBgNVBAgM +B01vbnRhbmExEDAOBgNVBAcMB0JvemVtYW4xEDAOBgNVBAoMB3dvbGZTU0wxEDAO +BgNVBAsMB1N1cHBvcnQxGDAWBgNVBAMMD3d3dy53b2xmc3NsLmNvbTEfMB0GCSqG +SIb3DQEJARYQaW5mb0B3b2xmc3NsLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEP +ADCCAQoCggEBAMCVCOFXQfJxbbfSRUEnAWXGRa7yvCQwuJXOL07W9hyIvHyf+6hn +f/5cnFF194rKB+c1L4/hvXvAL3yrZKgX/Mpde7rgIeVyLm8uhtiVc9qsG1O5Xz/X +GQ0lT+FjY1GLC2Q/rUO4pRxcNLOuAKBjxfZ/C1loeHOmjBipAm2vwxkBLrgQ48bM +QLRpo0YzaYduxLsXpvPo3a1zvHsvIbX9ZlEMvVSz4W1fHLwjc9EJA4kU0hC5ZMMq +0KGWSrzh1Bpbx6DAwWN4D0Q3MDKWgDIjlaF3uhPSl3PiXSXJag3DOWCktLBpQkIJ +6dgIvDMgs1gip6rrxOHmYYPF0pbf2dBPrdcCAwEAAaOB/DCB+TAdBgNVHQ4EFgQU +sxEyyZKYhOLJ+NA7bgNCyh8OjjwwgckGA1UdIwSBwTCBvoAUJ45nEXTDJh0/7TNj +s6TYHTDl6NWhgZqkgZcwgZQxCzAJBgNVBAYTAlVTMRAwDgYDVQQIDAdNb250YW5h +MRAwDgYDVQQHDAdCb3plbWFuMREwDwYDVQQKDAhTYXd0b290aDETMBEGA1UECwwK +Q29uc3VsdGluZzEYMBYGA1UEAwwPd3d3LndvbGZzc2wuY29tMR8wHQYJKoZIhvcN +AQkBFhBpbmZvQHdvbGZzc2wuY29tggkAmkFHzaEUYowwDAYDVR0TBAUwAwEB/zAN +BgkqhkiG9w0BAQUFAAOCAQEAPYxwBVtiS79stkhhARAdXgW6VZQsrllvl4BdbIbs +musVRUTkVvh1yopFMvTH4frymByR0z/oDskb+uF5mWcODWuK7BosWcQ0BI05d821 +6WBbgr80zu3GTz+0XE2KtPQKBBKgVsHhMzehVIdI6YHCD49v01JMTDJMa586BI93 +Xa3cPSvyyd88YF3Y/IZyfD3QhEuM3yZD/sDMW+E2sz0yKKPvDCDWsVA51mepi4S8 +kjTrGSPoEI/qvRiMkyc8dHWOWAT6KnREffxNOd9UF7p44V1qcNN8ooCB5hlRkcNE +Uey7iKlT4depjCj0IRxCUQm0Em2g1iUJhcYqDK+nWOZSiw== +-----END CERTIFICATE----- +Certificate: + Data: + Version: 3 (0x2) + Serial Number: + 9a:41:47:cd:a1:14:62:8c + Signature Algorithm: sha1WithRSAEncryption + Issuer: C=US, ST=Montana, L=Bozeman, O=Sawtooth, OU=Consulting, CN=www.wolfssl.com/emailAddress=info@wolfssl.com + Validity + Not Before: Jul 11 03:20:08 2014 GMT + Not After : Apr 6 03:20:08 2017 GMT + Subject: C=US, ST=Montana, L=Bozeman, O=Sawtooth, OU=Consulting, CN=www.wolfssl.com/emailAddress=info@wolfssl.com + Subject Public Key Info: + Public Key Algorithm: rsaEncryption + Public-Key: (2048 bit) + Modulus: + 00:bf:0c:ca:2d:14:b2:1e:84:42:5b:cd:38:1f:4a: + f2:4d:75:10:f1:b6:35:9f:df:ca:7d:03:98:d3:ac: + de:03:66:ee:2a:f1:d8:b0:7d:6e:07:54:0b:10:98: + 21:4d:80:cb:12:20:e7:cc:4f:de:45:7d:c9:72:77: + 32:ea:ca:90:bb:69:52:10:03:2f:a8:f3:95:c5:f1: + 8b:62:56:1b:ef:67:6f:a4:10:41:95:ad:0a:9b:e3: + a5:c0:b0:d2:70:76:50:30:5b:a8:e8:08:2c:7c:ed: + a7:a2:7a:8d:38:29:1c:ac:c7:ed:f2:7c:95:b0:95: + 82:7d:49:5c:38:cd:77:25:ef:bd:80:75:53:94:3c: + 3d:ca:63:5b:9f:15:b5:d3:1d:13:2f:19:d1:3c:db: + 76:3a:cc:b8:7d:c9:e5:c2:d7:da:40:6f:d8:21:dc: + 73:1b:42:2d:53:9c:fe:1a:fc:7d:ab:7a:36:3f:98: + de:84:7c:05:67:ce:6a:14:38:87:a9:f1:8c:b5:68: + cb:68:7f:71:20:2b:f5:a0:63:f5:56:2f:a3:26:d2: + b7:6f:b1:5a:17:d7:38:99:08:fe:93:58:6f:fe:c3: + 13:49:08:16:0b:a7:4d:67:00:52:31:67:23:4e:98: + ed:51:45:1d:b9:04:d9:0b:ec:d8:28:b3:4b:bd:ed: + 36:79 + Exponent: 65537 (0x10001) + X509v3 extensions: + X509v3 Subject Key Identifier: + 27:8E:67:11:74:C3:26:1D:3F:ED:33:63:B3:A4:D8:1D:30:E5:E8:D5 + X509v3 Authority Key Identifier: + keyid:27:8E:67:11:74:C3:26:1D:3F:ED:33:63:B3:A4:D8:1D:30:E5:E8:D5 + DirName:/C=US/ST=Montana/L=Bozeman/O=Sawtooth/OU=Consulting/CN=www.wolfssl.com/emailAddress=info@wolfssl.com + serial:9A:41:47:CD:A1:14:62:8C + + X509v3 Basic Constraints: + CA:TRUE + Signature Algorithm: sha1WithRSAEncryption + 79:78:0c:6d:79:88:91:fc:3a:15:9c:f9:27:62:16:f0:21:1f: + fa:7d:3f:a2:a8:32:1e:f7:f2:11:a9:74:16:74:5e:dc:18:ca: + f0:00:2a:d5:03:06:26:30:f1:47:83:fd:32:6e:fc:ed:aa:4f: + 7d:0c:63:60:31:2f:7c:0c:bf:99:66:87:ed:27:08:86:2d:c4: + 33:e8:98:23:1c:fe:a3:db:9a:49:4e:fc:5a:42:ef:71:c3:3f: + ad:dc:4a:a8:d2:a3:1d:09:ac:33:04:7b:86:f3:6d:00:59:a3: + c8:db:d1:3c:73:f6:0e:90:d6:5e:49:e0:bf:36:63:08:7b:a5: + b0:8f:35:3b:56:8c:11:35:49:04:1c:d0:e7:ba:56:c5:0d:0a: + 91:8d:d6:b7:62:19:34:12:52:4c:d2:6d:7c:c5:3d:0f:18:81: + 54:cb:f6:3c:e5:84:d2:d6:71:15:ec:1a:34:0b:f0:a0:21:74: + 43:c8:a3:b0:df:d9:67:da:e2:ad:93:48:f8:a0:87:bd:79:14: + e0:62:0a:df:f7:31:2e:31:7b:d1:32:2a:0a:fe:5d:14:ef:d9: + 64:50:e4:83:91:bc:70:0d:d7:88:8d:d9:bc:84:0e:c5:1a:b3: + bf:64:02:4e:51:91:a4:a2:85:15:83:af:f0:5b:9b:28:49:5f: + b2:b3:03:d8 +-----BEGIN CERTIFICATE----- +MIIEqjCCA5KgAwIBAgIJAJpBR82hFGKMMA0GCSqGSIb3DQEBBQUAMIGUMQswCQYD +VQQGEwJVUzEQMA4GA1UECAwHTW9udGFuYTEQMA4GA1UEBwwHQm96ZW1hbjERMA8G +A1UECgwIU2F3dG9vdGgxEzARBgNVBAsMCkNvbnN1bHRpbmcxGDAWBgNVBAMMD3d3 +dy53b2xmc3NsLmNvbTEfMB0GCSqGSIb3DQEJARYQaW5mb0B3b2xmc3NsLmNvbTAe +Fw0xNDA3MTEwMzIwMDhaFw0xNzA0MDYwMzIwMDhaMIGUMQswCQYDVQQGEwJVUzEQ +MA4GA1UECAwHTW9udGFuYTEQMA4GA1UEBwwHQm96ZW1hbjERMA8GA1UECgwIU2F3 +dG9vdGgxEzARBgNVBAsMCkNvbnN1bHRpbmcxGDAWBgNVBAMMD3d3dy53b2xmc3Ns +LmNvbTEfMB0GCSqGSIb3DQEJARYQaW5mb0B3b2xmc3NsLmNvbTCCASIwDQYJKoZI +hvcNAQEBBQADggEPADCCAQoCggEBAL8Myi0Ush6EQlvNOB9K8k11EPG2NZ/fyn0D +mNOs3gNm7irx2LB9bgdUCxCYIU2AyxIg58xP3kV9yXJ3MurKkLtpUhADL6jzlcXx +i2JWG+9nb6QQQZWtCpvjpcCw0nB2UDBbqOgILHztp6J6jTgpHKzH7fJ8lbCVgn1J +XDjNdyXvvYB1U5Q8PcpjW58VtdMdEy8Z0TzbdjrMuH3J5cLX2kBv2CHccxtCLVOc +/hr8fat6Nj+Y3oR8BWfOahQ4h6nxjLVoy2h/cSAr9aBj9VYvoybSt2+xWhfXOJkI +/pNYb/7DE0kIFgunTWcAUjFnI06Y7VFFHbkE2Qvs2CizS73tNnkCAwEAAaOB/DCB ++TAdBgNVHQ4EFgQUJ45nEXTDJh0/7TNjs6TYHTDl6NUwgckGA1UdIwSBwTCBvoAU +J45nEXTDJh0/7TNjs6TYHTDl6NWhgZqkgZcwgZQxCzAJBgNVBAYTAlVTMRAwDgYD +VQQIDAdNb250YW5hMRAwDgYDVQQHDAdCb3plbWFuMREwDwYDVQQKDAhTYXd0b290 +aDETMBEGA1UECwwKQ29uc3VsdGluZzEYMBYGA1UEAwwPd3d3LndvbGZzc2wuY29t +MR8wHQYJKoZIhvcNAQkBFhBpbmZvQHdvbGZzc2wuY29tggkAmkFHzaEUYowwDAYD +VR0TBAUwAwEB/zANBgkqhkiG9w0BAQUFAAOCAQEAeXgMbXmIkfw6FZz5J2IW8CEf ++n0/oqgyHvfyEal0FnRe3BjK8AAq1QMGJjDxR4P9Mm787apPfQxjYDEvfAy/mWaH +7ScIhi3EM+iYIxz+o9uaSU78WkLvccM/rdxKqNKjHQmsMwR7hvNtAFmjyNvRPHP2 +DpDWXkngvzZjCHulsI81O1aMETVJBBzQ57pWxQ0KkY3Wt2IZNBJSTNJtfMU9DxiB +VMv2POWE0tZxFewaNAvwoCF0Q8ijsN/ZZ9rirZNI+KCHvXkU4GIK3/cxLjF70TIq +Cv5dFO/ZZFDkg5G8cA3XiI3ZvIQOxRqzv2QCTlGRpKKFFYOv8FubKElfsrMD2A== -----END CERTIFICATE----- diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/certs/server-keyEnc.pem mysql-5.5-5.5.43/extra/yassl/certs/server-keyEnc.pem --- mysql-5.5-5.5.35+dfsg/extra/yassl/certs/server-keyEnc.pem 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/certs/server-keyEnc.pem 2015-02-27 08:30:34.000000000 +0000 @@ -1,12 +1,30 @@ -----BEGIN RSA PRIVATE KEY----- Proc-Type: 4,ENCRYPTED -DEK-Info: DES-CBC,08132C1FFF5BC8CC +DEK-Info: DES-CBC,136C7D8A69656668 -gsvuAsGmB8AkR23M25w4E6wuywfBey1Jqh3g71gJcnsUYwynex9dvfAU0lTowOXh -sb7ld1KNjEMzrht9AC1IC0iE1rLqvRQZOdJ7h3n7aHZQ4a/HjcwAhqJq0ZW45m6Q -mpoO5fRISjx2VbKFRUz6Xj2x0/do3IjQhpuUDVrTFFe1sEySM6APZ6CVpcnTOyPR -ADyLDKzOi2E+sj1UXs58pct56FaqTIZPUEflICU3k6q9FPU6gsYANRLfzegclkv4 -JAx6mKVSJuYnjCCppx8WBwGJa1J1GcYRJ3qFfdbUzL4bcXTvoFkJEnDkHsXgDUS6 -xmT0XGT3IMaW8cwQ8KD8m5YYI/L26Mas/w3eA2ekyMR8pYICjXp/YZtcKxxkQSVE -Uv/+D+20KbNAHIW5Mrxf61cX/CggGEbVP8ZhDY1flh8= +jvNTyPaztxPIoAzbdmZnD0Zw2+60tMxNc0GMHNmeOyG25aHP/dT+TWiKFpFVkkkY +uoCIhYUyw7gmpw+CnRJwWd+ans4nrvAjwy5oWJvarvsyUpjqvnPoIlAqd+d4TDKN +eESzcI76+gHdisAtCrQD+fGqgTZhli5TgDbnpasL/QnY2qDlutvakkVw7gPXe156 +2Phy8WN+efr65J6wt3K/dj7Datl9u4JeHQK81gYyWBVX+EagEjPGDzkFQCj9Z0q7 +8K3iB5GW1JAqJS0IfZPB40AnSTF/n1TL1SN3qfU3l7hTGNrx9o7580bgDEoAR7pI +F8eZlS15KHtZmh11AnU1KTKZ6kmgnNqeMTGMN6N0ct2wMKW1dV87eTDlF0oiR2ol +XwtFgKmrIjfpmzkdWjbJmWnGMjD56KdiFZga/ZyKMsPrVoYLgfJEpn36iQspfygx +HCGNTf0PjIsjEWU0WyQiF86t+c45W3wNFsv/AxVyfMl+su02yrd6u2ecuQDir3Cs +b2k8IKtQgVe/NIpEWLKuiHG5oedIPPQyDYK5uq+gHxCGeOoKnWlsWFEHZRiza4X5 +tbgTrJB8Sw0ENWrvVGGmQZN4pSImlsMwzQ2qik5CQ00N1b3+56/obn0z75I3bUSb +tC5g8DRjl6oclAenNgh/MYMT287y5W2dD4npxHcekX4O3J2CDXNfg4vV2j5GRxtg +LVJdYE2p7bpYePCDHrYng8b9ubBprx0CrEnkIvvtUjzNPf6VDL0+MBKl+XgR2/nz +iRqTuZnlGGOyM+KYDwXpgwfs/HfvFGksxTAlO/40GkGh+WGPaIoNyCK0SgQKhyb4 +JIkR0vd2/yLg3lWMJrGwh7A0Gm07Z/781oURP3uWd+PaCOgGcd5ipcAjcEyuxNly +AthipWqmQWUcbf6Z2N9j3OA22Hv2Uzk8HSfi9VOZtL9svdEEZ0NnOekJgnc6stQp +bXiknlK/T5WdrWxSyCfgUq68Vf6DFfIRAVuFdJ3WHT2wVXHrDfft6D+Ne/XCxPoE +8zGmkyusaph33UHQ1oNyUbLbwcDCDSmOo8gYoedD3IwxtMA3wJRugomqosItwV8X +vkgmcy8eSE/+gZUxJEN2gnLcfKFhCkC80J6oFhmoDD6vuUnPHcFdKZgVPw2rzPk5 +Vb1kX+gpORplYmKpq1vz/ujscL4T0TmYLz02hkIS4edpW55ncTTv7JWefpRiTB1J +RB3td3me4htqR+YIDWJ+emrOmqsCG2WvpAS+MTw2mj1jYk9LL/ZYobTjSCEWmuwT +yVK6m303irR7HQDauxhslRFgoK21w63viOyj5NKIU1gQtaAANGDxcgORC1XLjjgt +oNutSQA+7P42vfHSHK4cnTBXl6V32H/GyVpdHQOZqSrqIjgLmUZodSmRPROxosZF +a46B1O7m/rJFxkiKW4vod+/WqjoE0Hhfrb8rRrkRjzGeCqqSSnQ3vrunVkvF8hlA +b6FOv4ZBJL4piC1GKH+rscqke9NEiDqXN8C3iYz86jbck/Ha21yUS8T3X7N52sg+ +B3AmOGnLK6BebYeto9vZxQjacChJZSixSxLV+l9/nVQ0+mW42azHdzk0ru59TGAj -----END RSA PRIVATE KEY----- diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/certs/server-key.pem mysql-5.5-5.5.43/extra/yassl/certs/server-key.pem --- mysql-5.5-5.5.35+dfsg/extra/yassl/certs/server-key.pem 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/certs/server-key.pem 2015-02-27 08:30:34.000000000 +0000 @@ -1,9 +1,27 @@ -----BEGIN RSA PRIVATE KEY----- -MIIBOwIBAAJBAMZ7wGiBL96CP/msw4ZKZrfs1PH2ZCH/9aI0QtA4n8bdO24mZWpU -lt3Se+s2oq5+Kp5+VqW2h58VxxhmfhZ34qcCAwEAAQJBAJSbGxgjgV+rTZL2Ev58 -viN/IoB25cm/Bn4Heu7DNn2A2kpdGX2cCaf7rEQoIKCiHxvopvxOcd/7nLS/gNli -dCECIQD/cX/9fvB1Uajw0fmvwNON9+3P9uJSqpig90zL32pwjQIhAMbqee9TBMN4 -TxXbgWqA92PrCXe8WDZ3PwoJqdR6MRUDAiEAny+TDF1z6hiWiGTCDgXDkKBlwgjf -p5aKgR077XzwLu0CICVpWEGg1ZaF/CnaPP7w/pZ2UDOK4vRrfRnAM4bY7H5NAiBS -1eXJ/MCZ2uPfpl7XK2BU9P69KdKUk5WHxdRchVvcDg== +MIIEpQIBAAKCAQEAwJUI4VdB8nFtt9JFQScBZcZFrvK8JDC4lc4vTtb2HIi8fJ/7 +qGd//lycUXX3isoH5zUvj+G9e8AvfKtkqBf8yl17uuAh5XIuby6G2JVz2qwbU7lf +P9cZDSVP4WNjUYsLZD+tQ7ilHFw0s64AoGPF9n8LWWh4c6aMGKkCba/DGQEuuBDj +xsxAtGmjRjNph27Euxem8+jdrXO8ey8htf1mUQy9VLPhbV8cvCNz0QkDiRTSELlk +wyrQoZZKvOHUGlvHoMDBY3gPRDcwMpaAMiOVoXe6E9KXc+JdJclqDcM5YKS0sGlC +Qgnp2Ai8MyCzWCKnquvE4eZhg8XSlt/Z0E+t1wIDAQABAoIBAQCa0DQPUmIFUAHv +n+1kbsLE2hryhNeSEEiSxOlq64t1bMZ5OPLJckqGZFSVd8vDmp231B2kAMieTuTd +x7pnFsF0vKnWlI8rMBr77d8hBSPZSjm9mGtlmrjcxH3upkMVLj2+HSJgKnMw1T7Y +oqyGQy7E9WReP4l1DxHYUSVOn9iqo85gs+KK2X4b8GTKmlsFC1uqy+XjP24yIgXz +0PrvdFKB4l90073/MYNFdfpjepcu1rYZxpIm5CgGUFAOeC6peA0Ul7QS2DFAq6EB +QcIw+AdfFuRhd9Jg8p+N6PS662PeKpeB70xs5lU0USsoNPRTHMRYCj+7r7X3SoVD +LTzxWFiBAoGBAPIsVHY5I2PJEDK3k62vvhl1loFk5rW4iUJB0W3QHBv4G6xpyzY8 +ZH3c9Bm4w2CxV0hfUk9ZOlV/MsAZQ1A/rs5vF/MOn0DKTq0VO8l56cBZOHNwnAp8 +yTpIMqfYSXUKhcLC/RVz2pkJKmmanwpxv7AEpox6Wm9IWlQ7xrFTF9/nAoGBAMuT +3ncVXbdcXHzYkKmYLdZpDmOzo9ymzItqpKISjI57SCyySzfcBhh96v52odSh6T8N +zRtfr1+elltbD6F8r7ObkNtXczrtsCNErkFPHwdCEyNMy/r0FKTV9542fFufqDzB +hV900jkt/9CE3/uzIHoumxeu5roLrl9TpFLtG8SRAoGBAOyY2rvV/vlSSn0CVUlv +VW5SL4SjK7OGYrNU0mNS2uOIdqDvixWl0xgUcndex6MEH54ZYrUbG57D8rUy+UzB +qusMJn3UX0pRXKRFBnBEp1bA1CIUdp7YY1CJkNPiv4GVkjFBhzkaQwsYpVMfORpf +H0O8h2rfbtMiAP4imHBOGhkpAoGBAIpBVihRnl/Ungs7mKNU8mxW1KrpaTOFJAza +1AwtxL9PAmk4fNTm3Ezt1xYRwz4A58MmwFEC3rt1nG9WnHrzju/PisUr0toGakTJ +c/5umYf4W77xfOZltU9s8MnF/xbKixsX4lg9ojerAby/QM5TjI7t7+5ZneBj5nxe +9Y5L8TvBAoGATUX5QIzFW/QqGoq08hysa+kMVja3TnKW1eWK0uL/8fEYEz2GCbjY +dqfJHHFSlDBD4PF4dP1hG0wJzOZoKnGtHN9DvFbbpaS+NXCkXs9P/ABVmTo9I89n +WvUi+LUp0EQR6zUuRr79jhiyX6i/GTKh9dwD5nyaHwx8qbAOITc78bA= -----END RSA PRIVATE KEY----- diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/CMakeLists.txt mysql-5.5-5.5.43/extra/yassl/CMakeLists.txt --- mysql-5.5-5.5.35+dfsg/extra/yassl/CMakeLists.txt 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/CMakeLists.txt 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -# Copyright (c) 2006, 2012, Oracle and/or its affiliates. All rights reserved. +# Copyright (c) 2006, 2014, Oracle and/or its affiliates. All rights reserved. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -37,7 +37,6 @@ ADD_CONVENIENCE_LIBRARY(yassl ${YASSL_SOURCES}) RESTRICT_SYMBOL_EXPORTS(yassl) -INSTALL_DEBUG_SYMBOLS(yassl) IF(MSVC) INSTALL_DEBUG_TARGET(yassl DESTINATION ${INSTALL_LIBDIR}/debug) ENDIF() diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/examples/client/client.cpp mysql-5.5-5.5.43/extra/yassl/examples/client/client.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/examples/client/client.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/examples/client/client.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -18,6 +18,10 @@ /* client.cpp */ +// takes an optional command line argument of cipher list to make scripting +// easier + + #include "../../testsuite/test.hpp" //#define TEST_RESUME @@ -73,11 +77,16 @@ #ifdef NON_BLOCKING tcp_set_nonblocking(sockfd); #endif - SSL_METHOD* method = TLSv1_client_method(); SSL_CTX* ctx = SSL_CTX_new(method); set_certs(ctx); + if (argc >= 2) { + printf("setting cipher list to %s\n", argv[1]); + if (SSL_CTX_set_cipher_list(ctx, argv[1]) != SSL_SUCCESS) { + ClientError(ctx, NULL, sockfd, "set_cipher_list error\n"); + } + } SSL* ssl = SSL_new(ctx); SSL_set_fd(ssl, sockfd); diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/examples/server/server.cpp mysql-5.5-5.5.43/extra/yassl/examples/server/server.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/examples/server/server.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/examples/server/server.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -18,6 +18,9 @@ /* server.cpp */ +// takes 2 optional command line argument to make scripting +// if the first command line argument is 'n' client auth is disabled +// if the second command line argument is 'd' DSA certs are used instead of RSA #include "../../testsuite/test.hpp" @@ -69,6 +72,9 @@ char** argv = 0; set_args(argc, argv, *static_cast(args)); +#ifdef SERVER_READY_FILE + set_file_ready("server_ready", *static_cast(args)); +#endif tcp_accept(sockfd, clientfd, *static_cast(args)); tcp_close(sockfd); @@ -77,8 +83,21 @@ SSL_CTX* ctx = SSL_CTX_new(method); //SSL_CTX_set_cipher_list(ctx, "RC4-SHA:RC4-MD5"); - SSL_CTX_set_verify(ctx, SSL_VERIFY_PEER, 0); - set_serverCerts(ctx); + + // should we disable client auth + if (argc >= 2 && argv[1][0] == 'n') + printf("disabling client auth\n"); + else + SSL_CTX_set_verify(ctx, SSL_VERIFY_PEER, 0); + + // are we using DSA certs + if (argc >= 3 && argv[2][0] == 'd') { + printf("using DSA certs\n"); + set_dsaServerCerts(ctx); + } + else { + set_serverCerts(ctx); + } DH* dh = set_tmpDH(ctx); SSL* ssl = SSL_new(ctx); diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/buffer.hpp mysql-5.5-5.5.43/extra/yassl/include/buffer.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/buffer.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/buffer.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2000, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -48,7 +48,11 @@ struct NoCheck { - void check(uint, uint); + int check(uint, uint); +}; + +struct Check { + int check(uint, uint); }; /* input_buffer operates like a smart c style array with a checking option, @@ -60,11 +64,13 @@ * write to the buffer bulk wise and have the correct size */ -class input_buffer : public NoCheck { +class input_buffer : public Check { uint size_; // number of elements in buffer uint current_; // current offset position in buffer byte* buffer_; // storage for buffer byte* end_; // end of storage marker + int error_; // error number + byte zero_; // for returning const reference to zero byte public: input_buffer(); @@ -93,6 +99,10 @@ uint get_remaining() const; + int get_error() const; + + void set_error(); + void set_current(uint i); // read only access through [], advance current @@ -103,7 +113,7 @@ bool eof(); // peek ahead - byte peek() const; + byte peek(); // write function, should use at/near construction void assign(const byte* t, uint s); diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/cert_wrapper.hpp mysql-5.5-5.5.43/extra/yassl/include/cert_wrapper.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/cert_wrapper.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/cert_wrapper.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2005, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2005, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -88,6 +88,7 @@ bool verifyNone_; // no error if verify fails bool failNoCert_; bool sendVerify_; + bool sendBlankCert_; VerifyCallback verifyCallback_; // user verify callback public: CertManager(); @@ -114,16 +115,18 @@ bool verifyNone() const; bool failNoCert() const; bool sendVerify() const; + bool sendBlankCert() const; void setVerifyPeer(); void setVerifyNone(); void setFailNoCert(); void setSendVerify(); + void setSendBlankCert(); void setPeerX509(X509*); void setVerifyCallback(VerifyCallback); private: CertManager(const CertManager&); // hide copy - CertManager& operator=(const CertManager&); // and assign + CertManager& operator=(const CertManager&); // and assigin }; diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/crypto_wrapper.hpp mysql-5.5-5.5.43/extra/yassl/include/crypto_wrapper.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/crypto_wrapper.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/crypto_wrapper.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/factory.hpp mysql-5.5-5.5.43/extra/yassl/include/factory.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/factory.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/factory.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/handshake.hpp mysql-5.5-5.5.43/extra/yassl/include/handshake.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/handshake.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/handshake.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/log.hpp mysql-5.5-5.5.43/extra/yassl/include/log.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/log.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/log.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/crypto.h mysql-5.5-5.5.43/extra/yassl/include/openssl/crypto.h --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/crypto.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/openssl/crypto.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2005, 2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/des.h mysql-5.5-5.5.43/extra/yassl/include/openssl/des.h --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/des.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/openssl/des.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2005 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/des_old.h mysql-5.5-5.5.43/extra/yassl/include/openssl/des_old.h --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/des_old.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/openssl/des_old.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/engine.h mysql-5.5-5.5.43/extra/yassl/include/openssl/engine.h --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/engine.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/openssl/engine.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2006 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/err.h mysql-5.5-5.5.43/extra/yassl/include/openssl/err.h --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/err.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/openssl/err.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2005, 2006 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/evp.h mysql-5.5-5.5.43/extra/yassl/include/openssl/evp.h --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/evp.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/openssl/evp.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/generate_prefix_files.pl mysql-5.5-5.5.43/extra/yassl/include/openssl/generate_prefix_files.pl --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/generate_prefix_files.pl 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/openssl/generate_prefix_files.pl 2015-02-27 08:30:34.000000000 +0000 @@ -1,6 +1,7 @@ #!/usr/bin/perl # Copyright (C) 2006 MySQL AB +# Use is subject to license terms # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/hmac.h mysql-5.5-5.5.43/extra/yassl/include/openssl/hmac.h --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/hmac.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/openssl/hmac.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/lhash.h mysql-5.5-5.5.43/extra/yassl/include/openssl/lhash.h --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/lhash.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/openssl/lhash.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2005 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/md4.h mysql-5.5-5.5.43/extra/yassl/include/openssl/md4.h --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/md4.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/openssl/md4.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2006 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/md5.h mysql-5.5-5.5.43/extra/yassl/include/openssl/md5.h --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/md5.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/openssl/md5.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2005, 2006 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/objects.h mysql-5.5-5.5.43/extra/yassl/include/openssl/objects.h --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/objects.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/openssl/objects.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/opensslv.h mysql-5.5-5.5.43/extra/yassl/include/openssl/opensslv.h --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/opensslv.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/openssl/opensslv.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2005 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/pem.h mysql-5.5-5.5.43/extra/yassl/include/openssl/pem.h --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/pem.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/openssl/pem.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2006 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/pkcs12.h mysql-5.5-5.5.43/extra/yassl/include/openssl/pkcs12.h --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/pkcs12.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/openssl/pkcs12.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2006 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/prefix_crypto.h mysql-5.5-5.5.43/extra/yassl/include/openssl/prefix_crypto.h --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/prefix_crypto.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/openssl/prefix_crypto.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2006 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/rand.h mysql-5.5-5.5.43/extra/yassl/include/openssl/rand.h --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/rand.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/openssl/rand.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2005 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/rsa.h mysql-5.5-5.5.43/extra/yassl/include/openssl/rsa.h --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/rsa.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/openssl/rsa.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2005, 2006 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/sha.h mysql-5.5-5.5.43/extra/yassl/include/openssl/sha.h --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/sha.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/openssl/sha.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/ssl.h mysql-5.5-5.5.43/extra/yassl/include/openssl/ssl.h --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/ssl.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/openssl/ssl.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2005, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2005, 2014, Oracle and/or its affiliates. All rights reserved. Use is subject to license terms. This program is free software; you can redistribute it and/or modify @@ -35,7 +35,7 @@ #include "rsa.h" -#define YASSL_VERSION "2.2.2" +#define YASSL_VERSION "2.3.7" #if defined(__cplusplus) diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/x509.h mysql-5.5-5.5.43/extra/yassl/include/openssl/x509.h --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/x509.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/openssl/x509.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2006 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/x509v3.h mysql-5.5-5.5.43/extra/yassl/include/openssl/x509v3.h --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/openssl/x509v3.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/openssl/x509v3.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2006 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/timer.hpp mysql-5.5-5.5.43/extra/yassl/include/timer.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/timer.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/timer.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/yassl_error.hpp mysql-5.5-5.5.43/extra/yassl/include/yassl_error.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/yassl_error.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/yassl_error.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2005, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2005, 2013, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/yassl.hpp mysql-5.5-5.5.43/extra/yassl/include/yassl.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/yassl.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/yassl.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/yassl_int.hpp mysql-5.5-5.5.43/extra/yassl/include/yassl_int.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/yassl_int.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/yassl_int.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -107,6 +107,25 @@ }; +// track received messages to explicitly disallow duplicate messages +struct RecvdMessages { + uint8 gotClientHello_; + uint8 gotServerHello_; + uint8 gotCert_; + uint8 gotServerKeyExchange_; + uint8 gotCertRequest_; + uint8 gotServerHelloDone_; + uint8 gotCertVerify_; + uint8 gotClientKeyExchange_; + uint8 gotFinished_; + RecvdMessages() : gotClientHello_(0), gotServerHello_(0), gotCert_(0), + gotServerKeyExchange_(0), gotCertRequest_(0), + gotServerHelloDone_(0), gotCertVerify_(0), + gotClientKeyExchange_(0), gotFinished_(0) + {} +}; + + // combines all states class States { RecordLayerState recordLayer_; @@ -115,6 +134,7 @@ ServerState serverState_; ConnectState connectState_; AcceptState acceptState_; + RecvdMessages recvdMessages_; char errorString_[MAX_ERROR_SZ]; YasslError what_; public: @@ -137,6 +157,7 @@ AcceptState& UseAccept(); char* useString(); void SetError(YasslError); + int SetMessageRecvd(HandShakeType); private: States(const States&); // hide copy States& operator=(const States&); // and assign diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/include/yassl_types.hpp mysql-5.5-5.5.43/extra/yassl/include/yassl_types.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/include/yassl_types.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/include/yassl_types.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2005, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2005, 2013, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/README mysql-5.5-5.5.43/extra/yassl/README --- mysql-5.5-5.5.35+dfsg/extra/yassl/README 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/README 2015-02-27 08:30:34.000000000 +0000 @@ -12,7 +12,71 @@ *** end Note *** -yaSSL Release notes, version 2.2.2 (7/5/2012) +yaSSL Release notes, version 2.3.7 (12/10/2014) + This release of yaSSL fixes the potential to process duplicate handshake + messages by explicitly marking/checking received handshake messages. + +yaSSL Release notes, version 2.3.6 (11/25/2014) + + This release of yaSSL fixes some valgrind warnings/errors including + uninitialized reads and off by one index errors induced from fuzzing + the handshake. These were reported by Oracle. + +yaSSL Release notes, version 2.3.5 (9/29/2014) + + This release of yaSSL fixes an RSA Padding check vulnerability reported by + Intel Security Advanced Threat Research team + +See normal build instructions below under 1.0.6. +See libcurl build instructions below under 1.3.0 and note in 1.5.8. + + +yaSSL Release notes, version 2.3.4 (8/15/2014) + + This release of yaSSL adds checking to the input_buffer class itself. + +See normal build instructions below under 1.0.6. +See libcurl build instructions below under 1.3.0 and note in 1.5.8. + + +yaSSL Release notes, version 2.3.2 (7/25/2014) + + This release of yaSSL updates test certs. + +See normal build instructions below under 1.0.6. +See libcurl build instructions below under 1.3.0 and note in 1.5.8. + + +*****************yaSSL Release notes, version 2.3.0 (12/5/2013) + + This release of yaSSL updates asm for newer GCC versions. + +See normal build instructions below under 1.0.6. +See libcurl build instructions below under 1.3.0 and note in 1.5.8. + + +*****************yaSSL Release notes, version 2.2.3 (4/23/2013) + + This release of yaSSL updates the test certificates as they were expired + +See normal build instructions below under 1.0.6. +See libcurl build instructions below under 1.3.0 and note in 1.5.8. + + +*****************yaSSL Release notes, version 2.2.2d (2/5/2013) + + This release of yaSSL contains countermeasuers for the Lucky 13 TLS 1.1 + CBC timing padding attack identified by Nadhem AlFardan and Kenneth Paterson + see: http://www.isg.rhul.ac.uk/tls/ + + It also adds SHA2 certificate verification and better checks for malicious + input. + +See normal build instructions below under 1.0.6. +See libcurl build instructions below under 1.3.0 and note in 1.5.8. + + +*****************yaSSL Release notes, version 2.2.2 (7/5/2012) This release of yaSSL contains bug fixes and more security checks around malicious certificates. diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/src/buffer.cpp mysql-5.5-5.5.43/extra/yassl/src/buffer.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/src/buffer.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/src/buffer.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2005, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2005, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -32,8 +32,19 @@ -void NoCheck::check(uint, uint) +/* return 0 on check success, always true for NoCheck policy */ +int NoCheck::check(uint, uint) { + return 0; +} + +/* return 0 on check success */ +int Check::check(uint i, uint max) +{ + if (i < max) + return 0; + + return -1; } @@ -48,18 +59,20 @@ input_buffer::input_buffer() - : size_(0), current_(0), buffer_(0), end_(0) + : size_(0), current_(0), buffer_(0), end_(0), error_(0), zero_(0) {} input_buffer::input_buffer(uint s) - : size_(0), current_(0), buffer_(NEW_YS byte[s]), end_(buffer_ + s) + : size_(0), current_(0), buffer_(NEW_YS byte[s]), end_(buffer_ + s), + error_(0), zero_(0) {} // with assign input_buffer::input_buffer(uint s, const byte* t, uint len) - : size_(0), current_(0), buffer_(NEW_YS byte[s]), end_(buffer_ + s) + : size_(0), current_(0), buffer_(NEW_YS byte[s]), end_(buffer_ + s), + error_(0), zero_(0) { assign(t, len); } @@ -74,8 +87,10 @@ // users can pass defualt zero length buffer and then allocate void input_buffer::allocate(uint s) { - buffer_ = NEW_YS byte[s]; - end_ = buffer_ + s; + if (error_ == 0) { + buffer_ = NEW_YS byte[s]; + end_ = buffer_ + s; + } } @@ -90,40 +105,67 @@ // if you know the size before the write use assign() void input_buffer::add_size(uint i) { - check(size_ + i-1, get_capacity()); - size_ += i; + if (error_ == 0 && check(size_ + i-1, get_capacity()) == 0) + size_ += i; + else + error_ = -1; } uint input_buffer::get_capacity() const { - return (uint) (end_ - buffer_); + if (error_ == 0) + return end_ - buffer_; + + return 0; } uint input_buffer::get_current() const { - return current_; + if (error_ == 0) + return current_; + + return 0; } uint input_buffer::get_size() const { - return size_; + if (error_ == 0) + return size_; + + return 0; } uint input_buffer::get_remaining() const { - return size_ - current_; + if (error_ == 0) + return size_ - current_; + + return 0; +} + + +int input_buffer::get_error() const +{ + return error_; +} + + +void input_buffer::set_error() +{ + error_ = -1; } void input_buffer::set_current(uint i) { - if (i) - check(i - 1, size_); - current_ = i; + if (error_ == 0 && i && check(i - 1, size_) == 0) + current_ = i; + else + error_ = -1; } @@ -131,40 +173,59 @@ // user passes in AUTO index for ease of use const byte& input_buffer::operator[](uint i) { - check(current_, size_); - return buffer_[current_++]; + if (error_ == 0 && check(current_, size_) == 0) + return buffer_[current_++]; + + error_ = -1; + return zero_; } // end of input test bool input_buffer::eof() { + if (error_ != 0) + return true; + return current_ >= size_; } // peek ahead -byte input_buffer::peek() const +byte input_buffer::peek() { - return buffer_[current_]; + if (error_ == 0 && check(current_, size_) == 0) + return buffer_[current_]; + + error_ = -1; + return 0; } // write function, should use at/near construction void input_buffer::assign(const byte* t, uint s) { - check(current_, get_capacity()); - add_size(s); - memcpy(&buffer_[current_], t, s); + if (t && error_ == 0 && check(current_, get_capacity()) == 0) { + add_size(s); + if (error_ == 0) { + memcpy(&buffer_[current_], t, s); + return; // success + } + } + + error_ = -1; } // use read to query input, adjusts current void input_buffer::read(byte* dst, uint length) { - check(current_ + length - 1, size_); - memcpy(dst, &buffer_[current_], length); - current_ += length; + if (dst && error_ == 0 && check(current_ + length - 1, size_) == 0) { + memcpy(dst, &buffer_[current_], length); + current_ += length; + } else { + error_ = -1; + } } diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/src/cert_wrapper.cpp mysql-5.5-5.5.43/extra/yassl/src/cert_wrapper.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/src/cert_wrapper.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/src/cert_wrapper.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2005, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2005, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -91,7 +91,7 @@ //CertManager CertManager::CertManager() : peerX509_(0), verifyPeer_(false), verifyNone_(false), failNoCert_(false), - sendVerify_(false), verifyCallback_(0) + sendVerify_(false), sendBlankCert_(false), verifyCallback_(0) {} @@ -142,6 +142,11 @@ verifyNone_ = true; } +bool CertManager::sendBlankCert() const +{ + return sendBlankCert_; +} + void CertManager::setFailNoCert() { @@ -154,6 +159,11 @@ sendVerify_ = true; } +void CertManager::setSendBlankCert() +{ + sendBlankCert_ = true; +} + void CertManager::setVerifyCallback(VerifyCallback vc) { diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/src/crypto_wrapper.cpp mysql-5.5-5.5.43/extra/yassl/src/crypto_wrapper.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/src/crypto_wrapper.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/src/crypto_wrapper.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -953,9 +953,9 @@ info->set = true; } } - // get blank line - if (fgets(line, sizeof(line), file)) begin = ftell(file); + if (fgets(line,sizeof(line), file)) // get blank line + begin = ftell(file); } } diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/src/handshake.cpp mysql-5.5-5.5.43/extra/yassl/src/handshake.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/src/handshake.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/src/handshake.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2005, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2005, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -522,7 +522,7 @@ // some clients still send sslv2 client hello void ProcessOldClientHello(input_buffer& input, SSL& ssl) { - if (input.get_remaining() < 2) { + if (input.get_error() || input.get_remaining() < 2) { ssl.SetError(bad_input); return; } @@ -549,20 +549,24 @@ byte len[2]; - input.read(len, sizeof(len)); + len[0] = input[AUTO]; + len[1] = input[AUTO]; ato16(len, ch.suite_len_); - input.read(len, sizeof(len)); + len[0] = input[AUTO]; + len[1] = input[AUTO]; uint16 sessionLen; ato16(len, sessionLen); ch.id_len_ = sessionLen; - input.read(len, sizeof(len)); + len[0] = input[AUTO]; + len[1] = input[AUTO]; uint16 randomLen; ato16(len, randomLen); - if (ch.suite_len_ > MAX_SUITE_SZ || sessionLen > ID_LEN || - randomLen > RAN_LEN) { + if (input.get_error() || ch.suite_len_ > MAX_SUITE_SZ || + ch.suite_len_ > input.get_remaining() || + sessionLen > ID_LEN || randomLen > RAN_LEN) { ssl.SetError(bad_input); return; } @@ -580,13 +584,12 @@ ch.suite_len_ = j; if (ch.id_len_) - input.read(ch.session_id_, ch.id_len_); + input.read(ch.session_id_, ch.id_len_); // id_len_ from sessionLen if (randomLen < RAN_LEN) memset(ch.random_, 0, RAN_LEN - randomLen); input.read(&ch.random_[RAN_LEN - randomLen], randomLen); - ch.Process(input, ssl); } @@ -787,6 +790,9 @@ ssl.verifyState(hdr); } + if (ssl.GetError()) + return 0; + // make sure we have enough input in buffer to process this record if (needHdr || hdr.length_ > buffer.get_remaining()) { // put header in front for next time processing @@ -799,6 +805,9 @@ while (buffer.get_current() < hdr.length_ + RECORD_HEADER + offset) { // each message in record, can be more than 1 if not encrypted + if (ssl.GetError()) + return 0; + if (ssl.getSecurity().get_parms().pending_ == false) { // cipher on // sanity check for malicious/corrupted/illegal input if (buffer.get_remaining() < hdr.length_) { @@ -1159,6 +1168,8 @@ { if (ssl.GetError()) return; + if(ssl.getCrypto().get_certManager().sendBlankCert()) return; + CertificateVerify verify; verify.Build(ssl); RecordLayerHeader rlHeader; diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/src/log.cpp mysql-5.5-5.5.43/extra/yassl/src/log.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/src/log.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/src/log.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/src/ssl.cpp mysql-5.5-5.5.43/extra/yassl/src/ssl.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/src/ssl.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/src/ssl.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2005, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2005, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -790,7 +790,10 @@ strncpy(name, path, MAX_PATH - 1 - HALF_PATH); strncat(name, "/", 1); strncat(name, entry->d_name, HALF_PATH); - if (stat(name, &buf) < 0) return SSL_BAD_STAT; + if (stat(name, &buf) < 0) { + closedir(dir); + return SSL_BAD_STAT; + } if (S_ISREG(buf.st_mode)) ret = read_file(ctx, name, SSL_FILETYPE_PEM, CA); diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/src/timer.cpp mysql-5.5-5.5.43/extra/yassl/src/timer.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/src/timer.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/src/timer.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/src/yassl_error.cpp mysql-5.5-5.5.43/extra/yassl/src/yassl_error.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/src/yassl_error.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/src/yassl_error.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2005, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2005, 2013, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/src/yassl_imp.cpp mysql-5.5-5.5.43/extra/yassl/src/yassl_imp.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/src/yassl_imp.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/src/yassl_imp.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2005, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2005, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -220,18 +220,29 @@ // read PreMaster secret and decrypt, server side void EncryptedPreMasterSecret::read(SSL& ssl, input_buffer& input) { + if (input.get_error()) { + ssl.SetError(bad_input); + return; + } + const CertManager& cert = ssl.getCrypto().get_certManager(); RSA rsa(cert.get_privateKey(), cert.get_privateKeyLength(), false); uint16 cipherLen = rsa.get_cipherLength(); if (ssl.isTLS()) { byte len[2]; - input.read(len, sizeof(len)); + len[0] = input[AUTO]; + len[1] = input[AUTO]; ato16(len, cipherLen); } alloc(cipherLen); input.read(secret_, length_); + if (input.get_error()) { + ssl.SetError(bad_input); + return; + } opaque preMasterSecret[SECRET_LEN]; + memset(preMasterSecret, 0, sizeof(preMasterSecret)); rsa.decrypt(preMasterSecret, secret_, length_, ssl.getCrypto().get_random()); @@ -277,6 +288,11 @@ // read client's public key, server side void ClientDiffieHellmanPublic::read(SSL& ssl, input_buffer& input) { + if (input.get_error() || input.get_remaining() < (uint)LENGTH_SZ) { + ssl.SetError(bad_input); + return; + } + DiffieHellman& dh = ssl.useCrypto().use_dh(); uint16 keyLength; @@ -285,8 +301,17 @@ tmp[1] = input[AUTO]; ato16(tmp, keyLength); + if (keyLength < dh.get_agreedKeyLength()/2) { + ssl.SetError(bad_input); + return; + } + alloc(keyLength); input.read(Yc_, keyLength); + if (input.get_error()) { + ssl.SetError(bad_input); + return; + } dh.makeAgreement(Yc_, keyLength); // because of encoding, first byte might be 0, don't use for preMaster @@ -331,6 +356,10 @@ // read server's p, g, public key and sig, client side void DH_Server::read(SSL& ssl, input_buffer& input) { + if (input.get_error() || input.get_remaining() < (uint)LENGTH_SZ) { + ssl.SetError(bad_input); + return; + } uint16 length, messageTotal = 6; // pSz + gSz + pubSz byte tmp[2]; @@ -341,6 +370,10 @@ messageTotal += length; input.read(parms_.alloc_p(length), length); + if (input.get_error() || input.get_remaining() < (uint)LENGTH_SZ) { + ssl.SetError(bad_input); + return; + } // g tmp[0] = input[AUTO]; @@ -349,6 +382,10 @@ messageTotal += length; input.read(parms_.alloc_g(length), length); + if (input.get_error() || input.get_remaining() < (uint)LENGTH_SZ) { + ssl.SetError(bad_input); + return; + } // pub tmp[0] = input[AUTO]; @@ -357,20 +394,36 @@ messageTotal += length; input.read(parms_.alloc_pub(length), length); + if (input.get_error() || input.get_remaining() < (uint)LENGTH_SZ) { + ssl.SetError(bad_input); + return; + } // save message for hash verify input_buffer message(messageTotal); input.set_current(input.get_current() - messageTotal); input.read(message.get_buffer(), messageTotal); message.add_size(messageTotal); + if (input.get_error() || input.get_remaining() < (uint)LENGTH_SZ) { + ssl.SetError(bad_input); + return; + } // signature tmp[0] = input[AUTO]; tmp[1] = input[AUTO]; ato16(tmp, length); + if (length == 0) { + ssl.SetError(bad_input); + return; + } signature_ = NEW_YS byte[length]; input.read(signature_, length); + if (input.get_error()) { + ssl.SetError(bad_input); + return; + } // verify signature byte hash[FINISHED_SZ]; @@ -645,6 +698,10 @@ { ssl.verifyState(*this); if (ssl.GetError()) return; + if (input.get_error()) { + ssl.SetError(bad_input); + return; + } const HandShakeFactory& hsf = ssl.getFactory().getHandShake(); mySTL::auto_ptr hs(hsf.CreateObject(type_)); if (!hs.get()) { @@ -810,8 +867,19 @@ // CipherSpec processing handler -void ChangeCipherSpec::Process(input_buffer&, SSL& ssl) +void ChangeCipherSpec::Process(input_buffer& input, SSL& ssl) { + if (input.get_error()) { + ssl.SetError(bad_input); + return; + } + + // detect duplicate change_cipher + if (ssl.getSecurity().get_parms().pending_ == false) { + ssl.order_error(); + return; + } + ssl.useSecurity().use_parms().pending_ = false; if (ssl.getSecurity().get_resuming()) { if (ssl.getSecurity().get_parms().entity_ == client_end) @@ -873,6 +941,11 @@ // Alert processing handler void Alert::Process(input_buffer& input, SSL& ssl) { + if (input.get_error()) { + ssl.SetError(bad_input); + return; + } + if (ssl.getSecurity().get_parms().pending_ == false) { // encrypted alert int aSz = get_length(); // alert size already read on input opaque verify[SHA_LEN]; @@ -890,12 +963,19 @@ if (ssl.getSecurity().get_parms().cipher_type_ == block) { int ivExtra = 0; + opaque fill; if (ssl.isTLSv1_1()) ivExtra = ssl.getCrypto().get_cipher().get_blockSize(); int padSz = ssl.getSecurity().get_parms().encrypt_size_ - ivExtra - aSz - digestSz; - input.set_current(input.get_current() + padSz); + for (int i = 0; i < padSz; i++) + fill = input[AUTO]; + } + + if (input.get_error()) { + ssl.SetError(bad_input); + return; } // verify @@ -1112,6 +1192,11 @@ // Process handler for Data void Data::Process(input_buffer& input, SSL& ssl) { + if (input.get_error()) { + ssl.SetError(bad_input); + return; + } + int msgSz = ssl.getSecurity().get_parms().encrypt_size_; int pad = 0, padSz = 0; int ivExtra = 0; @@ -1154,7 +1239,7 @@ int dataSz = msgSz - ivExtra - digestSz - pad - padSz; - if (dataSz < 0) { + if (dataSz < 0 || dataSz > (MAX_RECORD_SIZE + COMPRESS_EXTRA)) { ssl.SetError(bad_input); return; } @@ -1180,6 +1265,10 @@ // advance past mac and fill input.set_current(input.get_current() + digestSz + pad + padSz); + if (input.get_error()) { + ssl.SetError(bad_input); + return; + } } @@ -1199,22 +1288,38 @@ Certificate::Certificate(const x509* cert) : cert_(cert) { - set_length(cert_->get_length() + 2 * CERT_HEADER); // list and cert size + if (cert) + set_length(cert_->get_length() + 2 * CERT_HEADER); // list and cert size + else + set_length(CERT_HEADER); // total blank cert size, just list header } const opaque* Certificate::get_buffer() const { - return cert_->get_buffer(); + if (cert_) + return cert_->get_buffer(); + + return NULL; } // output operator for Certificate output_buffer& operator<<(output_buffer& output, const Certificate& cert) { - uint sz = cert.get_length() - 2 * CERT_HEADER; + uint sz = cert.get_length(); opaque tmp[CERT_HEADER]; + if ((int)sz > CERT_HEADER) + sz -= 2 * CERT_HEADER; // actual cert, not including headers + else { + sz = 0; // blank cert case + c32to24(sz, tmp); + output.write(tmp, CERT_HEADER); + + return output; + } + c32to24(sz + CERT_HEADER, tmp); output.write(tmp, CERT_HEADER); c32to24(sz, tmp); @@ -1228,6 +1333,11 @@ // certificate processing handler void Certificate::Process(input_buffer& input, SSL& ssl) { + if (input.get_error()) { + ssl.SetError(bad_input); + return; + } + CertManager& cm = ssl.useCrypto().use_certManager(); uint32 list_sz; @@ -1264,9 +1374,11 @@ ssl.SetError(YasslError(bad_input)); return; } - x509* myCert; - cm.AddPeerCert(myCert = NEW_YS x509(cert_sz)); - input.read(myCert->use_buffer(), myCert->get_length()); + if (cert_sz) { + x509* myCert; + cm.AddPeerCert(myCert = NEW_YS x509(cert_sz)); + input.read(myCert->use_buffer(), myCert->get_length()); + } list_sz -= cert_sz + CERT_HEADER; } @@ -1394,6 +1506,10 @@ // Session hello.id_len_ = input[AUTO]; + if (hello.id_len_ > ID_LEN) { + input.set_error(); + return input; + } if (hello.id_len_) input.read(hello.session_id_, hello.id_len_); @@ -1434,8 +1550,13 @@ // Server Hello processing handler -void ServerHello::Process(input_buffer&, SSL& ssl) +void ServerHello::Process(input_buffer& input, SSL& ssl) { + if (input.get_error()) { + ssl.SetError(bad_input); + return; + } + if (ssl.GetMultiProtocol()) { // SSLv23 support if (ssl.isTLS() && server_version_.minor_ < 1) // downgrade to SSLv3 @@ -1529,8 +1650,12 @@ // Server Hello Done processing handler -void ServerHelloDone::Process(input_buffer&, SSL& ssl) +void ServerHelloDone::Process(input_buffer& input, SSL& ssl) { + if (input.get_error()) { + ssl.SetError(bad_input); + return; + } ssl.useStates().useClient() = serverHelloDoneComplete; } @@ -1649,8 +1774,13 @@ // Client Hello processing handler -void ClientHello::Process(input_buffer&, SSL& ssl) +void ClientHello::Process(input_buffer& input, SSL& ssl) { + if (input.get_error()) { + ssl.SetError(bad_input); + return; + } + // store version for pre master secret ssl.useSecurity().use_connection().chVersion_ = client_version_; @@ -1782,9 +1912,17 @@ // Server Key Exchange processing handler void ServerKeyExchange::Process(input_buffer& input, SSL& ssl) { + if (input.get_error()) { + ssl.SetError(bad_input); + return; + } createKey(ssl); if (ssl.GetError()) return; server_key_->read(ssl, input); + if (input.get_error()) { + ssl.SetError(bad_input); + return; + } ssl.useStates().useClient() = serverKeyExchangeComplete; } @@ -1906,27 +2044,32 @@ { // types request.typeTotal_ = input[AUTO]; + if (request.typeTotal_ > CERT_TYPES) { + input.set_error(); + return input; + } for (int i = 0; i < request.typeTotal_; i++) request.certificate_types_[i] = ClientCertificateType(input[AUTO]); - byte tmp[REQUEST_HEADER]; - input.read(tmp, sizeof(tmp)); + byte tmp[2]; + tmp[0] = input[AUTO]; + tmp[1] = input[AUTO]; uint16 sz; ato16(tmp, sz); // authorities while (sz) { uint16 dnSz; - input.read(tmp, sizeof(tmp)); + tmp[0] = input[AUTO]; + tmp[1] = input[AUTO]; ato16(tmp, dnSz); - - DistinguishedName dn; - request.certificate_authorities_.push_back(dn = NEW_YS - byte[REQUEST_HEADER + dnSz]); - memcpy(dn, tmp, REQUEST_HEADER); - input.read(&dn[REQUEST_HEADER], dnSz); + + input.set_current(input.get_current() + dnSz); sz -= dnSz + REQUEST_HEADER; + + if (input.get_error()) + break; } return input; @@ -1965,13 +2108,17 @@ // CertificateRequest processing handler -void CertificateRequest::Process(input_buffer&, SSL& ssl) +void CertificateRequest::Process(input_buffer& input, SSL& ssl) { + if (input.get_error()) { + ssl.SetError(bad_input); + return; + } CertManager& cm = ssl.useCrypto().use_certManager(); - // make sure user provided cert and key before sending and using - if (cm.get_cert() && cm.get_privateKey()) - cm.setSendVerify(); + cm.setSendVerify(); + if (cm.get_cert() == NULL || cm.get_privateKey() == NULL) + cm.setSendBlankCert(); // send blank cert, OpenSSL requires now } @@ -2049,12 +2196,18 @@ input_buffer& operator>>(input_buffer& input, CertificateVerify& request) { byte tmp[VERIFY_HEADER]; - input.read(tmp, sizeof(tmp)); + tmp[0] = input[AUTO]; + tmp[1] = input[AUTO]; uint16 sz = 0; ato16(tmp, sz); request.set_length(sz); + if (sz == 0) { + input.set_error(); + return input; + } + request.signature_ = NEW_YS byte[sz]; input.read(request.signature_, sz); @@ -2073,8 +2226,13 @@ // CertificateVerify processing handler -void CertificateVerify::Process(input_buffer&, SSL& ssl) +void CertificateVerify::Process(input_buffer& input, SSL& ssl) { + if (input.get_error()) { + ssl.SetError(bad_input); + return; + } + const Hashes& hashVerify = ssl.getHashes().get_certVerify(); const CertManager& cert = ssl.getCrypto().get_certManager(); @@ -2113,9 +2271,17 @@ // Client Key Exchange processing handler void ClientKeyExchange::Process(input_buffer& input, SSL& ssl) { + if (input.get_error()) { + ssl.SetError(bad_input); + return; + } createKey(ssl); if (ssl.GetError()) return; client_key_->read(ssl, input); + if (input.get_error()) { + ssl.SetError(bad_input); + return; + } if (ssl.getCrypto().get_certManager().verifyPeer()) build_certHashes(ssl, ssl.useHashes().use_certVerify()); @@ -2202,11 +2368,19 @@ // Finished processing handler void Finished::Process(input_buffer& input, SSL& ssl) { + if (input.get_error()) { + ssl.SetError(bad_input); + return; + } // verify hashes const Finished& verify = ssl.getHashes().get_verify(); uint finishedSz = ssl.isTLS() ? TLS_FINISHED_SZ : FINISHED_SZ; input.read(hashes_.md5_, finishedSz); + if (input.get_error()) { + ssl.SetError(bad_input); + return; + } if (memcmp(&hashes_, &verify.hashes_, finishedSz)) { ssl.SetError(verify_error); @@ -2228,19 +2402,23 @@ opaque mac[SHA_LEN]; // max size int digestSz = ssl.getCrypto().get_digest().get_digestSize(); input.read(mac, digestSz); + if (input.get_error()) { + ssl.SetError(bad_input); + return; + } uint ivExtra = 0; if (ssl.getSecurity().get_parms().cipher_type_ == block) if (ssl.isTLSv1_1()) ivExtra = ssl.getCrypto().get_cipher().get_blockSize(); + opaque fill; int padSz = ssl.getSecurity().get_parms().encrypt_size_ - ivExtra - HANDSHAKE_HEADER - finishedSz - digestSz; - input.set_current(input.get_current() + padSz); - - // verify mac - if (memcmp(mac, verifyMAC, digestSz)) { - ssl.SetError(verify_error); + for (int i = 0; i < padSz; i++) + fill = input[AUTO]; + if (input.get_error()) { + ssl.SetError(bad_input); return; } diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/src/yassl_int.cpp mysql-5.5-5.5.43/extra/yassl/src/yassl_int.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/src/yassl_int.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/src/yassl_int.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2005, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2005, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -255,6 +255,77 @@ } +// mark message recvd, check for duplicates, return 0 on success +int States::SetMessageRecvd(HandShakeType hst) +{ + switch (hst) { + case hello_request: + break; // could send more than one + + case client_hello: + if (recvdMessages_.gotClientHello_) + return -1; + recvdMessages_.gotClientHello_ = 1; + break; + + case server_hello: + if (recvdMessages_.gotServerHello_) + return -1; + recvdMessages_.gotServerHello_ = 1; + break; + + case certificate: + if (recvdMessages_.gotCert_) + return -1; + recvdMessages_.gotCert_ = 1; + break; + + case server_key_exchange: + if (recvdMessages_.gotServerKeyExchange_) + return -1; + recvdMessages_.gotServerKeyExchange_ = 1; + break; + + case certificate_request: + if (recvdMessages_.gotCertRequest_) + return -1; + recvdMessages_.gotCertRequest_ = 1; + break; + + case server_hello_done: + if (recvdMessages_.gotServerHelloDone_) + return -1; + recvdMessages_.gotServerHelloDone_ = 1; + break; + + case certificate_verify: + if (recvdMessages_.gotCertVerify_) + return -1; + recvdMessages_.gotCertVerify_ = 1; + break; + + case client_key_exchange: + if (recvdMessages_.gotClientKeyExchange_) + return -1; + recvdMessages_.gotClientKeyExchange_ = 1; + break; + + case finished: + if (recvdMessages_.gotFinished_) + return -1; + recvdMessages_.gotFinished_ = 1; + break; + + + default: + return -1; + + } + + return 0; +} + + sslFactory::sslFactory() : messageFactory_(InitMessageFactory), handShakeFactory_(InitHandShakeFactory), @@ -1199,6 +1270,11 @@ return; } + if (states_.SetMessageRecvd(hsHeader.get_handshakeType()) != 0) { + order_error(); + return; + } + if (secure_.get_parms().entity_ == client_end) verifyClientState(hsHeader.get_handshakeType()); else @@ -2534,8 +2610,9 @@ int DeCompress(input_buffer& in, int sz, input_buffer& out) { byte tmp[LENGTH_SZ]; - - in.read(tmp, sizeof(tmp)); + + tmp[0] = in[AUTO]; + tmp[1] = in[AUTO]; uint16 len; ato16(tmp, len); diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/CMakeLists.txt mysql-5.5-5.5.43/extra/yassl/taocrypt/CMakeLists.txt --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/CMakeLists.txt 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/CMakeLists.txt 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -# Copyright (c) 2006, 2010, Oracle and/or its affiliates. All rights reserved. +# Copyright (c) 2006, 2014, Oracle and/or its affiliates. All rights reserved. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -36,7 +36,6 @@ ADD_CONVENIENCE_LIBRARY(taocrypt ${TAOCRYPT_SOURCES}) RESTRICT_SYMBOL_EXPORTS(taocrypt) -INSTALL_DEBUG_SYMBOLS(taocrypt) IF(MSVC) INSTALL_DEBUG_TARGET(taocrypt DESTINATION ${INSTALL_LIBDIR}/debug) ENDIF() diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/algebra.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/include/algebra.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/algebra.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/include/algebra.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/arc4.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/include/arc4.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/arc4.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/include/arc4.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/asn.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/include/asn.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/asn.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/include/asn.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2005, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -111,7 +111,7 @@ MAX_LENGTH_SZ = 5, MAX_SEQ_SZ = 5, // enum(seq|con) + length(4) MAX_ALGO_SIZE = 9, - MAX_DIGEST_SZ = 25, // SHA + enum(Bit or Octet) + length(4) + MAX_DIGEST_SZ = 69, // SHA512 + enum(Bit or Octet) + length(4) DSA_SIG_SZ = 40, ASN_NAME_MAX = 512 // max total of all included names }; @@ -257,8 +257,11 @@ enum ContentType { HUH = 651 }; -enum SigType { SHAwDSA = 517, MD2wRSA = 646, MD5wRSA = 648, SHAwRSA =649}; -enum HashType { MD2h = 646, MD5h = 649, SHAh = 88 }; +enum SigType { SHAwDSA = 517, MD2wRSA = 646, MD5wRSA = 648, SHAwRSA = 649, + SHA256wRSA = 655, SHA384wRSA = 656, SHA512wRSA = 657, + SHA256wDSA = 416 }; +enum HashType { MD2h = 646, MD5h = 649, SHAh = 88, SHA256h = 414, SHA384h = 415, + SHA512h = 416 }; enum KeyType { DSAk = 515, RSAk = 645 }; // sums of algo OID @@ -294,9 +297,9 @@ byte* signature_; char issuer_[ASN_NAME_MAX]; // Names char subject_[ASN_NAME_MAX]; // Names - char beforeDate_[MAX_DATE_SZ]; // valid before date - char afterDate_[MAX_DATE_SZ]; // valid after date - bool verify_; // Default to yes, but could be off + char beforeDate_[MAX_DATE_SZ+1]; // valid before date, +null term + char afterDate_[MAX_DATE_SZ+1]; // valid after date, +null term + bool verify_; // Default to yes, but could be off void ReadHeader(); void Decode(SignerList*, CertType); diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/block.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/include/block.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/block.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/include/block.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2005, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -74,7 +74,7 @@ if (preserve) { A b = A(); typename A::pointer newPointer = b.allocate(newSize, 0); - memcpy(newPointer, p, sizeof(T) * min((word32) oldSize, (word32) newSize)); + memcpy(newPointer, p, sizeof(T) * min(oldSize, newSize)); a.deallocate(p, oldSize); STL::swap(a, b); return newPointer; @@ -186,9 +186,9 @@ ~Block() { allocator_.deallocate(buffer_, sz_); } private: + A allocator_; word32 sz_; // size in Ts T* buffer_; - A allocator_; }; diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/coding.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/include/coding.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/coding.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/include/coding.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/dh.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/include/dh.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/dh.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/include/dh.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/dsa.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/include/dsa.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/dsa.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/include/dsa.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/error.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/include/error.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/error.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/include/error.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/hmac.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/include/hmac.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/hmac.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/include/hmac.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/integer.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/include/integer.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/integer.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/include/integer.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2000, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -46,6 +46,14 @@ #ifdef TAOCRYPT_X86ASM_AVAILABLE + #if defined(__GNUC__) && (__GNUC__ >= 4) + // GCC 4 or greater optimizes too much inline on recursive for bigint, + // -O3 just as fast without asm here anyway + #undef TAOCRYPT_X86ASM_AVAILABLE + #endif +#endif + +#ifdef TAOCRYPT_X86ASM_AVAILABLE #ifdef _M_IX86 #if (defined(__INTEL_COMPILER) && (__INTEL_COMPILER >= 500)) || \ diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/md2.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/include/md2.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/md2.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/include/md2.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/md4.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/include/md4.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/md4.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/include/md4.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/md5.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/include/md5.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/md5.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/include/md5.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/misc.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/include/misc.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/misc.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/include/misc.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -124,15 +124,22 @@ // no gas on these systems ?, disable for now -#if defined(__sun__) || defined (__APPLE__) +#if defined(__sun__) + #undef TAOCRYPT_DISABLE_X86ASM #define TAOCRYPT_DISABLE_X86ASM #endif // icc problem with -03 and integer, disable for now #if defined(__INTEL_COMPILER) + #undef TAOCRYPT_DISABLE_X86ASM #define TAOCRYPT_DISABLE_X86ASM #endif +// indpedent of build system, unless ia32 asm is enabled disable it +#if !defined(TAOCRYPT_ENABLE_X86ASM) + #undef TAOCRYPT_DISABLE_X86ASM + #define TAOCRYPT_DISABLE_X86ASM +#endif // Turn on ia32 ASM for Big Integer // CodeWarrior defines _MSC_VER diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/modarith.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/include/modarith.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/modarith.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/include/modarith.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/pwdbased.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/include/pwdbased.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/pwdbased.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/include/pwdbased.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2000, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -16,6 +16,7 @@ MA 02110-1301 USA. */ + /* pwdbased.hpp defines PBKDF2 from PKCS #5 */ @@ -48,10 +49,7 @@ word32 pLen, const byte* salt, word32 sLen, word32 iterations) const { - if (dLen > MaxDerivedKeyLength()) - return 0; - - if (iterations < 0) + if (dLen > MaxDerivedKeyLength()) return 0; ByteBlock buffer(T::DIGEST_SIZE); diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/random.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/include/random.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/random.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/include/random.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/ripemd.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/include/ripemd.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/ripemd.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/include/ripemd.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/runtime.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/include/runtime.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/runtime.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/include/runtime.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2005, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -34,7 +34,10 @@ // Handler for pure virtual functions namespace __Crun { - void pure_error(void); + static void pure_error(void) + { + // "Pure virtual method called, Aborted", GCC 4.2 str cmp fix + } } // namespace __Crun #endif // __sun @@ -48,7 +51,15 @@ #if defined(DO_TAOCRYPT_KERNEL_MODE) #include "kernelc.hpp" #endif - int __cxa_pure_virtual () __attribute__ ((weak)); + +/* Disallow inline __cxa_pure_virtual() */ +static int __cxa_pure_virtual() __attribute__((noinline, used)); +static int __cxa_pure_virtual() +{ + // oops, pure virtual called! + return 0; +} + } // extern "C" #endif // __GNUC__ > 2 diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/sha.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/include/sha.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/sha.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/include/sha.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (C) 2000-2007 MySQL AB + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -158,6 +158,12 @@ void Transform(); }; +enum { MAX_SHA2_DIGEST_SIZE = 64 }; // SHA512 + +#else + +enum { MAX_SHA2_DIGEST_SIZE = 32 }; // SHA256 + #endif // WORD64_AVAILABLE diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/twofish.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/include/twofish.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/twofish.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/include/twofish.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/type_traits.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/include/type_traits.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/include/type_traits.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/include/type_traits.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/mySTL/algorithm.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/mySTL/algorithm.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/mySTL/algorithm.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/mySTL/algorithm.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/mySTL/helpers.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/mySTL/helpers.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/mySTL/helpers.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/mySTL/helpers.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/mySTL/list.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/mySTL/list.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/mySTL/list.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/mySTL/list.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/mySTL/memory_array.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/mySTL/memory_array.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/mySTL/memory_array.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/mySTL/memory_array.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/mySTL/memory.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/mySTL/memory.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/mySTL/memory.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/mySTL/memory.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/mySTL/pair.hpp mysql-5.5-5.5.43/extra/yassl/taocrypt/mySTL/pair.hpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/mySTL/pair.hpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/mySTL/pair.hpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/aes.cpp mysql-5.5-5.5.43/extra/yassl/taocrypt/src/aes.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/aes.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/src/aes.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2005, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -52,7 +52,7 @@ in += BLOCK_SIZE; } else if (mode_ == CBC) { - if (dir_ == ENCRYPTION) + if (dir_ == ENCRYPTION) { while (blocks--) { r_[0] ^= *(word32*)in; r_[1] ^= *(word32*)(in + 4); @@ -65,7 +65,8 @@ out += BLOCK_SIZE; in += BLOCK_SIZE; } - else + } + else { while (blocks--) { AsmDecrypt(in, out, (void*)Td0); @@ -78,7 +79,8 @@ out += BLOCK_SIZE; in += BLOCK_SIZE; } - } + } + } } #endif // DO_AES_ASM @@ -452,27 +454,30 @@ #if defined(DO_AES_ASM) #ifdef __GNUC__ - #define AS1(x) asm(#x); - #define AS2(x, y) asm(#x ", " #y); + #define AS1(x) #x ";" + #define AS2(x, y) #x ", " #y ";" #define PROLOG() \ - asm(".intel_syntax noprefix"); \ - AS2( movd mm3, edi ) \ - AS2( movd mm4, ebx ) \ - AS2( sub esp, 4 ) \ - AS2( movd mm7, ebp ) \ - AS2( mov [ebp - 4], esi ) \ - AS2( mov ecx, DWORD PTR [ebp + 8] ) \ - AS2( mov esi, DWORD PTR [ebp + 12] ) \ - AS2( mov ebp, DWORD PTR [ebp + 20] ) - + __asm__ __volatile__ \ + ( \ + ".intel_syntax noprefix;" \ + "push ebx;" \ + "push ebp;" \ + "movd mm7, ebp;" \ + "movd mm4, eax;" \ + "mov ebp, edx;" \ + "sub esp, 4;" #define EPILOG() \ - AS2( mov esi, [ebp - 4] ) \ - AS2( mov esp, ebp ) \ - AS2( movd ebx, mm4 ) \ - AS2( movd edi, mm3 ) \ - AS1( emms ) \ - asm(".att_syntax"); + "add esp, 4;" \ + "pop ebp;" \ + "pop ebx;" \ + "emms;" \ + ".att_syntax;" \ + : \ + : "c" (this), "S" (inBlock), "d" (boxes), "a" (outBlock) \ + : "%edi", "memory", "cc" \ + ); + #else #define AS1(x) __asm x #define AS2(x, y) __asm x, y @@ -504,6 +509,8 @@ #ifdef _MSC_VER __declspec(naked) +#else + __attribute__ ((noinline)) #endif void AES::AsmEncrypt(const byte* inBlock, byte* outBlock, void* boxes) const { @@ -537,7 +544,11 @@ AS2( xor ecx, DWORD PTR [edi + 8] ) // s2 AS2( xor edx, DWORD PTR [edi + 12] ) // s3 - AS1(loop1: ) +#ifdef _MSC_VER + AS1( loop1: ) // loop1 +#else + AS1(1: ) // loop1 +#endif /* Put0 (mm0) = Te0[get0,rs 24] ^ Te1[get1,rs 16] ^ @@ -652,7 +663,11 @@ AS1( dec edi ) AS2( movd mm5, edi ) - AS1( jnz loop1 ) +#ifdef _MSC_VER + AS1( jnz loop1) // loop1 +#else + AS1( jnz 1b ) // loop1 +#endif // last round /* @@ -799,9 +814,9 @@ // store #ifdef __GNUC__ - AS2( mov esi, DWORD PTR [ebp + 16] ) // outBlock + AS2( movd esi, mm4 ) // outBlock #else - AS2( mov esi, DWORD PTR [ebp + 12] ) // outBlock + AS2( mov esi, DWORD PTR [ebp + 12] ) // outBlock #endif AS1( bswap ecx ) @@ -819,6 +834,8 @@ #ifdef _MSC_VER __declspec(naked) +#else + __attribute__ ((noinline)) #endif void AES::AsmDecrypt(const byte* inBlock, byte* outBlock, void* boxes) const { @@ -853,7 +870,11 @@ AS2( xor edx, DWORD PTR [edi + 12] ) // s3 - AS1(loop2: ) +#ifdef _MSC_VER + AS1( loop2: ) // loop2 +#else + AS1(2: ) // loop2 +#endif /* Put0 (mm0) = Td0[GETBYTE(get0, rs24)] ^ Td1[GETBYTE(get3, rs16)] ^ @@ -964,7 +985,11 @@ AS1( dec edi ) AS2( movd mm5, edi ) - AS1( jnz loop2 ) +#ifdef _MSC_VER + AS1( jnz loop2) // loop2 +#else + AS1( jnz 2b ) // loop2 +#endif // last round /* @@ -1114,9 +1139,9 @@ // store #ifdef __GNUC__ - AS2( mov esi, DWORD PTR [ebp + 16] ) // outBlock + AS2( movd esi, mm4 ) // outBlock #else - AS2( mov esi, DWORD PTR [ebp + 12] ) // outBlock + AS2( mov esi, DWORD PTR [ebp + 12] ) // outBlock #endif AS2( mov DWORD PTR [esi], eax ) AS2( mov DWORD PTR [esi + 4], ebx ) diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/algebra.cpp mysql-5.5-5.5.43/extra/yassl/taocrypt/src/algebra.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/algebra.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/src/algebra.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2005, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -186,10 +186,10 @@ struct WindowSlider { - WindowSlider(const Integer &expIn, bool fastNegateIn, + WindowSlider(const Integer &exp, bool fastNegate, unsigned int windowSizeIn=0) - : exp(expIn), windowModulus(Integer::One()), windowSize(windowSizeIn), - windowBegin(0), fastNegate(fastNegateIn), firstTime(true), + : exp(exp), windowModulus(Integer::One()), windowSize(windowSizeIn), + windowBegin(0), fastNegate(fastNegate), firstTime(true), finished(false) { if (windowSize == 0) diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/arc4.cpp mysql-5.5-5.5.43/extra/yassl/taocrypt/src/arc4.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/arc4.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/src/arc4.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2000, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -111,28 +111,26 @@ void ARC4::AsmProcess(byte* out, const byte* in, word32 length) { #ifdef __GNUC__ - #define AS1(x) asm(#x); - #define AS2(x, y) asm(#x ", " #y); + #define AS1(x) #x ";" + #define AS2(x, y) #x ", " #y ";" #define PROLOG() \ - asm(".intel_syntax noprefix"); \ - AS2( movd mm3, edi ) \ - AS2( movd mm4, ebx ) \ - AS2( movd mm5, esi ) \ - AS2( movd mm6, ebp ) \ - AS2( mov ecx, DWORD PTR [ebp + 8] ) \ - AS2( mov edi, DWORD PTR [ebp + 12] ) \ - AS2( mov esi, DWORD PTR [ebp + 16] ) \ - AS2( mov ebp, DWORD PTR [ebp + 20] ) - + __asm__ __volatile__ \ + ( \ + ".intel_syntax noprefix;" \ + "push ebx;" \ + "push ebp;" \ + "mov ebp, eax;" #define EPILOG() \ - AS2( movd ebp, mm6 ) \ - AS2( movd esi, mm5 ) \ - AS2( movd ebx, mm4 ) \ - AS2( mov esp, ebp ) \ - AS2( movd edi, mm3 ) \ - AS1( emms ) \ - asm(".att_syntax"); + "pop ebp;" \ + "pop ebx;" \ + "emms;" \ + ".att_syntax;" \ + : \ + : "c" (this), "D" (out), "S" (in), "a" (length) \ + : "%edx", "memory", "cc" \ + ); + #else #define AS1(x) __asm x #define AS2(x, y) __asm x, y @@ -178,7 +176,11 @@ AS2( movzx eax, BYTE PTR [ebp + ecx] ) -AS1( begin: ) +#ifdef _MSC_VER + AS1( loopStart: ) // loopStart +#else + AS1( 0: ) // loopStart for some gas (need numeric for jump back +#endif // y = (y+a) & 0xff; AS2( add edx, eax ) @@ -215,7 +217,11 @@ AS1( inc edi ) AS1( dec DWORD PTR [esp] ) - AS1( jnz begin ) +#ifdef _MSC_VER + AS1( jnz loopStart ) // loopStart +#else + AS1( jnz 0b ) // loopStart +#endif // write back to x_ and y_ @@ -225,6 +231,8 @@ AS1( nothing: ) + // inline adjust + AS2( add esp, 4 ) // fix room on stack EPILOG() } diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/asn.cpp mysql-5.5-5.5.43/extra/yassl/taocrypt/src/asn.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/asn.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/src/asn.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,6 +1,5 @@ /* - Copyright (c) 2005, 2012, Oracle and/or its affiliates. All rights reserved. - Use is subject to license terms. + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -673,7 +672,7 @@ } sigLength_ = GetLength(source_); - if (sigLength_ == 0 || source_.IsLeft(sigLength_) == false) { + if (sigLength_ <= 1 || source_.IsLeft(sigLength_) == false) { source_.SetError(CONTENT_E); return 0; } @@ -761,7 +760,7 @@ while (source_.get_index() < length) { GetSet(); if (source_.GetError().What() == SET_E) { - source_.SetError(NO_ERROR_E); // extensions may only have sequence + source_.SetError(NO_ERROR_E); // extensions may only have sequence source_.prev(); } GetSequence(); @@ -832,10 +831,8 @@ if (source_.IsLeft(length) == false) return; if (email) { - if (!(ptr = AddTag(ptr, buf_end, "/emailAddress=", 14, length))) { - source_.SetError(CONTENT_E); - return; - } + if (!(ptr = AddTag(ptr, buf_end, "/emailAddress=", 14, length))) + return; } source_.advance(length); @@ -972,12 +969,26 @@ hasher.reset(NEW_TC SHA); ht = SHAh; } + else if (signatureOID_ == SHA256wRSA || signatureOID_ == SHA256wDSA) { + hasher.reset(NEW_TC SHA256); + ht = SHA256h; + } +#ifdef WORD64_AVAILABLE + else if (signatureOID_ == SHA384wRSA) { + hasher.reset(NEW_TC SHA384); + ht = SHA384h; + } + else if (signatureOID_ == SHA512wRSA) { + hasher.reset(NEW_TC SHA512); + ht = SHA512h; + } +#endif else { source_.SetError(UNKOWN_SIG_E); return false; } - byte digest[SHA::DIGEST_SIZE]; // largest size + byte digest[MAX_SHA2_DIGEST_SIZE]; // largest size hasher->Update(source_.get_buffer() + certBegin_, sigIndex_ - certBegin_); hasher->Final(digest); @@ -990,11 +1001,17 @@ RSA_PublicKey pubKey(pub); RSAES_Encryptor enc(pubKey); + if (pubKey.FixedCiphertextLength() != sigLength_) { + source_.SetError(SIG_LEN_E); + return false; + } + return enc.SSL_Verify(build.get_buffer(), build.size(), signature_); } else { // DSA // extract r and s from sequence byte seqDecoded[DSA_SIG_SZ]; + memset(seqDecoded, 0, sizeof(seqDecoded)); DecodeDSA_Signature(seqDecoded, signature_, sigLength_); DSA_PublicKey pubKey(pub); @@ -1050,6 +1067,12 @@ 0x02, 0x05, 0x05, 0x00 }; static const byte md2AlgoID[] = { 0x2a, 0x86, 0x48, 0x86, 0xf7, 0x0d, 0x02, 0x02, 0x05, 0x00}; + static const byte sha256AlgoID[] = { 0x60, 0x86, 0x48, 0x01, 0x65, 0x03, + 0x04, 0x02, 0x01, 0x05, 0x00 }; + static const byte sha384AlgoID[] = { 0x60, 0x86, 0x48, 0x01, 0x65, 0x03, + 0x04, 0x02, 0x02, 0x05, 0x00 }; + static const byte sha512AlgoID[] = { 0x60, 0x86, 0x48, 0x01, 0x65, 0x03, + 0x04, 0x02, 0x03, 0x05, 0x00 }; int algoSz = 0; const byte* algoName = 0; @@ -1060,6 +1083,21 @@ algoName = shaAlgoID; break; + case SHA256h: + algoSz = sizeof(sha256AlgoID); + algoName = sha256AlgoID; + break; + + case SHA384h: + algoSz = sizeof(sha384AlgoID); + algoName = sha384AlgoID; + break; + + case SHA512h: + algoSz = sizeof(sha512AlgoID); + algoName = sha512AlgoID; + break; + case MD2h: algoSz = sizeof(md2AlgoID); algoName = md2AlgoID; diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/bftables.cpp mysql-5.5-5.5.43/extra/yassl/taocrypt/src/bftables.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/bftables.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/src/bftables.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/blowfish.cpp mysql-5.5-5.5.43/extra/yassl/taocrypt/src/blowfish.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/blowfish.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/src/blowfish.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2006, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -54,7 +54,7 @@ in += BLOCK_SIZE; } else if (mode_ == CBC) { - if (dir_ == ENCRYPTION) + if (dir_ == ENCRYPTION) { while (blocks--) { r_[0] ^= *(word32*)in; r_[1] ^= *(word32*)(in + 4); @@ -66,7 +66,8 @@ out += BLOCK_SIZE; in += BLOCK_SIZE; } - else + } + else { while (blocks--) { AsmProcess(in, out); @@ -78,6 +79,7 @@ out += BLOCK_SIZE; in += BLOCK_SIZE; } + } } } @@ -222,23 +224,26 @@ #if defined(DO_BLOWFISH_ASM) #ifdef __GNUC__ - #define AS1(x) asm(#x); - #define AS2(x, y) asm(#x ", " #y); + #define AS1(x) #x ";" + #define AS2(x, y) #x ", " #y ";" #define PROLOG() \ - asm(".intel_syntax noprefix"); \ - AS2( movd mm3, edi ) \ - AS2( movd mm4, ebx ) \ - AS2( movd mm5, esi ) \ - AS2( mov ecx, DWORD PTR [ebp + 8] ) \ - AS2( mov esi, DWORD PTR [ebp + 12] ) - + __asm__ __volatile__ \ + ( \ + ".intel_syntax noprefix;" \ + "push ebx;" \ + "push ebp;" \ + "movd mm3, eax;" #define EPILOG() \ - AS2( movd esi, mm5 ) \ - AS2( movd ebx, mm4 ) \ - AS2( movd edi, mm3 ) \ - AS1( emms ) \ - asm(".att_syntax"); + "pop ebp;" \ + "pop ebx;" \ + "emms;" \ + ".att_syntax;" \ + : \ + : "c" (this), "S" (inBlock), "a" (outBlock) \ + : "%edi", "%edx", "memory", "cc" \ + ); + #else #define AS1(x) __asm x #define AS2(x, y) __asm x, y @@ -287,6 +292,8 @@ #ifdef _MSC_VER __declspec(naked) +#else + __attribute__ ((noinline)) #endif void Blowfish::AsmProcess(const byte* inBlock, byte* outBlock) const { @@ -335,7 +342,7 @@ #endif #ifdef __GNUC__ - AS2( mov edi, [ebp + 16] ) // outBlock + AS2( movd edi, mm3 ) // outBlock #else AS2( mov edi, [ebp + 12] ) // outBlock #endif diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/des.cpp mysql-5.5-5.5.43/extra/yassl/taocrypt/src/des.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/des.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/src/des.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (C) 2000-2007 MySQL AB + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -473,7 +473,7 @@ uses ecx */ -#define AsmIPERM() {\ +#define AsmIPERM() \ AS2( rol ebx, 4 ) \ AS2( mov ecx, eax ) \ AS2( xor ecx, ebx ) \ @@ -504,7 +504,7 @@ AS2( and ecx, 0xaaaaaaaa ) \ AS2( xor eax, ecx ) \ AS2( rol eax, 1 ) \ - AS2( xor ebx, ecx ) } + AS2( xor ebx, ecx ) /* Uses FPERM algorithm from above @@ -514,7 +514,7 @@ uses ecx */ -#define AsmFPERM() {\ +#define AsmFPERM() \ AS2( ror ebx, 1 ) \ AS2( mov ecx, eax ) \ AS2( xor ecx, ebx ) \ @@ -545,7 +545,7 @@ AS2( and ecx, 0xf0f0f0f0 ) \ AS2( xor eax, ecx ) \ AS2( xor ebx, ecx ) \ - AS2( ror eax, 4 ) } + AS2( ror eax, 4 ) @@ -642,31 +642,33 @@ #ifdef _MSC_VER __declspec(naked) +#else + __attribute__ ((noinline)) #endif void DES_EDE3::AsmProcess(const byte* in, byte* out, void* box) const { #ifdef __GNUC__ - #define AS1(x) asm(#x); - #define AS2(x, y) asm(#x ", " #y); - - asm(".intel_syntax noprefix"); + #define AS1(x) #x ";" + #define AS2(x, y) #x ", " #y ";" #define PROLOG() \ - AS2( movd mm3, edi ) \ - AS2( movd mm4, ebx ) \ - AS2( movd mm5, esi ) \ - AS2( movd mm6, ebp ) \ - AS2( mov edx, DWORD PTR [ebp + 8] ) \ - AS2( mov esi, DWORD PTR [ebp + 12] ) \ - AS2( mov ebp, DWORD PTR [ebp + 20] ) - - // ebp restored at end - #define EPILOG() \ - AS2( movd edi, mm3 ) \ - AS2( movd ebx, mm4 ) \ - AS2( movd esi, mm5 ) \ - AS1( emms ) \ - asm(".att_syntax"); + __asm__ __volatile__ \ + ( \ + ".intel_syntax noprefix;" \ + "push ebx;" \ + "push ebp;" \ + "movd mm6, ebp;" \ + "movd mm7, ecx;" \ + "mov ebp, eax;" + #define EPILOG() \ + "pop ebp;" \ + "pop ebx;" \ + "emms;" \ + ".att_syntax;" \ + : \ + : "d" (this), "S" (in), "a" (box), "c" (out) \ + : "%edi", "memory", "cc" \ + ); #else #define AS1(x) __asm x @@ -756,7 +758,7 @@ AS1( bswap eax ) #ifdef __GNUC__ - AS2( mov esi, DWORD PTR [ebp + 16] ) // outBlock + AS2( movd esi, mm7 ) // outBlock #else AS2( mov esi, DWORD PTR [ebp + 12] ) // outBlock #endif diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/dh.cpp mysql-5.5-5.5.43/extra/yassl/taocrypt/src/dh.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/dh.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/src/dh.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/file.cpp mysql-5.5-5.5.43/extra/yassl/taocrypt/src/file.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/file.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/src/file.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/integer.cpp mysql-5.5-5.5.43/extra/yassl/taocrypt/src/integer.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/integer.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/src/integer.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2005, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -55,8 +55,9 @@ #include #endif #elif defined(_MSC_VER) && defined(_M_IX86) - #pragma message("You do not seem to have the Visual C++ Processor Pack ") +/* #pragma message("You do not seem to have the Visual C++ Processor Pack ") #pragma message("installed, so use of SSE2 intrinsics will be disabled.") +*/ #elif defined(__GNUC__) && defined(__i386__) /* #warning You do not have GCC 3.3 or later, or did not specify the -msse2 \ compiler option. Use of SSE2 intrinsics will be disabled. @@ -73,7 +74,7 @@ CPP_TYPENAME AlignedAllocator::pointer AlignedAllocator::allocate( size_type n, const void *) { - if (n > max_size()) + if (n > this->max_size()) return 0; if (n == 0) return 0; @@ -280,7 +281,12 @@ word GetHighHalfAsBorrow() const {return 0-halfs_.high;} private: - struct dword_struct + union + { + #ifdef TAOCRYPT_NATIVE_DWORD_AVAILABLE + dword whole_; + #endif + struct { #ifdef LITTLE_ENDIAN_ORDER word low; @@ -289,14 +295,7 @@ word high; word low; #endif - }; - - union - { - #ifdef TAOCRYPT_NATIVE_DWORD_AVAILABLE - dword whole_; - #endif - struct dword_struct halfs_; + } halfs_; }; }; @@ -1199,24 +1198,20 @@ #define AS1(x) #x ";" #define AS2(x, y) #x ", " #y ";" #define AddPrologue \ - word res; \ __asm__ __volatile__ \ ( \ "push %%ebx;" /* save this manually, in case of -fPIC */ \ - "mov %3, %%ebx;" \ + "mov %2, %%ebx;" \ ".intel_syntax noprefix;" \ "push ebp;" #define AddEpilogue \ "pop ebp;" \ ".att_syntax prefix;" \ "pop %%ebx;" \ - "mov %%eax, %0;" \ - : "=g" (res) \ + : \ : "c" (C), "d" (A), "m" (B), "S" (N) \ : "%edi", "memory", "cc" \ - ); \ - return res; - + ); #define MulPrologue \ __asm__ __volatile__ \ ( \ @@ -2610,18 +2605,20 @@ void Integer::Decode(const byte* input, unsigned int inputLen, Signedness s) { unsigned int idx(0); - byte b = input[idx++]; + byte b = 0; + if (inputLen>0) + b = input[idx]; // peek sign_ = ((s==SIGNED) && (b & 0x80)) ? NEGATIVE : POSITIVE; while (inputLen>0 && (sign_==POSITIVE ? b==0 : b==0xff)) { - inputLen--; - b = input[idx++]; + idx++; // skip + if (--inputLen>0) + b = input[idx]; // peek } reg_.CleanNew(RoundupSize(BytesToWords(inputLen))); - --idx; for (unsigned int i=inputLen; i > 0; i--) { b = input[idx++]; diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/md2.cpp mysql-5.5-5.5.43/extra/yassl/taocrypt/src/md2.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/md2.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/src/md2.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,6 @@ /* Copyright (C) 2000-2007 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/md5.cpp mysql-5.5-5.5.43/extra/yassl/taocrypt/src/md5.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/md5.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/src/md5.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2000, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -224,31 +224,31 @@ #ifdef _MSC_VER __declspec(naked) +#else + __attribute__ ((noinline)) #endif void MD5::AsmTransform(const byte* data, word32 times) { #ifdef __GNUC__ - #define AS1(x) asm(#x); - #define AS2(x, y) asm(#x ", " #y); + #define AS1(x) #x ";" + #define AS2(x, y) #x ", " #y ";" #define PROLOG() \ - asm(".intel_syntax noprefix"); \ - AS2( movd mm3, edi ) \ - AS2( movd mm4, ebx ) \ - AS2( movd mm5, esi ) \ - AS2( movd mm6, ebp ) \ - AS2( mov ecx, DWORD PTR [ebp + 8] ) \ - AS2( mov edi, DWORD PTR [ebp + 12] ) \ - AS2( mov eax, DWORD PTR [ebp + 16] ) - + __asm__ __volatile__ \ + ( \ + ".intel_syntax noprefix;" \ + "push ebx;" \ + "push ebp;" #define EPILOG() \ - AS2( movd ebp, mm6 ) \ - AS2( movd esi, mm5 ) \ - AS2( movd ebx, mm4 ) \ - AS2( mov esp, ebp ) \ - AS2( movd edi, mm3 ) \ - AS1( emms ) \ - asm(".att_syntax"); + "pop ebp;" \ + "pop ebx;" \ + "emms;" \ + ".att_syntax;" \ + : \ + : "c" (this), "D" (data), "a" (times) \ + : "%esi", "%edx", "memory", "cc" \ + ); + #else #define AS1(x) __asm x #define AS2(x, y) __asm x, y @@ -294,7 +294,11 @@ AS2( mov ecx, [esi + 8] ) // c AS2( mov edx, [esi + 12] ) // d -AS1(loopStart:) +#ifdef _MSC_VER + AS1( loopStart: ) // loopStart +#else + AS1( 0: ) // loopStart for some gas (need numeric for jump back +#endif // set up AS2( mov esi, ecx ) @@ -389,7 +393,11 @@ AS2( movd ebp, mm2 ) // times AS1( dec ebp ) AS2( movd mm2, ebp ) - AS1( jnz loopStart ) +#ifdef _MSC_VER + AS1( jnz loopStart ) // loopStart +#else + AS1( jnz 0b ) // loopStart +#endif EPILOG() diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/misc.cpp mysql-5.5-5.5.43/extra/yassl/taocrypt/src/misc.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/misc.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/src/misc.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2005, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -84,17 +84,7 @@ } -#ifdef __sun - -// Handler for pure virtual functions -namespace __Crun { - void pure_error() { - } -} - -#endif - -#if defined(__ICC) || defined(__INTEL_COMPILER) || (__GNUC__ > 2) +#if defined(__ICC) || defined(__INTEL_COMPILER) extern "C" { @@ -175,6 +165,14 @@ #ifdef TAOCRYPT_X86ASM_AVAILABLE +#ifndef _MSC_VER + static jmp_buf s_env; + static void SigIllHandler(int) + { + longjmp(s_env, 1); + } +#endif + bool HaveCpuId() { diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/rabbit.cpp mysql-5.5-5.5.43/extra/yassl/taocrypt/src/rabbit.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/rabbit.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/src/rabbit.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,15 +1,15 @@ /* - Copyright (c) 2005, 2012, Oracle and/or its affiliates. All rights reserved. - + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. + This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. - + This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. - + You should have received a copy of the GNU General Public License along with this program; see the file COPYING. If not, write to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, @@ -198,7 +198,6 @@ { /* Temporary variables */ word32 i; - byte buffer[16]; /* Encrypt/decrypt all full blocks */ while (msglen >= 16) { @@ -227,17 +226,23 @@ /* Encrypt/decrypt remaining data */ if (msglen) { + + word32 tmp[4]; + byte* buffer = (byte*)tmp; + + memset(tmp, 0, sizeof(tmp)); /* help static analysis */ + /* Iterate the system */ NextState(Work); /* Generate 16 bytes of pseudo-random data */ - *(word32*)(buffer+ 0) = LITTLE32(workCtx_.x[0] ^ + tmp[0] = LITTLE32(workCtx_.x[0] ^ (workCtx_.x[5]>>16) ^ U32V(workCtx_.x[3]<<16)); - *(word32*)(buffer+ 4) = LITTLE32(workCtx_.x[2] ^ + tmp[1] = LITTLE32(workCtx_.x[2] ^ (workCtx_.x[7]>>16) ^ U32V(workCtx_.x[5]<<16)); - *(word32*)(buffer+ 8) = LITTLE32(workCtx_.x[4] ^ + tmp[2] = LITTLE32(workCtx_.x[4] ^ (workCtx_.x[1]>>16) ^ U32V(workCtx_.x[7]<<16)); - *(word32*)(buffer+12) = LITTLE32(workCtx_.x[6] ^ + tmp[3] = LITTLE32(workCtx_.x[6] ^ (workCtx_.x[3]>>16) ^ U32V(workCtx_.x[1]<<16)); /* Encrypt/decrypt the data */ diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/random.cpp mysql-5.5-5.5.43/extra/yassl/taocrypt/src/random.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/random.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/src/random.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2005, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -27,6 +27,7 @@ #include #if defined(_WIN32) + #define _WIN32_WINNT 0x0400 #include #include #else diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/ripemd.cpp mysql-5.5-5.5.43/extra/yassl/taocrypt/src/ripemd.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/ripemd.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/src/ripemd.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2000, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -507,31 +507,31 @@ #ifdef _MSC_VER __declspec(naked) +#else + __attribute__ ((noinline)) #endif void RIPEMD160::AsmTransform(const byte* data, word32 times) { #ifdef __GNUC__ - #define AS1(x) asm(#x); - #define AS2(x, y) asm(#x ", " #y); + #define AS1(x) #x ";" + #define AS2(x, y) #x ", " #y ";" #define PROLOG() \ - asm(".intel_syntax noprefix"); \ - AS2( movd mm3, edi ) \ - AS2( movd mm4, ebx ) \ - AS2( movd mm5, esi ) \ - AS2( movd mm6, ebp ) \ - AS2( mov ecx, DWORD PTR [ebp + 8] ) \ - AS2( mov edi, DWORD PTR [ebp + 12] ) \ - AS2( mov edx, DWORD PTR [ebp + 16] ) - + __asm__ __volatile__ \ + ( \ + ".intel_syntax noprefix;" \ + "push ebx;" \ + "push ebp;" #define EPILOG() \ - AS2( movd ebp, mm6 ) \ - AS2( movd esi, mm5 ) \ - AS2( movd ebx, mm4 ) \ - AS2( mov esp, ebp ) \ - AS2( movd edi, mm3 ) \ - AS1( emms ) \ - asm(".att_syntax"); + "pop ebp;" \ + "pop ebx;" \ + "emms;" \ + ".att_syntax;" \ + : \ + : "c" (this), "D" (data), "d" (times) \ + : "%esi", "%eax", "memory", "cc" \ + ); + #else #define AS1(x) __asm x #define AS2(x, y) __asm x, y @@ -569,7 +569,11 @@ AS2( sub esp, 24 ) // make room for tmp a1 - e1 AS2( movd mm1, esi ) // store digest_ -AS1( loopStart: ) +#ifdef _MSC_VER + AS1( loopStart: ) // loopStart +#else + AS1( 0: ) // loopStart for some gas (need numeric for jump back +#endif AS2( movd mm2, edx ) // store times_ @@ -821,8 +825,14 @@ AS2( movd edx, mm2 ) // times AS2( movd edi, mm0 ) // data, already advanced AS1( dec edx ) - AS1( jnz loopStart ) +#ifdef _MSC_VER + AS1( jnz loopStart ) // loopStart +#else + AS1( jnz 0b ) // loopStart +#endif + // inline adjust + AS2( add esp, 24 ) // fix room on stack EPILOG() } diff -Nru mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/rsa.cpp mysql-5.5-5.5.43/extra/yassl/taocrypt/src/rsa.cpp --- mysql-5.5-5.5.35+dfsg/extra/yassl/taocrypt/src/rsa.cpp 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/extra/yassl/taocrypt/src/rsa.cpp 2015-02-27 08:30:34.000000000 +0000 @@ -177,7 +177,7 @@ // skip past the padding until we find the separator unsigned i=1; - while (i= CR_ERROR_FIRST && (X) <= CR_ERROR_LAST)? \ + client_errors[(X)-CR_ERROR_FIRST]: client_errors[CR_UNKNOWN_ERROR]) + #endif #define CLIENT_ERRMAP 2 /* Errormap used by my_error() */ diff -Nru mysql-5.5-5.5.35+dfsg/include/m_ctype.h mysql-5.5-5.5.43/include/m_ctype.h --- mysql-5.5-5.5.35+dfsg/include/m_ctype.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/include/m_ctype.h 2015-02-27 08:30:34.000000000 +0000 @@ -372,13 +372,13 @@ static inline my_bool my_cs_can_be_contraction_head(CHARSET_INFO *cs, my_wc_t wc) { - return ((const char *)cs->contractions)[0x40*0x40 + (wc & 0xFF)]; + return ((const char *) cs->contractions)[0x40 * 0x40 * 2 + (wc & 0xFF)]; } static inline my_bool my_cs_can_be_contraction_tail(CHARSET_INFO *cs, my_wc_t wc) { - return ((const char *)cs->contractions)[0x40*0x40 + (wc & 0xFF)]; + return ((const char *) cs->contractions)[0x40 * 0x40 * 2 + (wc & 0xFF)]; } static inline uint16* diff -Nru mysql-5.5-5.5.35+dfsg/include/my_getopt.h mysql-5.5-5.5.43/include/my_getopt.h --- mysql-5.5-5.5.35+dfsg/include/my_getopt.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/include/my_getopt.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2002, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2002, 2013, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/include/myisam.h mysql-5.5-5.5.43/include/myisam.h --- mysql-5.5-5.5.35+dfsg/include/myisam.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/include/myisam.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2000, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/include/my_net.h mysql-5.5-5.5.43/include/my_net.h --- mysql-5.5-5.5.35+dfsg/include/my_net.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/include/my_net.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -/* Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved. +/* Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/include/my_pthread.h mysql-5.5-5.5.43/include/my_pthread.h --- mysql-5.5-5.5.35+dfsg/include/my_pthread.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/include/my_pthread.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -/* Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved. +/* Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -134,7 +134,7 @@ int pthread_cond_init(pthread_cond_t *cond, const pthread_condattr_t *attr); int pthread_cond_wait(pthread_cond_t *cond, pthread_mutex_t *mutex); int pthread_cond_timedwait(pthread_cond_t *cond, pthread_mutex_t *mutex, - struct timespec *abstime); + const struct timespec *abstime); int pthread_cond_signal(pthread_cond_t *cond); int pthread_cond_broadcast(pthread_cond_t *cond); int pthread_cond_destroy(pthread_cond_t *cond); @@ -142,8 +142,18 @@ int pthread_attr_setstacksize(pthread_attr_t *connect_att,DWORD stack); int pthread_attr_destroy(pthread_attr_t *connect_att); int my_pthread_once(my_pthread_once_t *once_control,void (*init_routine)(void)); -struct tm *localtime_r(const time_t *timep,struct tm *tmp); -struct tm *gmtime_r(const time_t *timep,struct tm *tmp); + +static inline struct tm *localtime_r(const time_t *timep, struct tm *tmp) +{ + localtime_s(tmp, timep); + return tmp; +} + +static inline struct tm *gmtime_r(const time_t *clock, struct tm *res) +{ + gmtime_s(res, clock); + return res; +} void pthread_exit(void *a); int pthread_join(pthread_t thread, void **value_ptr); diff -Nru mysql-5.5-5.5.35+dfsg/include/mysql/plugin_audit.h mysql-5.5-5.5.43/include/mysql/plugin_audit.h --- mysql-5.5-5.5.35+dfsg/include/mysql/plugin_audit.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/include/mysql/plugin_audit.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -/* Copyright (c) 2007, 2011, Oracle and/or its affiliates. All rights reserved. +/* Copyright (c) 2007, 2013, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License diff -Nru mysql-5.5-5.5.35+dfsg/include/mysql/plugin.h mysql-5.5-5.5.43/include/mysql/plugin.h --- mysql-5.5-5.5.35+dfsg/include/mysql/plugin.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/include/mysql/plugin.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -/* Copyright (c) 2005, 2011, Oracle and/or its affiliates. All rights reserved. +/* Copyright (c) 2005, 2013, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/include/mysql/psi/mysql_thread.h mysql-5.5-5.5.43/include/mysql/psi/mysql_thread.h --- mysql-5.5-5.5.35+dfsg/include/mysql/psi/mysql_thread.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/include/mysql/psi/mysql_thread.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -/* Copyright (c) 2008, 2010, Oracle and/or its affiliates. All rights reserved. +/* Copyright (c) 2008, 2013, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -988,7 +988,7 @@ static inline int inline_mysql_cond_timedwait( mysql_cond_t *that, mysql_mutex_t *mutex, - struct timespec *abstime + const struct timespec *abstime #ifdef HAVE_PSI_INTERFACE , const char *src_file, uint src_line #endif diff -Nru mysql-5.5-5.5.35+dfsg/include/mysql/thread_pool_priv.h mysql-5.5-5.5.43/include/mysql/thread_pool_priv.h --- mysql-5.5-5.5.35+dfsg/include/mysql/thread_pool_priv.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/include/mysql/thread_pool_priv.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,5 +1,5 @@ /* - Copyright (c) 2010, 2012, Oracle and/or its affiliates. All rights reserved. + Copyright (c) 2010, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -49,6 +49,8 @@ void thd_set_thread_stack(THD *thd, char *stack_start); void thd_lock_thread_count(THD *thd); void thd_unlock_thread_count(THD *thd); +void thd_lock_thread_remove(THD *thd); +void thd_unlock_thread_remove(THD *thd); void thd_close_connection(THD *thd); THD *thd_get_current_thd(); void thd_new_connection_setup(THD *thd, char *stack_start); diff -Nru mysql-5.5-5.5.35+dfsg/include/mysql_version.h.in mysql-5.5-5.5.43/include/mysql_version.h.in --- mysql-5.5-5.5.35+dfsg/include/mysql_version.h.in 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/include/mysql_version.h.in 2015-02-27 08:30:34.000000000 +0000 @@ -1,6 +1,7 @@ -/* Copyright (c) 1996, 1999-2004, 2007 MySQL AB - Use is subject to license terms - This file is public domain and comes with NO WARRANTY of any kind */ +/* Copyright Abandoned 1996,1999 TCX DataKonsult AB & Monty Program KB + & Detron HB, 1996, 1999-2004, 2007 MySQL AB. + This file is public domain and comes with NO WARRANTY of any kind +*/ /* Version numbers for protocol & mysqld */ diff -Nru mysql-5.5-5.5.35+dfsg/include/t_ctype.h mysql-5.5-5.5.43/include/t_ctype.h --- mysql-5.5-5.5.35+dfsg/include/t_ctype.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/include/t_ctype.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,5 @@ /* Copyright (C) 2000 MySQL AB + Use is subject to license terms This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/include/welcome_copyright_notice.h mysql-5.5-5.5.43/include/welcome_copyright_notice.h --- mysql-5.5-5.5.35+dfsg/include/welcome_copyright_notice.h 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/include/welcome_copyright_notice.h 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -/* Copyright (c) 2010, 2012, Oracle and/or its affiliates. All rights reserved. +/* Copyright (c) 2010, 2015, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -16,7 +16,7 @@ #ifndef _welcome_copyright_notice_h_ #define _welcome_copyright_notice_h_ -#define COPYRIGHT_NOTICE_CURRENT_YEAR "2013" +#define COPYRIGHT_NOTICE_CURRENT_YEAR "2015" /* This define specifies copyright notice which is displayed by every MySQL diff -Nru mysql-5.5-5.5.35+dfsg/INSTALL-SOURCE mysql-5.5-5.5.43/INSTALL-SOURCE --- mysql-5.5-5.5.35+dfsg/INSTALL-SOURCE 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/INSTALL-SOURCE 2015-02-27 08:30:42.000000000 +0000 @@ -1,384 +1,222 @@ +Chapter 2 Installing and Upgrading MySQL -Chapter 2. Installing and Upgrading MySQL - - This chapter describes how to obtain and install MySQL. A summary - of the procedure follows and later sections provide the details. - If you plan to upgrade an existing version of MySQL to a newer - version rather than install MySQL for the first time, see Section - 2.12.1, "Upgrading MySQL," for information about upgrade - procedures and about issues that you should consider before - upgrading. - - If you are interested in migrating to MySQL from another database - system, you may wish to read Section B.8, "MySQL 5.5 FAQ: - Migration," which contains answers to some common questions - concerning migration issues. + This chapter describes how to obtain and install MySQL. A + summary of the procedure follows and later sections provide + the details. If you plan to upgrade an existing version of + MySQL to a newer version rather than install MySQL for the + first time, see Section 2.11.1, "Upgrading MySQL," for + information about upgrade procedures and about issues that + you should consider before upgrading. + + If you are interested in migrating to MySQL from another + database system, you may wish to read Section A.8, "MySQL 5.5 + FAQ: Migration," which contains answers to some common + questions concerning migration issues. If you are migrating from MySQL Enterprise Edition to MySQL - Community Server, see Section 2.12.2.2, "Downgrading from MySQL - Enterprise Edition to MySQL Community Server." + Community Server, see Section 2.11.2.2, "Downgrading from + MySQL Enterprise Edition to MySQL Community Server." - Installation of MySQL generally follows the steps outlined here: + Installation of MySQL generally follows the steps outlined + here: 1. Determine whether MySQL runs and is supported on your platform. - Please note that not all platforms are equally suitable for - running MySQL, and that not all platforms on which MySQL is - known to run are officially supported by Oracle Corporation: + Please note that not all platforms are equally suitable + for running MySQL, and that not all platforms on which + MySQL is known to run are officially supported by Oracle + Corporation: 2. Choose which distribution to install. Several versions of MySQL are available, and most are - available in several distribution formats. You can choose from - pre-packaged distributions containing binary (precompiled) - programs or source code. When in doubt, use a binary - distribution. We also provide public access to our current - source tree for those who want to see our most recent - developments and help us test new code. To determine which - version and type of distribution you should use, see Section - 2.1.2, "Choosing Which MySQL Distribution to Install." + available in several distribution formats. You can choose + from pre-packaged distributions containing binary + (precompiled) programs or source code. When in doubt, use + a binary distribution. We also provide public access to + our current source tree for those who want to see our + most recent developments and help us test new code. To + determine which version and type of distribution you + should use, see Section 2.1.1, "Which MySQL Version and + Distribution to Install." 3. Download the distribution that you want to install. - For instructions, see Section 2.1.3, "How to Get MySQL." To - verify the integrity of the distribution, use the instructions - in Section 2.1.4, "Verifying Package Integrity Using MD5 - Checksums or GnuPG." + For instructions, see Section 2.1.2, "How to Get MySQL." + To verify the integrity of the distribution, use the + instructions in Section 2.1.3, "Verifying Package + Integrity Using MD5 Checksums or GnuPG." 4. Install the distribution. To install MySQL from a binary distribution, use the - instructions in Section 2.2, "Installing MySQL on Unix/Linux - Using Generic Binaries." + instructions in Section 2.2, "Installing MySQL on + Unix/Linux Using Generic Binaries." To install MySQL from a source distribution or from the current development source tree, use the instructions in - Section 2.10, "Installing MySQL from Source." + Section 2.9, "Installing MySQL from Source." 5. Perform any necessary postinstallation setup. - After installing MySQL, see Section 2.11, "Postinstallation - Setup and Testing" for information about making sure the MySQL - server is working properly. Also refer to the information - provided in Section 2.11.2, "Securing the Initial MySQL - Accounts." This section describes how to secure the initial - MySQL user accounts, which have no passwords until you assign - passwords. The section applies whether you install MySQL using - a binary or source distribution. - - 6. If you want to run the MySQL benchmark scripts, Perl support - for MySQL must be available. See Section 2.14, "Perl - Installation Notes." + After installing MySQL, see Section 2.10, + "Postinstallation Setup and Testing" for information + about making sure the MySQL server is working properly. + Also refer to the information provided in Section 2.10.2, + "Securing the Initial MySQL Accounts." This section + describes how to secure the initial MySQL user accounts, + which have no passwords until you assign passwords. The + section applies whether you install MySQL using a binary + or source distribution. + + 6. If you want to run the MySQL benchmark scripts, Perl + support for MySQL must be available. See Section 2.13, + "Perl Installation Notes." Instructions for installing MySQL on different platforms and environments is available on a platform by platform basis: * Unix, Linux, FreeBSD - For instructions on installing MySQL on most Linux and Unix - platforms using a generic binary (for example, a .tar.gz - package), see Section 2.2, "Installing MySQL on Unix/Linux - Using Generic Binaries." - For information on building MySQL entirely from the source - code distributions or the source code repositories, see - Section 2.10, "Installing MySQL from Source" - For specific platform help on installation, configuration, and - building from source see the corresponding platform section: - - + Linux, including notes on distribution specific methods, - see Section 2.5, "Installing MySQL on Linux." - - + Solaris and OpenSolaris, including PKG and IPS formats, - see Section 2.7, "Installing MySQL on Solaris and - OpenSolaris." - - + IBM AIX, see Section 2.7, "Installing MySQL on Solaris - and OpenSolaris." + For instructions on installing MySQL on most Linux and + Unix platforms using a generic binary (for example, a + .tar.gz package), see Section 2.2, "Installing MySQL on + Unix/Linux Using Generic Binaries." + For information on building MySQL entirely from the + source code distributions or the source code + repositories, see Section 2.9, "Installing MySQL from + Source" + For specific platform help on installation, + configuration, and building from source see the + corresponding platform section: + + + Linux, including notes on distribution specific + methods, see Section 2.5, "Installing MySQL on + Linux." + + + Solaris and OpenSolaris, including PKG and IPS + formats, see Section 2.7, "Installing MySQL on + Solaris and OpenSolaris." - + Hewlett-Packard HP-UX, including the DEPOT package - format, see Section 2.8, "Installing MySQL on HP-UX." + + IBM AIX, see Section 2.7, "Installing MySQL on + Solaris and OpenSolaris." - + FreeBSD, see Section 2.9, "Installing MySQL on FreeBSD." + + FreeBSD, see Section 2.8, "Installing MySQL on + FreeBSD." * Microsoft Windows - For instructions on installing MySQL on Microsoft Windows, - using either a Zipped binary or an MSI package, see Section - 2.3, "Installing MySQL on Microsoft Windows." - For information on using the MySQL Server Instance Config - Wizard, see Section 2.3.6, "MySQL Server Instance - Configuration Wizard." - For details and instructions on building MySQL from source - code using Microsoft Visual Studio, see Section 2.10, - "Installing MySQL from Source." - - * Mac OS X - For installation on Mac OS X, including using both the binary - package and native PKG formats, see Section 2.4, "Installing - MySQL on Mac OS X." - For information on making use of the MySQL Startup Item to + For instructions on installing MySQL on Microsoft + Windows, using either the MySQL Installer standalone MSI, + or Zipped binary, see Section 2.3, "Installing MySQL on + Microsoft Windows." + For information about managing MySQL instances, see + Section 2.3.4, "MySQL Notifier." + For details and instructions on building MySQL from + source code using Microsoft Visual Studio, see Section + 2.9, "Installing MySQL from Source." + + * OS X + For installation on OS X, including using both the binary + package and native PKG formats, see Section 2.4, + "Installing MySQL on OS X." + For information on making use of an OS X Launch Daemon to automatically start and stop MySQL, see Section 2.4.3, - "Installing the MySQL Startup Item." + "Installing a MySQL Launch Daemon." For information on the MySQL Preference Pane, see Section - 2.4.4, "Installing and Using the MySQL Preference Pane." + 2.4.5, "Installing and Using the MySQL Preference Pane." -2.1. General Installation Guidance +2.1 General Installation Guidance The immediately following sections contain the information - necessary to choose, download, and verify your distribution. The - instructions in later sections of the chapter describe how to - install the distribution that you choose. For binary - distributions, see the instructions at Section 2.2, "Installing - MySQL on Unix/Linux Using Generic Binaries" or the corresponding - section for your platform if available. To build MySQL from - source, use the instructions in Section 2.10, "Installing MySQL - from Source." - -2.1.1. Operating Systems Supported by MySQL Community Server - - This section lists the operating systems on which MySQL Community - Server is known to run. - Important - - Oracle Corporation does not necessarily provide official support - for all the platforms listed in this section. For information - about those platforms that are officially supported, see - http://www.mysql.com/support/supportedplatforms/database.html on - the MySQL Web site. - - We use CMake, so it is possible to port MySQL to all modern - systems that have a C++ compiler and a working implementation of - POSIX threads. (Thread support is needed for the server. To - compile only the client code, the only requirement is a C++ - compiler.) - - MySQL has been reported to compile successfully on the following - systems: - - * FreeBSD 5.x and up. See Section 2.9, "Installing MySQL on - FreeBSD." + necessary to choose, download, and verify your distribution. + The instructions in later sections of the chapter describe + how to install the distribution that you choose. For binary + distributions, see the instructions at Section 2.2, + "Installing MySQL on Unix/Linux Using Generic Binaries" or + the corresponding section for your platform if available. To + build MySQL from source, use the instructions in Section 2.9, + "Installing MySQL from Source." + +2.1.1 Which MySQL Version and Distribution to Install + + MySQL is available on a number of operating systems and + platforms. For information about those platforms that are + officially supported, see + http://www.mysql.com/support/supportedplatforms/database.html + on the MySQL Web site. + + When preparing to install MySQL, you should decide which + version to use, and which distribution format (binary or + source) to use for the installation. + + First, decide if you want to install a development release or + a GA release. Development releases have the newest features, + but are not recommended for production use. GA (General + Availability) releases, also called production or stable + releases, are meant for production use. We recommend to use + the most recent GA release. + + The naming scheme in MySQL 5.5 uses release names that + consist of three numbers and a suffix; for example, + mysql-5.6.1-m1. The numbers within the release name are + interpreted as follows: + + * The first number (5) is the major version and describes + the file format. All MySQL 5 releases have the same file + format. + + * The second number (6) is the release level. Taken + together, the major version and release level constitute + the release series number. + + * The third number (1) is the version number within the + release series. This is incremented for each new release. + Usually you want the latest version for the series you + have chosen. + + For each minor update, the last number in the version string + is incremented. When there are major new features or minor + incompatibilities with previous versions, the second number + in the version string is incremented. When the file format + changes, the first number is increased. + + Release names can also include a suffix that indicates the + stability level of the release. Releases within a series + progress through a set of suffixes to indicate how the + stability level improves. The possible suffixes are: - * HP-UX 11.x. See Section 2.8, "Installing MySQL on HP-UX." - - * Linux. Builds on all recent Linux distributions based on the - 2.6 kernel. See Section 2.5, "Installing MySQL on Linux." - - * Mac OS X. See Section 2.4, "Installing MySQL on Mac OS X." - - * Solaris 2.8 on SPARC and x86. See Section 2.7, "Installing - MySQL on Solaris and OpenSolaris." - - * Microsoft Windows. See Section 2.3, "Installing MySQL on - Microsoft Windows." - - MySQL has also been known to run on other systems in the past. See - Section 2.1, "General Installation Guidance." Some porting effort - might be required for current versions of MySQL on these systems. - - Not all platforms are equally well-suited for running MySQL. How - well a certain platform is suited for a high-load mission-critical - MySQL server is determined by the following factors: - - * General stability of the thread library. A platform may have - an excellent reputation otherwise, but MySQL is only as stable - as the thread library it calls, even if everything else is - perfect. - - * The capability of the kernel and the thread library to take - advantage of symmetric multi-processor (SMP) systems. In other - words, when a process creates a thread, it should be possible - for that thread to run on a CPU different from the original - process. - - * The capability of the kernel and the thread library to run - many threads that acquire and release a mutex over a short - critical region frequently without excessive context switches. - If the implementation of pthread_mutex_lock() is too anxious - to yield CPU time, this hurts MySQL tremendously. If this - issue is not taken care of, adding extra CPUs actually makes - MySQL slower. - - * General file system stability and performance. - - * Table size. If your tables are large, performance is affected - by the ability of the file system to deal with large files and - dealing with them efficiently. - - * Our level of expertise here at Oracle Corporation with the - platform. If we know a platform well, we enable - platform-specific optimizations and fixes at compile time. We - can also provide advice on configuring your system optimally - for MySQL. - - * The amount of testing we have done internally for similar - configurations. - - * The number of users that have run MySQL successfully on the - platform in similar configurations. If this number is high, - the likelihood of encountering platform-specific surprises is - much smaller. - -2.1.2. Choosing Which MySQL Distribution to Install - - When preparing to install MySQL, you should decide which version - to use. MySQL development occurs in several release series, and - you can pick the one that best fits your needs. After deciding - which version to install, you can choose a distribution format. - Releases are available in binary or source format. - -2.1.2.1. Choosing Which Version of MySQL to Install - - The first decision to make is whether you want to use a production - (stable) release or a development release. In the MySQL - development process, multiple release series co-exist, each at a - different stage of maturity. - -Production Releases - - - * MySQL 5.6: Latest General Availability (Production) release - - * MySQL 5.5: Previous General Availability (Production) release - - * MySQL 5.1: Older General Availability (Production) release - - * MySQL 5.0: Older Production release nearing the end of the - product lifecycle - - MySQL 4.1, 4.0, and 3.23 are old releases that are no longer - supported. - - See http://www.mysql.com/about/legal/lifecycle/ for information - about support policies and schedules. - - Normally, if you are beginning to use MySQL for the first time or - trying to port it to some system for which there is no binary - distribution, use the most recent General Availability series - listed in the preceding descriptions. All MySQL releases, even - those from development series, are checked with the MySQL - benchmarks and an extensive test suite before being issued. - - If you are running an older system and want to upgrade, but do not - want to take the chance of having a nonseamless upgrade, you - should upgrade to the latest version in the same release series - you are using (where only the last part of the version number is - newer than yours). We have tried to fix only fatal bugs and make - only small, relatively "safe" changes to that version. - - If you want to use new features not present in the production - release series, you can use a version from a development series. - Be aware that development releases are not as stable as production - releases. - - We do not use a complete code freeze because this prevents us from - making bugfixes and other fixes that must be done. We may add - small things that should not affect anything that currently works - in a production release. Naturally, relevant bugfixes from an - earlier series propagate to later series. - - If you want to use the very latest sources containing all current - patches and bugfixes, you can use one of our source code - repositories (see Section 2.10.3, "Installing MySQL Using a - Development Source Tree"). These are not "releases" as such, but - are available as previews of the code on which future releases are - to be based. - - The naming scheme in MySQL 5.5 uses release names that consist of - three numbers and a suffix; for example, mysql-5.5.6-m3. The - numbers within the release name are interpreted as follows: - - * The first number (5) is the major version and describes the - file format. All MySQL 5 releases have the same file format. - - * The second number (5) is the release level. Taken together, - the major version and release level constitute the release - series number. - - * The third number (6) is the version number within the release - series. This is incremented for each new release. Usually you - want the latest version for the series you have chosen. - - For each minor update, the last number in the version string is - incremented. When there are major new features or minor - incompatibilities with previous versions, the second number in the - version string is incremented. When the file format changes, the - first number is increased. - - Release names also include a suffix to indicates the stability - level of the release. Releases within a series progress through a - set of suffixes to indicate how the stability level improves. The - possible suffixes are: - - * mN (for example, m1, m2, m3, ...) indicate a milestone number. - MySQL development uses a milestone model, in which each - milestone proceeds through a small number of versions with a - tight focus on a small subset of thoroughly tested features. - Following the releases for one milestone, development proceeds - with another small number of releases that focuses on the next - small set of features, also thoroughly tested. Features within - milestone releases may be considered to be of pre-production - quality. + * If there is no suffix, it indicates that the release is a + General Availability (GA) or Production release. GA + releases are stable, having successfully passed through + all earlier release stages and are believed to be + reliable, free of serious bugs, and suitable for use in + production systems. Only critical bugfixes are applied to + the release. + + * mN (for example, m1, m2, m3, ...) indicate a milestone + number. MySQL development uses a milestone model, in + which each milestone proceeds through a small number of + versions with a tight focus on a small subset of + thoroughly tested features. Following the releases for + one milestone, development proceeds with another small + number of releases that focuses on the next small set of + features, also thoroughly tested. Features within + milestone releases may be considered to be of + pre-production quality. * rc indicates a Release Candidate. Release candidates are - believed to be stable, having passed all of MySQL's internal - testing, and with all known fatal runtime bugs fixed. However, - the release has not been in widespread use long enough to know - for sure that all bugs have been identified. Only minor fixes - are added. - - * If there is no suffix, it indicates that the release is a - General Availability (GA) or Production release. GA releases - are stable, having successfully passed through all earlier - release stages and are believed to be reliable, free of - serious bugs, and suitable for use in production systems. Only - critical bugfixes are applied to the release. - - All releases of MySQL are run through our standard tests and - benchmarks to ensure that they are relatively safe to use. Because - the standard tests are extended over time to check for all - previously found bugs, the test suite keeps getting better. - - All releases have been tested at least with these tools: - - * An internal test suite. The mysql-test directory contains an - extensive set of test cases. We run these tests for every - server binary. See Section 23.1.2, "The MySQL Test Suite," for - more information about this test suite. - - * The MySQL benchmark suite. This suite runs a range of common - queries. It is also a test to determine whether the latest - batch of optimizations actually made the code faster. See - Section 8.12.2, "The MySQL Benchmark Suite." - - We also perform additional integration and nonfunctional testing - of the latest MySQL version in our internal production - environment. Integration testing is done with different - connectors, storage engines, replication modes, backup, - partitioning, stored programs, and so forth in various - combinations. Additional nonfunctional testing is done in areas of - performance, concurrency, stress, high volume, upgrade and - downgrade. - -2.1.2.2. Choosing a Distribution Format - - After choosing which version of MySQL to install, you should - decide whether to use a binary distribution or a source - distribution. In most cases, you should probably use a binary - distribution, if one exists for your platform. Binary - distributions are available in native format for many platforms, - such as RPM packages for Linux, DMG packages for Mac OS X, and PKG - packages for Solaris. Distributions are also available in more - generic formats such as Zip archives or compressed tar files. - - Reasons to choose a binary distribution include the following: - - * Binary distributions generally are easier to install than - source distributions. - - * To satisfy different user requirements, we provide several - servers in binary distributions. mysqld is an optimized server - that is a smaller, faster binary. mysqld-debug is compiled - with debugging support. - Each of these servers is compiled from the same source - distribution, though with different configuration options. All - native MySQL clients can connect to servers from either MySQL - version. + believed to be stable, having passed all of MySQL's + internal testing, and with all known fatal runtime bugs + fixed. However, the release has not been in widespread + use long enough to know for sure that all bugs have been + identified. Only minor fixes are added. + + Once you've chosen which MySQL version to install, you need + to decide which distribution to install for your operating + system. For most use cases, a binary distribution is the + right choice. Binary distributions are available in native + format for many platforms, such as RPM packages for Linux, or + DMG packages for OS X. Distributions are also available in + more generic formats such as Zip archives or compressed tar + files. On Windows, you can use the MySQL Installer to install + a binary distribution. - Under some circumstances, you may be better off installing MySQL - from a source distribution: + Under some circumstances, you may be better off installing + MySQL from a source distribution: * You want to install MySQL at some explicit location. The standard binary distributions are ready to run at any @@ -386,103 +224,66 @@ flexibility to place MySQL components where you want. * You want to configure mysqld to ensure that features are - available that might not be included in the standard binary - distributions. Here is a list of the most common extra options - that you may want to use to ensure feature availability: + available that might not be included in the standard + binary distributions. Here is a list of the most common + extra options that you may want to use to ensure feature + availability: + -DWITH_LIBWRAP=1 for TCP wrappers support. - + -DWITH_ZLIB={system|bundled} for features that depend on - compression + + -DWITH_ZLIB={system|bundled} for features that + depend on compression + -DWITH_DEBUG=1 for debugging support - For additional information, see Section 2.10.4, "MySQL + For additional information, see Section 2.9.4, "MySQL Source-Configuration Options." - * You want to configure mysqld without some features that are - included in the standard binary distributions. For example, - distributions normally are compiled with support for all - character sets. If you want a smaller MySQL server, you can - recompile it with support for only the character sets you - need. + * You want to configure mysqld without some features that + are included in the standard binary distributions. For + example, distributions normally are compiled with support + for all character sets. If you want a smaller MySQL + server, you can recompile it with support for only the + character sets you need. - * You want to use the latest sources from one of the Bazaar + * You want to use the latest sources from one of the Git repositories to have access to all current bugfixes. For - example, if you have found a bug and reported it to the MySQL - development team, the bugfix is committed to the source - repository and you can access it there. The bugfix does not - appear in a release until a release actually is issued. - - * You want to read (or modify) the C and C++ code that makes up - MySQL. For this purpose, you should get a source distribution, - because the source code is always the ultimate manual. + example, if you have found a bug and reported it to the + MySQL development team, the bugfix is committed to the + source repository and you can access it there. The bugfix + does not appear in a release until a release actually is + issued. + + * You want to read (or modify) the C and C++ code that + makes up MySQL. For this purpose, you should get a source + distribution. * Source distributions contain more tests and examples than binary distributions. -2.1.2.3. How and When Updates Are Released +2.1.2 How to Get MySQL - MySQL is evolving quite rapidly and we want to share new - developments with other MySQL users. We try to produce a new - release whenever we have new and useful features that others also - seem to have a need for. - - We also try to help users who request features that are easy to - implement. We take note of what our licensed users want, and we - especially take note of what our support customers want and try to - help them in this regard. - - No one is required to download a new release. The Release Notes - (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/) help you - determine whether the new release has something you really want. - - We use the following policy when updating MySQL: - - * Enterprise Server releases are meant to appear every 18 - months, supplemented by quarterly service packs and monthly - rapid updates. Community Server releases are meant to appear 2 - to 3 times per year. - - * Releases are issued within each series. For each release, the - last number in the version is one more than the previous - release within the same series. - - * Binary distributions for some platforms are made by us for - major releases. Other people may make binary distributions for - other systems, but probably less frequently. - - * We make fixes available as soon as we have identified and - corrected small or noncritical but annoying bugs. The fixes - are available in source form immediately from our public - Bazaar repositories, and are included in the next release. - - * If by any chance a security vulnerability or critical bug is - found in a release, our policy is to fix it in a new release - as soon as possible. (We would like other companies to do - this, too!) - -2.1.3. How to Get MySQL - - Check our downloads page at http://dev.mysql.com/downloads/ for - information about the current version of MySQL and for downloading - instructions. For a complete up-to-date list of MySQL download - mirror sites, see http://dev.mysql.com/downloads/mirrors.html. You - can also find information there about becoming a MySQL mirror site - and how to report a bad or out-of-date mirror. + Check our downloads page at http://dev.mysql.com/downloads/ + for information about the current version of MySQL and for + downloading instructions. For a complete up-to-date list of + MySQL download mirror sites, see + http://dev.mysql.com/downloads/mirrors.html. You can also + find information there about becoming a MySQL mirror site and + how to report a bad or out-of-date mirror. - To obtain the latest development source, see Section 2.10.3, + To obtain the latest development source, see Section 2.9.3, "Installing MySQL Using a Development Source Tree." -2.1.4. Verifying Package Integrity Using MD5 Checksums or GnuPG +2.1.3 Verifying Package Integrity Using MD5 Checksums or GnuPG - After you have downloaded the MySQL package that suits your needs - and before you attempt to install it, you should make sure that it - is intact and has not been tampered with. There are three means of - integrity checking: + After you have downloaded the MySQL package that suits your + needs and before you attempt to install it, you should make + sure that it is intact and has not been tampered with. There + are three means of integrity checking: * MD5 checksums - * Cryptographic signatures using GnuPG, the GNU Privacy Guard + * Cryptographic signatures using GnuPG, the GNU Privacy + Guard * For RPM packages, the built-in RPM integrity verification mechanism @@ -490,72 +291,74 @@ The following sections describe how to use these methods. If you notice that the MD5 checksum or GPG signatures do not - match, first try to download the respective package one more time, - perhaps from another mirror site. + match, first try to download the respective package one more + time, perhaps from another mirror site. -2.1.4.1. Verifying the MD5 Checksum +2.1.3.1 Verifying the MD5 Checksum - After you have downloaded a MySQL package, you should make sure - that its MD5 checksum matches the one provided on the MySQL - download pages. Each package has an individual checksum that you - can verify against the package that you downloaded. The correct - MD5 checksum is listed on the downloads page for each MySQL - product, and you will compare it against the MD5 checksum of the - file (product) that you download. - - Each operating system and setup offers its own version of tools - for checking the MD5 checksum. Typically the command is named - md5sum, or it may be named md5, and some operating systems do not - ship it at all. On Linux, it is part of the GNU Text Utilities - package, which is available for a wide range of platforms. You can - also download the source code from - http://www.gnu.org/software/textutils/. If you have OpenSSL - installed, you can use the command openssl md5 package_name - instead. A Windows implementation of the md5 command line utility - is available from http://www.fourmilab.ch/md5/. winMd5Sum is a - graphical MD5 checking tool that can be obtained from - http://www.nullriver.com/index/products/winmd5sum. Our Microsoft - Windows examples will assume the name md5.exe. + After you have downloaded a MySQL package, you should make + sure that its MD5 checksum matches the one provided on the + MySQL download pages. Each package has an individual checksum + that you can verify against the package that you downloaded. + The correct MD5 checksum is listed on the downloads page for + each MySQL product, and you will compare it against the MD5 + checksum of the file (product) that you download. + + Each operating system and setup offers its own version of + tools for checking the MD5 checksum. Typically the command is + named md5sum, or it may be named md5, and some operating + systems do not ship it at all. On Linux, it is part of the + GNU Text Utilities package, which is available for a wide + range of platforms. You can also download the source code + from http://www.gnu.org/software/textutils/. If you have + OpenSSL installed, you can use the command openssl md5 + package_name instead. A Windows implementation of the md5 + command line utility is available from + http://www.fourmilab.ch/md5/. winMd5Sum is a graphical MD5 + checking tool that can be obtained from + http://www.nullriver.com/index/products/winmd5sum. Our + Microsoft Windows examples will assume the name md5.exe. Linux and Microsoft Windows examples: -shell> md5sum mysql-standard-5.5.36-linux-i686.tar.gz -aaab65abbec64d5e907dcd41b8699945 mysql-standard-5.5.36-linux-i686.ta -r.gz -shell> md5.exe mysql-installer-community-5.5.36.msi -aaab65abbec64d5e907dcd41b8699945 mysql-installer-community-5.5.36.ms -i +shell> md5sum mysql-standard-5.5.44-linux-i686.tar.gz +aaab65abbec64d5e907dcd41b8699945 mysql-standard-5.5.44-linux-i686.tar +.gz + +shell> md5.exe mysql-installer-community-5.5.44.msi +aaab65abbec64d5e907dcd41b8699945 mysql-installer-community-5.5.44.msi You should verify that the resulting checksum (the string of - hexadecimal digits) matches the one displayed on the download page - immediately below the respective package. + hexadecimal digits) matches the one displayed on the download + page immediately below the respective package. Note - Make sure to verify the checksum of the archive file (for example, - the .zip, .tar.gz, or .msi file) and not of the files that are - contained inside of the archive. In other words, verify the file - before extracting its contents. + Make sure to verify the checksum of the archive file (for + example, the .zip, .tar.gz, or .msi file) and not of the + files that are contained inside of the archive. In other + words, verify the file before extracting its contents. -2.1.4.2. Signature Checking Using GnuPG +2.1.3.2 Signature Checking Using GnuPG - Another method of verifying the integrity and authenticity of a - package is to use cryptographic signatures. This is more reliable - than using MD5 checksums, but requires more work. + Another method of verifying the integrity and authenticity of + a package is to use cryptographic signatures. This is more + reliable than using MD5 checksums, but requires more work. We sign MySQL downloadable packages with GnuPG (GNU Privacy Guard). GnuPG is an Open Source alternative to the well-known Pretty Good Privacy (PGP) by Phil Zimmermann. See - http://www.gnupg.org/ for more information about GnuPG and how to - obtain and install it on your system. Most Linux distributions - ship with GnuPG installed by default. For more information about - GnuPG, see http://www.openpgp.org/. - - To verify the signature for a specific package, you first need to - obtain a copy of our public GPG build key, which you can download - from http://pgp.mit.edu/. The key that you want to obtain is named - mysql-build@oss.oracle.com. Alternatively, you can cut and paste - the key directly from the following text: + http://www.gnupg.org/ for more information about GnuPG and + how to obtain and install it on your system. Most Linux + distributions ship with GnuPG installed by default. For more + information about GnuPG, see http://www.openpgp.org/. + + To verify the signature for a specific package, you first + need to obtain a copy of our public GPG build key, which you + can download from http://pgp.mit.edu/. The key that you want + to obtain is named mysql-build@oss.oracle.com. Alternatively, + you can cut and paste the key directly from the following + text: -----BEGIN PGP PUBLIC KEY BLOCK----- -Version: PGP Universal 2.9.1 (Build 347) +Version: GnuPG v1.4.9 (SunOS) mQGiBD4+owwRBAC14GIfUfCyEDSIePvEW3SAFUdJBtoQHH/nJKZyQT7h9bPlUWC3 RODjQReyCITRrdwyrKUGku2FmeVGwn2u2WmDMNABLnpprWPkBdCk96+OmSLN9brZ @@ -566,34 +369,95 @@ kYpXBACmWpP8NJTkamEnPCia2ZoOHODANwpUkP43I7jsDmgtobZX9qnrAXw+uNDI QJEXM6FSbi0LLtZciNlYsafwAPEOMDKpMqAK6IyisNtPvaLd8lH0bPAnWqcyefep rv0sxxqUEMcM3o7wwgfN83POkDasDbs3pjwPhxvhz6//62zQJ7Q2TXlTUUwgUmVs -ZWFzZSBFbmdpbmVlcmluZyA8bXlzcWwtYnVpbGRAb3NzLm9yYWNsZS5jb20+iGYE -ExECACYCGyMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAUCTnc+KgUJE/sCFQAKCRCM -cY07UHLh9SbMAJ4l1+qBz2BZNSGCZwwA6YbhGPC7FwCgp8z5TzIw4YQuL5NGJ/sy -0oSazqmJASIEEAECAAwFAk53QS4FAwASdQAACgkQlxC4m8pXrXwJ8Qf/be/UO9mq -foc2sMyhwMpN4/fdBWwfLkA12FXQDOQMvwH9HsmEjnfUgYKXschZRi+DuHXe1P7l -8G2aQLubhBsQf9ejKvRFTzuWMQkdIq+6Koulxv6ofkCcv3d1xtO2W7nb5yxcpVBP -rRfGFGebJvZa58DymCNgyGtAU6AOz4veavNmI2+GIDQsY66+tYDvZ+CxwzdYu+HD -V9HmrJfc6deM0mnBn7SRjqzxJPgoTQhihTav6q/R5/2p5NvQ/H84OgS6GjosfGc2 -duUDzCP/kheMRKfzuyKCOHQPtJuIj8++gfpHtEU7IDUX1So3c9n0PdpeBvclsDbp -RnCNxQWU4mBot7kCDQQ+PqMdEAgA7+GJfxbMdY4wslPnjH9rF4N2qfWsEN/lxaZo -JYc3a6M02WCnHl6ahT2/tBK2w1QI4YFteR47gCvtgb6O1JHffOo2HfLmRDRiRjd1 -DTCHqeyX7CHhcghj/dNRlW2Z0l5QFEcmV9U0Vhp3aFfWC4Ujfs3LU+hkAWzE7zaD -5cH9J7yv/6xuZVw411x0h4UqsTcWMu0iM1BzELqX1DY7LwoPEb/O9Rkbf4fmLe11 -EzIaCa4PqARXQZc4dhSinMt6K3X4BrRsKTfozBu74F47D8Ilbf5vSYHbuE5p/1oI -Dznkg/p8kW+3FxuWrycciqFTcNz215yyX39LXFnlLzKUb/F5GwADBQf+Lwqqa8CG -rRfsOAJxim63CHfty5mUc5rUSnTslGYEIOCR1BeQauyPZbPDsDD9MZ1ZaSafanFv -wFG6Llx9xkU7tzq+vKLoWkm4u5xf3vn55VjnSd1aQ9eQnUcXiL4cnBGoTbOWI39E -cyzgslzBdC++MPjcQTcA7p6JUVsP6oAB3FQWg54tuUo0Ec8bsM8b3Ev42LmuQT5N -dKHGwHsXTPtl0klk4bQk4OajHsiy1BMahpT27jWjJlMiJc+IWJ0mghkKHt926s/y -mfdf5HkdQ1cyvsz5tryVI3Fx78XeSYfQvuuwqp2H139pXGEkg0n6KdUOetdZWhe7 -0YGNPw1yjWJT1IhUBBgRAgAMBQJOdz3tBQkT+wG4ABIHZUdQRwABAQkQjHGNO1By -4fUUmwCbBYr2+bBEn/L2BOcnw9Z/QFWuhRMAoKVgCFm5fadQ3Afi+UQlAcOphrnJ -=Eto8 +ZWFzZSBFbmdpbmVlcmluZyA8bXlzcWwtYnVpbGRAb3NzLm9yYWNsZS5jb20+iGkE +ExECACkCGyMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAIZAQUCUwHUZgUJGmbLywAK +CRCMcY07UHLh9V+DAKCjS1gGwgVI/eut+5L+l2v3ybl+ZgCcD7ZoA341HtoroV3U +6xRD09fUgeq0O015U1FMIFBhY2thZ2Ugc2lnbmluZyBrZXkgKHd3dy5teXNxbC5j +b20pIDxidWlsZEBteXNxbC5jb20+iG8EMBECAC8FAk53Pa0oHSBidWlsZEBteXNx +bC5jb20gd2lsbCBzdG9wIHdvcmtpbmcgc29vbgAKCRCMcY07UHLh9bU9AJ9xDK0o +xJFL9vTl9OSZC4lX0K9AzwCcCrS9cnJyz79eaRjL0s2r/CcljdyIZQQTEQIAHQUC +R6yUtAUJDTBYqAULBwoDBAMVAwIDFgIBAheAABIJEIxxjTtQcuH1B2VHUEcAAQGu +kgCffz4GUEjzXkOi71VcwgCxASTgbe0An34LPr1j9fCbrXWXO14msIADfb5piEwE +ExECAAwFAj4+o9EFgwlmALsACgkQSVDhKrJykfIk4QCfWbEeKN+3TRspe+5xKj+k +QJSammIAnjUz0xFWPlVx0f8o38qNG1bq0cU9iEwEExECAAwFAj5CggMFgwliIokA +CgkQtvXNTca6JD+WkQCgiGmnoGjMojynp5ppvMXkyUkfnykAoK79E6h8rwkSDZou +iz7nMRisH8uyiEYEEBECAAYFAj+s468ACgkQr8UjSHiDdA/2lgCg21IhIMMABTYd +p/IBiUsP/JQLiEoAnRzMywEtujQz/E9ono7H1DkebDa4iEYEEBECAAYFAj+0Q3cA +CgkQhZavqzBzTmbGwwCdFqD1frViC7WRt8GKoOS7hzNN32kAnirlbwpnT7a6NOsQ +83nk11a2dePhiEYEEBECAAYFAkNbs+oACgkQi9gubzC5S1x/dACdELKoXQKkwJN0 +gZztsM7kjsIgyFMAnRRMbHQ7V39XC90OIpaPjk3a01tgiEYEExECAAYFAkTxMyYA +CgkQ9knE9GCTUwwKcQCgibak/SwhxWH1ijRhgYCo5GtM4vcAnAhtzL57wcw1Kg1X +m7nVGetUqJ7fiEwEEBECAAwFAkGBywEFgwYi2YsACgkQGFnQH2d7oexCjQCcD8sJ +NDc/mS8m8OGDUOx9VMWcnGkAnj1YWOD+Qhxo3mI/Ul9oEAhNkjcfiEwEEBECAAwF +AkGByzQFgwYi2VgACgkQgcL36+ITtpIiIwCdFVNVUB8xe8mFXoPm4d9Z54PTjpMA +niSPA/ZsfJ3oOMLKar4F0QPPrdrGiEwEEBECAAwFAkGBy2IFgwYi2SoACgkQa3Ds +2V3D9HMJqgCbBYzr5GPXOXgP88jKzmdbjweqXeEAnRss4G2G/3qD7uhTL1SPT1SH +jWUXiEwEEBECAAwFAkHQkyQFgwXUEWgACgkQfSXKCsEpp8JiVQCghvWvkPqowsw8 +w7WSseTcw1tflvkAni+vLHl/DqIly0LkZYn5jzK1dpvfiEwEEBECAAwFAkIrW7oF +gwV5SNIACgkQ5hukiRXruavzEwCgkzL5QkLSypcw9LGHcFSx1ya0VL4An35nXkum +g6cCJ1NP8r2I4NcZWIrqiEwEEhECAAwFAkAqWToFgwd6S1IACgkQPKEfNJT6+GEm +XACcD+A53A5OGM7w750W11ukq4iZ9ckAnRMvndAqn3YTOxxlLPj2UPZiSgSqiEwE +EhECAAwFAkA9+roFgwdmqdIACgkQ8tdcY+OcZZyy3wCgtDcwlaq20w0cNuXFLLNe +EUaFFTwAni6RHN80moSVAdDTRkzZacJU3M5QiEwEEhECAAwFAkEOCoQFgwaWmggA +CgkQOcor9D1qil/83QCeITZ9wIo7XAMjC6y4ZWUL4m+edZsAoMOhRIRi42fmrNFu +vNZbnMGej81viEwEEhECAAwFAkKApTQFgwUj/1gACgkQBA3AhXyDn6jjJACcD1A4 +UtXk84J13JQyoH9+dy24714Aniwlsso/9ndICJOkqs2j5dlHFq6oiEwEExECAAwF +Aj5NTYQFgwlXVwgACgkQLbt2v63UyTMFDACglT5G5NVKf5Mj65bFSlPzb92zk2QA +n1uc2h19/IwwrsbIyK/9POJ+JMP7iEwEExECAAwFAkHXgHYFgwXNJBYACgkQZu/b +yM2C/T4/vACfXe67xiSHB80wkmFZ2krb+oz/gBAAnjR2ucpbaonkQQgnC3GnBqmC +vNaJiEwEExECAAwFAkIYgQ4FgwWMI34ACgkQdsEDHKIxbqGg7gCfQi2HcrHn+yLF +uNlH1oSOh48ZM0oAn3hKV0uIRJphonHaUYiUP1ttWgdBiGUEExECAB0FCwcKAwQD +FQMCAxYCAQIXgAUCS3AvygUJEPPzpwASB2VHUEcAAQEJEIxxjTtQcuH1sNsAniYp +YBGqy/HhMnw3WE8kXahOOR5KAJ4xUmWPGYP4l3hKxyNK9OAUbpDVYIh7BDARAgA7 +BQJCdzX1NB0AT29wcy4uLiBzaG91bGQgaGF2ZSBiZWVuIGxvY2FsISBJJ20gKnNv +KiBzdHVwaWQuLi4ACgkQOcor9D1qil/vRwCdFo08f66oKLiuEAqzlf9iDlPozEEA +n2EgvCYLCCHjfGosrkrU3WK5NFVgiI8EMBECAE8FAkVvAL9IHQBTaG91bGQgaGF2 +ZSBiZWVuIGEgbG9jYWwgc2lnbmF0dXJlLCBvciBzb21ldGhpbmcgLSBXVEYgd2Fz +IEkgdGhpbmtpbmc/AAoJEDnKK/Q9aopfoPsAn3BVqKOalJeF0xPSvLR90PsRlnmG +AJ44oisY7Tl3NJbPgZal8W32fbqgbIkCIgQQAQIADAUCQYHLhQWDBiLZBwAKCRCq +4+bOZqFEaKgvEACCErnaHGyUYa0wETjj6DLEXsqeOiXad4i9aBQxnD35GUgcFofC +/nCY4XcnCMMEnmdQ9ofUuU3OBJ6BNJIbEusAabgLooebP/3KEaiCIiyhHYU5jarp +ZAh+Zopgs3Oc11mQ1tIaS69iJxrGTLodkAsAJAeEUwTPq9fHFFzC1eGBysoyFWg4 +bIjz/zClI+qyTbFA5g6tRoiXTo8ko7QhY2AA5UGEg+83Hdb6akC04Z2QRErxKAqr +phHzj8XpjVOsQAdAi/qVKQeNKROlJ+iq6+YesmcWGfzeb87dGNweVFDJIGA0qY27 +pTb2lExYjsRFN4Cb13NfodAbMTOxcAWZ7jAPCxAPlHUG++mHMrhQXEToZnBFE4nb +nC7vOBNgWdjUgXcpkUCkop4b17BFpR+k8ZtYLSS8p2LLz4uAeCcSm2/msJxT7rC/ +FvoH8428oHincqs2ICo9zO/Ud4HmmO0O+SsZdVKIIjinGyOVWb4OOzkAlnnhEZ3o +6hAHcREIsBgPwEYVTj/9ZdC0AO44Nj9cU7awaqgtrnwwfr/o4V2gl8bLSkltZU27 +/29HeuOeFGjlFe0YrDd/aRNsxbyb2O28H4sG1CVZmC5uK1iQBDiSyA7Q0bbdofCW +oQzm5twlpKWnY8Oe0ub9XP5p/sVfck4FceWFHwv+/PC9RzSl33lQ6vM2wIkCIgQT +AQIADAUCQp8KHAWDBQWacAAKCRDYwgoJWiRXzyE+D/9uc7z6fIsalfOYoLN60ajA +bQbI/uRKBFugyZ5RoaItusn9Z2rAtn61WrFhu4uCSJtFN1ny2RERg40f56pTghKr +D+YEt+Nze6+FKQ5AbGIdFsR/2bUk+ZZRSt83e14Lcb6ii/fJfzkoIox9ltkifQxq +Y7Tvk4noKu4oLSc8O1Wsfc/y0B9sYUUCmUfcnq58DEmGie9ovUslmyt5NPnveXxp +5UeaRc5Rqt9tK2B4A+7/cqENrdZJbAMSunt2+2fkYiRunAFPKPBdJBsY1sxeL/A9 +aKe0viKEXQdAWqdNZKNCi8rd/oOP99/9lMbFudAbX6nL2DSb1OG2Z7NWEqgIAzjm +pwYYPCKeVz5Q8R+if9/fe5+STY/55OaI33fJ2H3v+U435VjYqbrerWe36xJItcJe +qUzW71fQtXi1CTEl3w2ch7VF5oj/QyjabLnAlHgSlkSi6p7By5C2MnbCHlCfPnIi +nPhFoRcRGPjJe9nFwGs+QblvS/Chzc2WX3s/2SWm4gEUKRX4zsAJ5ocyfa/vkxCk +SxK/erWlCPf/J1T70+i5waXDN/E3enSet/WL7h94pQKpjz8OdGL4JSBHuAVGA+a+ +dknqnPF0KMKLhjrgV+L7O84FhbmAP7PXm3xmiMPriXf+el5fZZequQoIagf8rdRH +HhRJxQgI0HNknkaOqs8dtrkCDQQ+PqMdEAgA7+GJfxbMdY4wslPnjH9rF4N2qfWs +EN/lxaZoJYc3a6M02WCnHl6ahT2/tBK2w1QI4YFteR47gCvtgb6O1JHffOo2HfLm +RDRiRjd1DTCHqeyX7CHhcghj/dNRlW2Z0l5QFEcmV9U0Vhp3aFfWC4Ujfs3LU+hk +AWzE7zaD5cH9J7yv/6xuZVw411x0h4UqsTcWMu0iM1BzELqX1DY7LwoPEb/O9Rkb +f4fmLe11EzIaCa4PqARXQZc4dhSinMt6K3X4BrRsKTfozBu74F47D8Ilbf5vSYHb +uE5p/1oIDznkg/p8kW+3FxuWrycciqFTcNz215yyX39LXFnlLzKUb/F5GwADBQf+ +Lwqqa8CGrRfsOAJxim63CHfty5mUc5rUSnTslGYEIOCR1BeQauyPZbPDsDD9MZ1Z +aSafanFvwFG6Llx9xkU7tzq+vKLoWkm4u5xf3vn55VjnSd1aQ9eQnUcXiL4cnBGo +TbOWI39EcyzgslzBdC++MPjcQTcA7p6JUVsP6oAB3FQWg54tuUo0Ec8bsM8b3Ev4 +2LmuQT5NdKHGwHsXTPtl0klk4bQk4OajHsiy1BMahpT27jWjJlMiJc+IWJ0mghkK +Ht926s/ymfdf5HkdQ1cyvsz5tryVI3Fx78XeSYfQvuuwqp2H139pXGEkg0n6KdUO +etdZWhe70YGNPw1yjWJT1IhUBBgRAgAMBQJOdz3tBQkT+wG4ABIHZUdQRwABAQkQ +jHGNO1By4fUUmwCbBYr2+bBEn/L2BOcnw9Z/QFWuhRMAoKVgCFm5fadQ3Afi+UQl +AcOphrnJ +=443I -----END PGP PUBLIC KEY BLOCK----- - To import the build key into your personal public GPG keyring, use - gpg --import. For example, if you have saved the key in a file - named mysql_pubkey.asc, the import command looks like this: + To import the build key into your personal public GPG + keyring, use gpg --import. For example, if you have saved the + key in a file named mysql_pubkey.asc, the import command + looks like this: shell> gpg --import mysql_pubkey.asc gpg: key 5072E1F5: public key "MySQL Release Engineering " imported @@ -601,15 +465,15 @@ gpg: imported: 1 gpg: no ultimately trusted keys found - You can also download the key from the public keyserver using the - public key id, 5072E1F5: + You can also download the key from the public keyserver using + the public key id, 5072E1F5: shell> gpg --recv-keys 5072E1F5 gpg: requesting key 5072E1F5 from hkp server keys.gnupg.net -gpg: key 5072E1F5: "MySQL Release Engineering " +gpg: key 5072E1F5: "MySQL Release Engineering " 1 new user ID -gpg: key 5072E1F5: "MySQL Release Engineering " +gpg: key 5072E1F5: "MySQL Release Engineering " 53 new signatures gpg: no ultimately trusted keys found gpg: Total number processed: 1 @@ -617,214 +481,220 @@ gpg: new signatures: 53 If you want to import the key into your RPM configuration to - validate RPM install packages, you should be able to import the - key directly: + validate RPM install packages, you should be able to import + the key directly: shell> rpm --import mysql_pubkey.asc - If you experience problems or require RPM specific information, - see Section 2.1.4.4, "Signature Checking Using RPM." + If you experience problems or require RPM specific + information, see Section 2.1.3.4, "Signature Checking Using + RPM." After you have downloaded and imported the public build key, download your desired MySQL package and the corresponding - signature, which also is available from the download page. The - signature file has the same name as the distribution file with an - .asc extension, as shown by the examples in the following table. + signature, which also is available from the download page. + The signature file has the same name as the distribution file + with an .asc extension, as shown by the examples in the + following table. - Table 2.1. MySQL Package and Signature Files for Source files + Table 2.1 MySQL Package and Signature Files for Source files File Type File Name - Distribution file mysql-standard-5.5.36-linux-i686.tar.gz - Signature file mysql-standard-5.5.36-linux-i686.tar.gz.asc + Distribution file mysql-standard-5.5.44-linux-i686.tar.gz + Signature file mysql-standard-5.5.44-linux-i686.tar.gz.asc - Make sure that both files are stored in the same directory and - then run the following command to verify the signature for the - distribution file: + Make sure that both files are stored in the same directory + and then run the following command to verify the signature + for the distribution file: shell> gpg --verify package_name.asc If the downloaded package is valid, you will see a "Good signature" similar to: -shell> gpg --verify mysql-standard-5.5.36-linux-i686.tar.gz.asc -gpg: Signature made Tue 01 Feb 2011 02:38:30 AM CST using DSA key ID -5072E1F5 -gpg: Good signature from "MySQL Release Engineering " - - The Good signature message indicates that the file signature is - valid, when compared to the signature listed on our site. But you - might also see warnings, like so: -shell> gpg --verify mysql-standard-5.5.36-linux-i686.tar.gz.asc -gpg: Signature made Wed 23 Jan 2013 02:25:45 AM PST using DSA key ID -5072E1F5 +shell> gpg --verify mysql-standard-5.5.44-linux-i686.tar.gz.asc +gpg: Signature made Tue 01 Feb 2011 02:38:30 AM CST using DSA key ID 5 +072E1F5 +gpg: Good signature from "MySQL Release Engineering " + + The Good signature message indicates that the file signature + is valid, when compared to the signature listed on our site. + But you might also see warnings, like so: +shell> gpg --verify mysql-standard-5.5.44-linux-i686.tar.gz.asc +gpg: Signature made Wed 23 Jan 2013 02:25:45 AM PST using DSA key ID 5 +072E1F5 gpg: checking the trustdb gpg: no ultimately trusted keys found -gpg: Good signature from "MySQL Release Engineering " +gpg: Good signature from "MySQL Release Engineering " gpg: WARNING: This key is not certified with a trusted signature! -gpg: There is no indication that the signature belongs to th -e owner. -Primary key fingerprint: A4A9 4068 76FC BD3C 4567 70C8 8C71 8D3B 507 -2 E1F5 - - That is normal, as they depend on your setup and configuration. - Here are explanations for these warnings: - - * gpg: no ultimately trusted keys found: This means that the - specific key is not "ultimately trusted" by you or your web of - trust, which is okay for the purposes of verifying file - signatures. - - * WARNING: This key is not certified with a trusted signature! - There is no indication that the signature belongs to the - owner.: This refers to your level of trust in your belief that - you possess our real public key. This is a personal decision. - Ideally, a MySQL developer would hand you the key in person, - but more commonly, you downloaded it. Was the download - tampered with? Probably not, but this decision is up to you. - Setting up a web of trust is one method for trusting them. - - See the GPG documentation for more information on how to work with - public keys. - -2.1.4.3. Signature Checking Using Gpg4win for Windows - - The Section 2.1.4.2, "Signature Checking Using GnuPG" section - describes how to verify MySQL downloads using GPG. That guide also - applies to Microsoft Windows, but another option is to use a GUI - tool like Gpg4win (http://www.gpg4win.org/). You may use a - different tool but our examples are based on Gpg4win, and utilize - its bundled Kleopatra GUI. +gpg: There is no indication that the signature belongs to the + owner. +Primary key fingerprint: A4A9 4068 76FC BD3C 4567 70C8 8C71 8D3B 5072 + E1F5 + + That is normal, as they depend on your setup and + configuration. Here are explanations for these warnings: + + * gpg: no ultimately trusted keys found: This means that + the specific key is not "ultimately trusted" by you or + your web of trust, which is okay for the purposes of + verifying file signatures. + + * WARNING: This key is not certified with a trusted + signature! There is no indication that the signature + belongs to the owner.: This refers to your level of trust + in your belief that you possess our real public key. This + is a personal decision. Ideally, a MySQL developer would + hand you the key in person, but more commonly, you + downloaded it. Was the download tampered with? Probably + not, but this decision is up to you. Setting up a web of + trust is one method for trusting them. + + See the GPG documentation for more information on how to work + with public keys. + +2.1.3.3 Signature Checking Using Gpg4win for Windows + + The Section 2.1.3.2, "Signature Checking Using GnuPG" section + describes how to verify MySQL downloads using GPG. That guide + also applies to Microsoft Windows, but another option is to + use a GUI tool like Gpg4win (http://www.gpg4win.org/). You + may use a different tool but our examples are based on + Gpg4win, and utilize its bundled Kleopatra GUI. - Download and install Gpg4win, and then load Kleopatra. The dialog - should look similar to: + Download and install Gpg4win, and then load Kleopatra. The + dialog should look similar to: - Figure 2.1. Initial screen after loading Kleopatra + Figure 2.1 Initial screen after loading Kleopatra Initial screen after loading Kleopatra - Next, add the MySQL Release Engineering certificate. Do this by - clicking File, Lookup Certificates on Server. Type "Mysql Release - Engineering" into the search box and press Search. + Next, add the MySQL Release Engineering certificate. Do this + by clicking File, Lookup Certificates on Server. Type "Mysql + Release Engineering" into the search box and press Search. - Figure 2.2. Finding the MySQL Release Engineering certificate + Figure 2.2 Finding the MySQL Release Engineering certificate Finding the MySQL Release Engineering certificate Select the "MySQL Release Engineering" certificate. The - Fingerprint and Key-ID must be "5072E1F5", or choose Details... to - confirm the certificate is valid. Now, import it by clicking - Import. An import dialog will be displayed, choose Okay, and this - certificate will now be listed under the Imported Certificates - tab. - - Next, configure the trust level for our certificate. Select our - certificate, then from the main menu select Certificates, Change - Owner Trust.... We suggest choosing I believe checks are very - accurate for our certificate, as otherwise you might not be able - to verify our signature. Select I believe checks are very accurate - and then press OK. + Fingerprint and Key-ID must be "5072E1F5", or choose + Details... to confirm the certificate is valid. Now, import + it by clicking Import. An import dialog will be displayed, + choose Okay, and this certificate will now be listed under + the Imported Certificates tab. + + Next, configure the trust level for our certificate. Select + our certificate, then from the main menu select Certificates, + Change Owner Trust.... We suggest choosing I believe checks + are very accurate for our certificate, as otherwise you might + not be able to verify our signature. Select I believe checks + are very accurate and then press OK. - Figure 2.3. Changing the Trust level + Figure 2.3 Changing the Trust level Changing the Trust level Next, verify the downloaded MySQL package file. This requires - files for both the packaged file, and the signature. The signature - file must have the same name as the packaged file but with an - appended .asc extension, as shown by the example in the following - table. The signature is linked to on the downloads page for each - MySQL product. You must create the .asc file with this signature. + files for both the packaged file, and the signature. The + signature file must have the same name as the packaged file + but with an appended .asc extension, as shown by the example + in the following table. The signature is linked to on the + downloads page for each MySQL product. You must create the + .asc file with this signature. - Table 2.2. MySQL Package and Signature Files for MySQL Installer - for Microsoft Windows + Table 2.2 MySQL Package and Signature Files for MySQL + Installer for Microsoft Windows File Type File Name - Distribution file mysql-installer-community-5.5.36.msi - Signature file mysql-installer-community-5.5.36.msi.asc + Distribution file mysql-installer-community-5.5.44.msi + Signature file mysql-installer-community-5.5.44.msi.asc - Make sure that both files are stored in the same directory and - then run the following command to verify the signature for the - distribution file. Either drag and drop the signature (.asc) file - into Kleopatra, or load the dialog from File, Decrypt/Verify - Files..., and then choose either the .msi or .asc file. + Make sure that both files are stored in the same directory + and then run the following command to verify the signature + for the distribution file. Either drag and drop the signature + (.asc) file into Kleopatra, or load the dialog from File, + Decrypt/Verify Files..., and then choose either the .msi or + .asc file. - Figure 2.4. The Decrypt/Verify Files dialog + Figure 2.4 The Decrypt/Verify Files dialog The Decrypt/Verify Files dialog Click Decrypt/Verify to check the file. The two most common results will look like the following, and although the yellow - warning looks problematic, the following means that the file check - passed with success. You may now run this installer. + warning looks problematic, the following means that the file + check passed with success. You may now run this installer. - Figure 2.5. The Decrypt/Verify Results: Good + Figure 2.5 The Decrypt/Verify Results: Good The Decrypt/Verify Results: Good Seeing a red "The signature is bad" error means the file is invalid. Do not execute the MSI file if you see this error. - Figure 2.6. The Decrypt/Verify Results: Bad + Figure 2.6 The Decrypt/Verify Results: Bad The Decrypt/Verify Results: Bad - The Section 2.1.4.2, "Signature Checking Using GnuPG" section - explains why you probably don't see a green Good signature result. - -2.1.4.4. Signature Checking Using RPM - - For RPM packages, there is no separate signature. RPM packages - have a built-in GPG signature and MD5 checksum. You can verify a - package by running the following command: + The Section 2.1.3.2, "Signature Checking Using GnuPG" section + explains why you probably don't see a green Good signature + result. + +2.1.3.4 Signature Checking Using RPM + + For RPM packages, there is no separate signature. RPM + packages have a built-in GPG signature and MD5 checksum. You + can verify a package by running the following command: shell> rpm --checksig package_name.rpm Example: -shell> rpm --checksig MySQL-server-5.5.36-0.glibc23.i386.rpm -MySQL-server-5.5.36-0.glibc23.i386.rpm: md5 gpg OK +shell> rpm --checksig MySQL-server-5.5.44-0.glibc23.i386.rpm +MySQL-server-5.5.44-0.glibc23.i386.rpm: md5 gpg OK Note If you are using RPM 4.1 and it complains about (GPG) NOT OK - (MISSING KEYS: GPG#5072e1f5), even though you have imported the - MySQL public build key into your own GPG keyring, you need to - import the key into the RPM keyring first. RPM 4.1 no longer uses - your personal GPG keyring (or GPG itself). Rather, RPM maintains a - separate keyring because it is a system-wide application and a - user's GPG public keyring is a user-specific file. To import the - MySQL public key into the RPM keyring, first obtain the key, then - use rpm --import to import the key. For example: + (MISSING KEYS: GPG#5072e1f5), even though you have imported + the MySQL public build key into your own GPG keyring, you + need to import the key into the RPM keyring first. RPM 4.1 no + longer uses your personal GPG keyring (or GPG itself). + Rather, RPM maintains a separate keyring because it is a + system-wide application and a user's GPG public keyring is a + user-specific file. To import the MySQL public key into the + RPM keyring, first obtain the key, then use rpm --import to + import the key. For example: shell> gpg --export -a 5072e1f5 > 5072e1f5.asc shell> rpm --import 5072e1f5.asc - Alternatively, rpm also supports loading the key directly from a - URL, and you can use this manual page: -shell> rpm --import http://dev.mysql.com/doc/refman/5.5/en/checking-g -pg-signature.html - - If you need to obtain the MySQL public key, see Section 2.1.4.2, - "Signature Checking Using GnuPG." - -2.1.5. Installation Layouts - - The installation layout differs for different installation types - (for example, native packages, binary tarballs, and source - tarballs), which can lead to confusion when managing different - systems or using different installation sources. The individual - layouts are given in the corresponding installation type or - platform chapter, as described following. Note that the layout of - installations from vendors other than Oracle may differ from these - layouts. + Alternatively, rpm also supports loading the key directly + from a URL, and you can use this manual page: +shell> rpm --import doc/refman/5.5/en/checking-gpg-signature.html + + If you need to obtain the MySQL public key, see Section + 2.1.3.2, "Signature Checking Using GnuPG." + +2.1.4 Installation Layouts + + The installation layout differs for different installation + types (for example, native packages, binary tarballs, and + source tarballs), which can lead to confusion when managing + different systems or using different installation sources. + The individual layouts are given in the corresponding + installation type or platform chapter, as described + following. Note that the layout of installations from vendors + other than Oracle may differ from these layouts. * Section 2.3.1, "MySQL Installation Layout on Microsoft Windows" - * Section 2.10.1, "MySQL Layout for Source Installation" + * Section 2.9.1, "MySQL Layout for Source Installation" - * Section 2.2, "MySQL Installation Layout for Generic Unix/Linux - Binary Package" + * Section 2.2, "MySQL Installation Layout for Generic + Unix/Linux Binary Package" * Section 2.5.1, "MySQL Installation Layout for Linux RPM Packages" - * Section 2.4.2, "MySQL Installation Layout on Mac OS X" + * Section 2.4.2, "MySQL Installation Layout on OS X" -2.1.6. Compiler-Specific Build Characteristics +2.1.5 Compiler-Specific Build Characteristics In some cases, the compiler used to build MySQL affects the - features available for use. The notes in this section apply for - binary distributions provided by Oracle Corporation or that you - compile yourself from source. + features available for use. The notes in this section apply + for binary distributions provided by Oracle Corporation or + that you compile yourself from source. icc (Intel C++ Compiler) Builds @@ -832,62 +702,79 @@ * SSL support is not included. -2.2. Installing MySQL on Unix/Linux Using Generic Binaries +2.2 Installing MySQL on Unix/Linux Using Generic Binaries Oracle provides a set of binary distributions of MySQL. These - include binary distributions in the form of compressed tar files - (files with a .tar.gz extension) for a number of platforms, as - well as binaries in platform-specific package formats for selected - platforms. - - This section covers the installation of MySQL from a compressed - tar file binary distribution. For other platform-specific package - formats, see the other platform-specific sections. For example, - for Windows distributions, see Section 2.3, "Installing MySQL on + include binary distributions in the form of compressed tar + files (files with a .tar.gz extension) for a number of + platforms, as well as binaries in platform-specific package + formats for selected platforms. + + This section covers the installation of MySQL from a + compressed tar file binary distribution. For other + platform-specific package formats, see the other + platform-specific sections. For example, for Windows + distributions, see Section 2.3, "Installing MySQL on Microsoft Windows." - To obtain MySQL, see Section 2.1.3, "How to Get MySQL." + To obtain MySQL, see Section 2.1.2, "How to Get MySQL." - MySQL compressed tar file binary distributions have names of the - form mysql-VERSION-OS.tar.gz, where VERSION is a number (for - example, 5.5.36), and OS indicates the type of operating system - for which the distribution is intended (for example, pc-linux-i686 - or winx64). - - To install MySQL from a compressed tar file binary distribution, - your system must have GNU gunzip to uncompress the distribution - and a reasonable tar to unpack it. If your tar program supports - the z option, it can both uncompress and unpack the file. + MySQL compressed tar file binary distributions have names of + the form mysql-VERSION-OS.tar.gz, where VERSION is a number + (for example, 5.5.44), and OS indicates the type of operating + system for which the distribution is intended (for example, + pc-linux-i686 or winx64). + + To install MySQL from a compressed tar file binary + distribution, your system must have GNU gunzip to uncompress + the distribution and a reasonable tar to unpack it. If your + tar program supports the z option, it can both uncompress and + unpack the file. GNU tar is known to work. The standard tar provided with some - operating systems is not able to unpack the long file names in the - MySQL distribution. You should download and install GNU tar, or if - available, use a preinstalled version of GNU tar. Usually this is - available as gnutar, gtar, or as tar within a GNU or Free Software - directory, such as /usr/sfw/bin or /usr/local/bin. GNU tar is - available from http://www.gnu.org/software/tar/. + operating systems is not able to unpack the long file names + in the MySQL distribution. You should download and install + GNU tar, or if available, use a preinstalled version of GNU + tar. Usually this is available as gnutar, gtar, or as tar + within a GNU or Free Software directory, such as /usr/sfw/bin + or /usr/local/bin. GNU tar is available from + http://www.gnu.org/software/tar/. Warning - If you have previously installed MySQL using your operating system - native package management system, such as yum or apt-get, you may - experience problems installing using a native binary. Make sure - your previous MySQL previous installation has been removed - entirely (using your package management system), and that any - additional files, such as old versions of your data files, have - also been removed. You should also check the existence of - configuration files such as /etc/my.cnf or the /etc/mysql - directory have been deleted. - - If you run into problems and need to file a bug report, please use - the instructions in Section 1.7, "How to Report Bugs or Problems." - - On Unix, to install a compressed tar file binary distribution, - unpack it at the installation location you choose (typically - /usr/local/mysql). This creates the directories shown in the - following table. + If you have previously installed MySQL using your operating + system native package management system, such as yum or + apt-get, you may experience problems installing using a + native binary. Make sure your previous MySQL installation has + been removed entirely (using your package management system), + and that any additional files, such as old versions of your + data files, have also been removed. You should also check the + existence of configuration files such as /etc/my.cnf or the + /etc/mysql directory have been deleted. + Warning + + MySQL has a dependency on the libaio library. The + mysql_install_db and subsequent mysqld_safe steps will fail + if this library is not installed locally. If necessary, + install it using the appropriate package manager. For + example, on Yum-based systems: +shell> yum search libaio # search for info +shell> yum install libaio # install library + + Or, on APT-based systems: +shell> apt-cache search libaio # search for info +shell> apt-get install libaio1 # install library + + If you run into problems and need to file a bug report, + please use the instructions in Section 1.7, "How to Report + Bugs or Problems." - Table 2.3. MySQL Installation Layout for Generic Unix/Linux Binary - Package + On Unix, to install a compressed tar file binary + distribution, unpack it at the installation location you + choose (typically /usr/local/mysql). This creates the + directories shown in the following table. + + Table 2.3 MySQL Installation Layout for Generic Unix/Linux + Binary Package Directory Contents of Directory bin Client programs and the mysqld server data Log files, databases @@ -900,25 +787,25 @@ sample configuration files, SQL for database installation sql-bench Benchmarks - Debug versions of the mysqld binary are available as mysqld-debug. - To compile your own debug version of MySQL from a source - distribution, use the appropriate configuration options to enable - debugging support. For more information on compiling from source, - see Section 2.10, "Installing MySQL from Source." + Debug versions of the mysqld binary are available as + mysqld-debug. To compile your own debug version of MySQL from + a source distribution, use the appropriate configuration + options to enable debugging support. For more information on + compiling from source, see Section 2.9, "Installing MySQL + from Source." - To install and use a MySQL binary distribution, the basic command - sequence looks like this: + To install and use a MySQL binary distribution, the basic + command sequence looks like this: shell> groupadd mysql shell> useradd -r -g mysql mysql shell> cd /usr/local shell> tar zxvf /path/to/mysql-VERSION-OS.tar.gz shell> ln -s full-path-to-mysql-VERSION-OS mysql shell> cd mysql -shell> chown -R mysql . -shell> chgrp -R mysql . -shell> scripts/mysql_install_db --user=mysql shell> chown -R root . shell> chown -R mysql data +shell> chgrp -R mysql . +shell> scripts/mysql_install_db --user=mysql # Next command is optional shell> cp support-files/my-medium.cnf /etc/my.cnf shell> bin/mysqld_safe --user=mysql & @@ -929,694 +816,1092 @@ installing a binary distribution follows. Note - This procedure assumes that you have root (administrator) access - to your system. Alternatively, you can prefix each command using - the sudo (Linux) or pfexec (OpenSolaris) command. - - The procedure does not set up any passwords for MySQL accounts. - After following the procedure, proceed to Section 2.11.2, - "Securing the Initial MySQL Accounts." + This procedure assumes that you have root (administrator) + access to your system. Alternatively, you can prefix each + command using the sudo (Linux) or pfexec (OpenSolaris) + command. + + The procedure does not set up any passwords for MySQL + accounts. After following the procedure, proceed to Section + 2.10.2, "Securing the Initial MySQL Accounts." Create a mysql User and Group - If your system does not already have a user and group for mysqld - to run as, you may need to create one. The following commands add - the mysql group and the mysql user. You might want to call the - user and group something else instead of mysql. If so, substitute - the appropriate name in the following instructions. The syntax for - useradd and groupadd may differ slightly on different versions of - Unix, or they may have different names such as adduser and - addgroup. + If your system does not already have a user and group for + mysqld to run as, you may need to create one. The following + commands add the mysql group and the mysql user. You might + want to call the user and group something else instead of + mysql. If so, substitute the appropriate name in the + following instructions. The syntax for useradd and groupadd + may differ slightly on different versions of Unix, or they + may have different names such as adduser and addgroup. shell> groupadd mysql shell> useradd -r -g mysql mysql Note Because the user is required only for ownership purposes, not - login purposes, the useradd command uses the -r option to create a - user that does not have login permissions to your server host. - Omit this option to permit logins for the user (or if your useradd - does not support the option). + login purposes, the useradd command uses the -r option to + create a user that does not have login permissions to your + server host. Omit this option to permit logins for the user + (or if your useradd does not support the option). Obtain and Unpack the Distribution - Pick the directory under which you want to unpack the distribution - and change location into it. The example here unpacks the - distribution under /usr/local. The instructions, therefore, assume - that you have permission to create files and directories in - /usr/local. If that directory is protected, you must perform the - installation as root. + Pick the directory under which you want to unpack the + distribution and change location into it. The example here + unpacks the distribution under /usr/local. The instructions, + therefore, assume that you have permission to create files + and directories in /usr/local. If that directory is + protected, you must perform the installation as root. shell> cd /usr/local Obtain a distribution file using the instructions in Section - 2.1.3, "How to Get MySQL." For a given release, binary + 2.1.2, "How to Get MySQL." For a given release, binary distributions for all platforms are built from the same MySQL source distribution. - Unpack the distribution, which creates the installation directory. - Then create a symbolic link to that directory. tar can uncompress - and unpack the distribution if it has z option support: + Unpack the distribution, which creates the installation + directory. Then create a symbolic link to that directory. tar + can uncompress and unpack the distribution if it has z option + support: shell> tar zxvf /path/to/mysql-VERSION-OS.tar.gz shell> ln -s full-path-to-mysql-VERSION-OS mysql - The tar command creates a directory named mysql-VERSION-OS. The ln - command makes a symbolic link to that directory. This enables you - to refer more easily to the installation directory as - /usr/local/mysql. - - If your tar does not have z option support, use gunzip to unpack - the distribution and tar to unpack it. Replace the preceding tar - command with the following alternative command to uncompress and - extract the distribution: + The tar command creates a directory named mysql-VERSION-OS. + The ln command makes a symbolic link to that directory. This + enables you to refer more easily to the installation + directory as /usr/local/mysql. + + If your tar does not have z option support, use gunzip to + unpack the distribution and tar to unpack it. Replace the + preceding tar command with the following alternative command + to uncompress and extract the distribution: shell> gunzip < /path/to/mysql-VERSION-OS.tar.gz | tar xvf - Perform Postinstallation Setup - The remainder of the installation process involves setting up the - configuration file, creating the core databases, and starting the - MySQL server. For next steps, see Section 2.11, "Postinstallation - Setup and Testing." - Note - - The accounts that are listed in the MySQL grant tables initially - have no passwords. After starting the server, you should set up - passwords for them using the instructions in Section 2.11.2, - "Securing the Initial MySQL Accounts." - -2.3. Installing MySQL on Microsoft Windows - - MySQL for Microsoft Windows is available in a number of different - forms. A Microsoft Windows operating system such as Windows XP, - Windows Vista, Windows 7, Windows 8, Windows Server 2003, Windows - Server 2008, or Windows Server 2012. Both 32-bit and 64-bit - versions are supported. For supported platform information, see - http://www.mysql.com/support/supportedplatforms/database.html. - - In addition to running MySQL as a standard application, you can - also run the MySQL server as a Windows service. By using a service - you can monitor and control the operation of the server through - the standard Windows service management tools. For more - information, see Section 2.3.7.7, "Starting MySQL as a Windows - Service." + The remainder of the installation process involves setting up + the configuration file, creating the core databases, and + starting the MySQL server. For next steps, see Section 2.10, + "Postinstallation Setup and Testing." + Note + + The accounts that are listed in the MySQL grant tables + initially have no passwords. After starting the server, you + should set up passwords for them using the instructions in + Section 2.10.2, "Securing the Initial MySQL Accounts." + +2.3 Installing MySQL on Microsoft Windows - Generally, you should install MySQL on Windows using an account - that has administrator rights. Otherwise, you may encounter - problems with certain operations such as editing the PATH - environment variable or accessing the Service Control Manager. - Once installed, MySQL does not need to be executed using a user - with Administrator privileges. + There are several different methods to install MySQL on + Microsoft Windows. - For a list of limitations within the Windows version of MySQL, see - Section E.10.6, "Windows Platform Limitations." +Simple Installation Method + + The simplest and recommended method is to download MySQL + Installer (for Windows) and let it install and configure all + of the MySQL products on your system. Here is how: + + * Download MySQL Installer from + http://dev.mysql.com/downloads/installer/ and execute it. + Note + Unlike the standard MySQL Installer, the smaller + "web-community" version does not bundle any MySQL + applications but it will download the MySQL products you + choose to install. + + * Choose the appropriate Setup Type for your system. + Typically you will choose Developer Default to install + MySQL server and other MySQL tools related to MySQL + development, helpful tools like MySQL Workbench. Or, + choose the Custom setup type to manually select your + desired MySQL products. + Note + Multiple versions of MySQL server can exist on a single + system. You can choose one or multiple versions. + + * Complete the installation process by following the MySQL + Installation wizard's instructions. This will install + several MySQL products and start the MySQL server. + + * MySQL is now installed. You probably configured MySQL as + a service that will automatically start MySQL server + every time you restart your system. + + Note + + You probably also installed other helpful MySQL products like + MySQL Workbench and MySQL Notifier on your system. Consider + loading Chapter 26, "MySQL Workbench" to check your new MySQL + server connection, and Section 2.3.4, "MySQL Notifier" to + view the connection's status. By default, these two programs + automatically start after installing MySQL. + + This process also installs the MySQL Installer application on + your system, and later you can use MySQL Installer to upgrade + or reconfigure your MySQL products. + +Additional Installation Information + + MySQL is available for Microsoft Windows, for both 32-bit and + 64-bit versions. For supported Windows platform information, + see + http://www.mysql.com/support/supportedplatforms/database.html + . + + It is possible to run MySQL as a standard application or as a + Windows service. By using a service, you can monitor and + control the operation of the server through the standard + Windows service management tools. For more information, see + Section 2.3.7.7, "Starting MySQL as a Windows Service." + + Generally, you should install MySQL on Windows using an + account that has administrator rights. Otherwise, you may + encounter problems with certain operations such as editing + the PATH environment variable or accessing the Service + Control Manager. Once installed, MySQL does not need to be + executed using a user with Administrator privileges. + + For a list of limitations on the use of MySQL on the Windows + platform, see Section D.10.6, "Windows Platform Limitations." In addition to the MySQL Server package, you may need or want additional components to use MySQL with your application or - development environment. These include, but are not limited to: + development environment. These include, but are not limited + to: + + * To connect to the MySQL server using ODBC, you must have + a Connector/ODBC driver. For more information, including + installation and configuration instructions, see MySQL + Connector/ODBC Developer Guide + (http://dev.mysql.com/doc/connector-odbc/en/index.html). + Note + MySQL Installer will install and configure Connector/ODBC + for you. - * If you plan to connect to the MySQL server using ODBC, you - need a Connector/ODBC driver. For more information, including - installation and configuration instructions, see Section 22.1, - "MySQL Connector/ODBC." - - * If you plan to use MySQL server with .NET applications, you - need the Connector/Net driver. For more information, including - installation and configuration instructions, see Section 22.2, - "MySQL Connector/Net." + * To use MySQL server with .NET applications, you must have + the Connector/Net driver. For more information, including + installation and configuration instructions, see MySQL + Connector/Net Developer Guide + (http://dev.mysql.com/doc/connector-net/en/index.html). + Note + MySQL Installer will install and configure Connector/NET + for you. MySQL distributions for Windows can be downloaded from - http://dev.mysql.com/downloads/. See Section 2.1.3, "How to Get - MySQL." + http://dev.mysql.com/downloads/. See Section 2.1.2, "How to + Get MySQL." - MySQL for Windows is available in several distribution formats, - detailed below. Generally speaking, you should use MySQL - Installer. It contains more features and MySQL products than the - older MSI, is simpler to use than the ZIP file, and you need no - additional tools to get MySQL up and running. MySQL Installer will - automatically install MySQL Server, install additional MySQL - products, create an options file, starts the server, and allow you - to create default user accounts. For more information on choosing - a package, see Section 2.3.2, "Choosing An Installation Package." - - MySQL for Windows is available in several distribution formats, - detailed below. Generally speaking, you should use a binary - distribution that includes an installer. It is simpler to use than - the others, and you need no additional tools to get MySQL up and - running. The installer for the Windows version of MySQL, combined - with a GUI Config Wizard, automatically installs MySQL, creates an - option file, starts the server, and secures the default user - accounts. - - * Binary installer distribution. There are two different - installable distributions that come packaged as a Microsoft - Windows Installer (MSI) package that you can install manually - or automatically on your systems. The older MSI package that - contains all the files you need to install and configure MySQL - server, but no additional components, and the preferred MySQL - Installer package that includes MySQL Server and additional - MySQL products including MySQL Workbench, MySQL Notifier, and - MySQL for Excel. And MySQL Installer can also be used to - upgrade these product in the future. For more information on - choosing a package, see Section 2.3.2, "Choosing An - Installation Package" - For instructions on installing MySQL using MySQL Installer, - see Section 2.3.3, "Installing MySQL on Microsoft Windows - Using MySQL Installer." - - * Standard binary distribution format packaged as a Zip file - containing all of the necessary files that you unpack into - your chosen location. This package contains all of the files - in the full Windows MSI Installer package, but does not - include an installation program. - For instructions on installing MySQL using the Zip file, see - Section 2.3.7, "Installing MySQL on Microsoft Windows Using a - noinstall Zip Archive." - - * The source distribution contains all the code and support - files for building the executables using the Visual Studio - compiler system. - For instructions on building MySQL from source on Windows, see - Section 2.10, "Installing MySQL from Source." + MySQL for Windows is available in several distribution + formats, detailed below. Generally speaking, you should use + MySQL Installer. It contains more features and MySQL products + than the older MSI, is simpler to use than the Zip file, and + you need no additional tools to get MySQL up and running. + MySQL Installer automatically installs MySQL Server and + additional MySQL products, creates an options file, starts + the server, and enables you to create default user accounts. + For more information on choosing a package, see Section + 2.3.2, "Choosing An Installation Package." + + * Binary installer distributions. There are two different + installable distributions that come packaged as a + Microsoft Windows Installer (MSI) package that you can + install manually or automatically on your systems. The + preferred MySQL Installer package includes MySQL Server + and additional MySQL products including MySQL Workbench, + MySQL Notifier, and MySQL for Excel. MySQL Installer can + also be used to upgrade these product in the future. The + older MSI package contains all the files you need to + install and configure MySQL server, but no additional + components. + For instructions on installing MySQL using MySQL + Installer, see Section 2.3.3, "Installing MySQL on + Microsoft Windows Using MySQL Installer." + + * The standard binary distribution (packaged as a Zip file) + contains all of the necessary files that you unpack into + your chosen location. This package contains all of the + files in the full Windows MSI Installer package, but does + not include an installation program. + For instructions on installing MySQL using the Zip file, + see Section 2.3.7, "Installing MySQL on Microsoft Windows + Using a noinstall Zip Archive." + + * The source distribution format contains all the code and + support files for building the executables using the + Visual Studio compiler system. + For instructions on building MySQL from source on + Windows, see Section 2.9, "Installing MySQL from Source." MySQL on Windows considerations: * Large Table Support - If you need tables with a size larger than 4GB, install MySQL - on an NTFS or newer file system. Do not forget to use MAX_ROWS - and AVG_ROW_LENGTH when you create tables. See Section - 13.1.17, "CREATE TABLE Syntax." + If you need tables with a size larger than 4GB, install + MySQL on an NTFS or newer file system. Do not forget to + use MAX_ROWS and AVG_ROW_LENGTH when you create tables. + See Section 13.1.17, "CREATE TABLE Syntax." * MySQL and Virus Checking Software - Using virus scanning software such as Norton/Symantec - Anti-Virus on directories containing MySQL data and temporary - tables can cause issues, both in terms of the performance of - MySQL and the virus-scanning software mis-identifying the - contents of the files as containing spam. This is because of - the fingerprinting mechanism used by the virus scanning - software, and the way in which MySQL rapidly updates different - files, which may be identified as a potential security risk. + Virus-scanning software such as Norton/Symantec + Anti-Virus on directories containing MySQL data and + temporary tables can cause issues, both in terms of the + performance of MySQL and the virus-scanning software + misidentifying the contents of the files as containing + spam. This is due to the fingerprinting mechanism used by + the virus-scanning software, and the way in which MySQL + rapidly updates different files, which may be identified + as a potential security risk. After installing MySQL Server, it is recommended that you - disable virus scanning on the main directory (datadir) being - used to store your MySQL table data. There is usually a system - built into the virus scanning software to permit certain - directories to be specifically ignored during virus scanning. - In addition, by default, MySQL creates temporary files in the - standard Windows temporary directory. To prevent the temporary - files also being scanned, you should configure a separate - temporary directory for MySQL temporary files and add this to - the virus scanning exclusion list. To do this, add a - configuration option for the tmpdir parameter to your my.ini - configuration file. For more information, see Section 2.3.7.2, - "Creating an Option File." - -2.3.1. MySQL Installation Layout on Microsoft Windows - - For MySQL 5.5 on Windows, the default installation directory is - C:\Program Files\MySQL\MySQL Server 5.5. Some Windows users prefer - to install in C:\mysql, the directory that formerly was used as - the default. However, the layout of the subdirectories remains the - same. + disable virus scanning on the main directory (datadir) + used to store your MySQL table data. There is usually a + system built into the virus-scanning software to enable + specific directories to be ignored. + In addition, by default, MySQL creates temporary files in + the standard Windows temporary directory. To prevent the + temporary files also being scanned, configure a separate + temporary directory for MySQL temporary files and add + this directory to the virus scanning exclusion list. To + do this, add a configuration option for the tmpdir + parameter to your my.ini configuration file. For more + information, see Section 2.3.7.2, "Creating an Option + File." + +2.3.1 MySQL Installation Layout on Microsoft Windows + + For MySQL 5.5 on Windows, the default installation directory + is C:\Program Files\MySQL\MySQL Server 5.5. Some Windows + users prefer to install in C:\mysql, the directory that + formerly was used as the default. However, the layout of the + subdirectories remains the same. - All of the files are located within this parent directory, using - the structure shown in the following table. + All of the files are located within this parent directory, + using the structure shown in the following table. - Table 2.4. Default MySQL Installation Layout for Microsoft Windows + Table 2.4 Default MySQL Installation Layout for Microsoft + Windows Directory Contents of Directory Notes bin Client programs and the mysqld server - %ALLUSERSPROFILE%\MySQL\MySQL Server 5.5\ Log files, databases - (Windows XP, Windows Server 2003) The Windows system variable - %ALLUSERSPROFILE% defaults to C:\Documents and Settings\All - Users\Application Data - %PROGRAMDATA%\MySQL\MySQL Server 5.5\ Log files, databases (Vista, - Windows 7, Windows Server 2008, and newer) The Windows system - variable %PROGRAMDATA% defaults to C:\ProgramData + %ALLUSERSPROFILE%\MySQL\MySQL Server 5.5\ Log files, + databases (Windows XP, Windows Server 2003) The Windows + system variable %ALLUSERSPROFILE% defaults to C:\Documents + and Settings\All Users\Application Data + %PROGRAMDATA%\MySQL\MySQL Server 5.5\ Log files, databases + (Vista, Windows 7, Windows Server 2008, and newer) The + Windows system variable %PROGRAMDATA% defaults to + C:\ProgramData examples Example programs and scripts include Include (header) files lib Libraries scripts Utility scripts share Miscellaneous support files, including error messages, - character set files, sample configuration files, SQL for database - installation + character set files, sample configuration files, SQL for + database installation - If you install MySQL using a Windows MSI package, this package - creates and sets up the data directory that the installed server - will use, but as of MySQL 5.5.5, it also creates a pristine - "template" data directory named data under the installation - directory. This directory can be useful when the machine will be - used to run multiple instances of MySQL: After an installation has - been performed using an MSI package, the template data directory - can be copied to set up additional MySQL instances. See Section - 5.3, "Running Multiple MySQL Instances on One Machine." - -2.3.2. Choosing An Installation Package - - For MySQL 5.5, there are installation package formats to choose - from when installing MySQL on Windows: - Note - - MySQL Installer and the "Complete Package" methods for installing - MySQL are similar, but different. The MySQL Installer is the newer - and more advanced option, and it includes all functionality found - within the "Complete Package." + If you install MySQL using a Windows MSI package, this + package creates and sets up the data directory that the + installed server will use, but as of MySQL 5.5.5, it also + creates a pristine "template" data directory named data under + the installation directory. This directory can be useful when + the machine will be used to run multiple instances of MySQL: + After an installation has been performed using an MSI + package, the template data directory can be copied to set up + additional MySQL instances. See Section 5.3, "Running + Multiple MySQL Instances on One Machine." + +2.3.2 Choosing An Installation Package + + For MySQL 5.5, there are installation package formats to + choose from when installing MySQL on Windows: + Note + + MySQL Installer and the "Complete Package" methods for + installing MySQL are similar, but different. The MySQL + Installer is the newer and more advanced option, and it + includes all functionality found within the "Complete + Package." * MySQL Installer: This package has a file name similar to - mysql-installer-community-5.5.36.0.msi or - mysql-installer-commercial-5.5.36.0.msi, and utilizes MSI's to - automatically install MySQL server and other products. It will - download and apply updates to itself, and for each of the - installed products. It also configures the additional - non-server products. - The installed products are configurable, and this includes: - documentation with samples and examples, connectors (such as - C, C++, J, NET, and ODBC), MySQL Workbench, MySQL Notifier for - Microsoft Windows, MySQL for Excel, and the MySQL Server with - its components. - MySQL Installer will run on all Windows platforms that are - supported by MySQL (see - http://www.mysql.com/support/supportedplatforms/database.html) - . Note: because MySQL is not a native component of Windows and - depends on .NET, it will not work on minimal installation - options like the "Server Core" version of Windows Server 2008. - For instructions on installing MySQL using MySQL Installer, - see Section 2.3.3, "Installing MySQL on Microsoft Windows - Using MySQL Installer." - - * The Complete Package: This package has a file name similar to - mysql-5.5.36-win32.msi and contains all files needed for a - complete Windows installation, including the Configuration - Wizard. This package includes optional components such as the - embedded server and benchmark suite. - - * The Noinstall Archive: This package has a file name similar to - mysql-5.5.36-win32.zip and contains all the files found in the - Complete install package, with the exception of the - Configuration Wizard. This package does not include an - automated installer, and must be manually installed and - configured. - - MySQL Installer is recommended for most users. Both MySQL - Installer and the alternative "Complete distribution" versions are - available as .msi files for use with installations on Windows. The - Noinstall distribution is packaged as a Zip archive. To use a Zip - archive, you must have a tool that can unpack .zip files. - - Your choice of install package affects the installation process - you must follow. If you choose to install using MySQL Installer, - see Section 2.3.3, "Installing MySQL on Microsoft Windows Using - MySQL Installer." If you choose to install a standard MSI package, - see Section 2.3.5, "Installing MySQL on Microsoft Windows Using an - MSI Package." If you choose to install a Noinstall archive, see - Section 2.3.7, "Installing MySQL on Microsoft Windows Using a - noinstall Zip Archive." - -2.3.3. Installing MySQL on Microsoft Windows Using MySQL Installer - - MySQL Installer is an application that simplifies the installation - and updating process for a wide range of MySQL products, including - MySQL Notifier for Microsoft Windows, MySQL Workbench, and MySQL - for Excel. From this central application, you can see which MySQL - products are already installed, configure them, and update or - remove them if necessary. The installer can also install plugins, - documentation, tutorials, and example databases. The MySQL - Installer is only available for Microsoft Windows, and includes - both a GUI and command-line interface. + mysql-installer-community-5.5.44.0.msi or + mysql-installer-commercial-5.5.44.0.msi, and utilizes + MSIs to automatically install MySQL server and other + products. It will download and apply updates to itself, + and for each of the installed products. It also + configures the additional non-server products. + The installed products are configurable, and this + includes: documentation with samples and examples, + connectors (such as C, C++, J, NET, and ODBC), MySQL + Workbench, MySQL Notifier, MySQL for Excel, and the MySQL + Server with its components. + MySQL Installer will run on all Windows platforms that + are supported by MySQL (see + http://www.mysql.com/support/supportedplatforms/database. + html). + Note + Because MySQL Installer is not a native component of + Microsoft Windows and depends on .NET, it will not work + on minimal installation options like the "Server Core" + version of Windows Server 2008. + For instructions on installing MySQL using MySQL + Installer, see Section 2.3.3, "Installing MySQL on + Microsoft Windows Using MySQL Installer." + + * The Complete Package: This package has a file name + similar to mysql-5.5.44-win32.msi or + mysql-5.5.44-winx64.zip, and contains all files needed + for a complete Windows installation, including the + Configuration Wizard. This package includes optional + components such as the embedded server and benchmark + suite. + + * The Noinstall Archive: This package has a file name + similar to mysql-5.5.44-win32.zip or + mysql-5.5.44-winx64.zip, and contains all the files found + in the Complete install package, with the exception of + the GUI. This package does not include an automated + installer, and must be manually installed and configured. + + MySQL Installer is recommended for most users. + + Your choice of install package affects the installation + process you must follow. If you choose to use MySQL + Installer, see Section 2.3.3, "Installing MySQL on Microsoft + Windows Using MySQL Installer." If you choose to install a + standard MSI package, see Section 2.3.5, "Installing MySQL on + Microsoft Windows Using an MSI Package." If you choose to + install a Noinstall archive, see Section 2.3.7, "Installing + MySQL on Microsoft Windows Using a noinstall Zip Archive." + +2.3.3 Installing MySQL on Microsoft Windows Using MySQL Installer + + MySQL Installer simplifies the installation and updating + process for your MySQL products on Microsoft Windows. From + this central application, you can view, remove, update, and + reconfigure the existing MySQL products on your system. MySQL + Installer can also install plugins, documentation, tutorials, + and example databases. The MySQL Installer is only available + for Microsoft Windows, and includes both GUI and command-line + interfaces. + + The supported products include: + + * MySQL server (http://dev.mysql.com/doc/) (one or multiple + versions) + + * MySQL Workbench + + * MySQL Connectors + (http://dev.mysql.com/doc/index-connectors.html) (.Net / + Python / ODBC / Java / C / C++) + + * MySQL Notifier + + * MySQL for Excel + (http://dev.mysql.com/doc/mysql-for-excel/en/index.html) + + * MySQL for Visual Studio + (http://dev.mysql.com/doc/connector-net/en/connector-net- + visual-studio.html) + + * MySQL Utilities and MySQL Fabric + (http://dev.mysql.com/doc/index-utils-fabric.html) + + * MySQL Samples and Examples + + * MySQL Documentation + + * MySQL Installer is also installed and remains on the + system as its own application Installer package types - * Full: Bundles all of the MySQL products (including MySQL - Server). The file is over 160MB, and have names of the form - mysql-installer-community-VERSION.N.msi where VERSION is the - MySQL Server version number such as 5.6 and N is the package - number, which begins at 0. - - * Web: Only contains the Installer and configuration files, and - it only downloads the MySQL products you choose to install. - The file is about 2MB, and have names of the form - mysql-installer-community-web-VERSION.N.msi where VERSION is - the MySQL Server version number such as 5.6 and N is the - package number, which begins at 0. + * Full: Bundles all of the MySQL products (including the + MySQL server). The file' size is over 200MB, and its name + has the form mysql-installer-community-VERSION.N.msi + where VERSION is the MySQL Server version number such as + 5.6 and N is the package number, which begins at 0. + + * Web: Only contains the Installer and configuration files, + and it only downloads the MySQL products you choose to + install. The size of this file is about 2MB; the name of + the file has the form + mysql-installer-community-web-VERSION.N.msi where VERSION + is the MySQL Server version number such as 5.6 and N is + the package number, which begins at 0. Installer editions * Community edition: Downloadable at - http://dev.mysql.com/downloads/installer/. It installs the - community edition of all MySQL products. + http://dev.mysql.com/downloads/installer/. It installs + the community edition of all MySQL products. - * Commercial edition: Downloadable at either My Oracle Support - (https://support.oracle.com/) (MOS) or + * Commercial edition: Downloadable at either My Oracle + Support (https://support.oracle.com/) (MOS) or https://edelivery.oracle.com/. It installs the commercial - version of all MySQL products, including Workbench SE. It also - integrates with your MOS account, so enter in your MOS - credentials to automatically receive updates for your - commercial MySQL products. + version of all MySQL products, including Workbench SE/EE. + It also integrates with your MOS account. + Note + Entering your MOS credentials is optional when installing + bundled MySQL products, but your credentials are required + when choosing non-bundled MySQL products that MySQL + Installer must download. - For release notes detailing the changes in each release of MySQL + For notes detailing the changes in each release of MySQL Installer, see MySQL Installer Release Notes (http://dev.mysql.com/doc/relnotes/mysql-installer/en/). - MySQL Installer is compatible with pre-existing installations, and - adds them to its list of installed components. And while the MySQL - Installer is bundled with a specific version of MySQL Server, a - single MySQL Installer instance can install and manage multiple - MySQL Server versions. For example, a single MySQL Installer - instance can install versions 5.1, 5.5, and 5.6. It can also - manage either commercial or community editions of the MySQL - Server. + MySQL Installer is compatible with pre-existing + installations, and adds them to its list of installed + components. While the standard MySQL Installer is bundled + with a specific version of MySQL Server, a single MySQL + Installer instance can install and manage multiple MySQL + Server versions. For example, a single MySQL Installer + instance can install (and update) versions 5.5, 5.6, and 5.7 + on the host. + Note + + A single host can not have both community and commercial + editions of MySQL Server installed. For example, if you want + both MySQL Server 5.5 and 5.6 installed on a single host, + then both must be the same edition. + + MySQL Installer handles the initial configuration and set up + of the applications. For example: + + 1. It creates initial MySQL Server connections in MySQL + Workbench. + + 2. It creates the configuration file (my.ini) that is used + to configure the MySQL Server. The values written to this + file are influenced by choices you make during the + installation process. + + 3. It can optionally import example databases. + + 4. It can optionally create MySQL Server user accounts with + configurable permissions based on general roles, such as + DB Administrator, DB Designer, and Backup Admin. It + optionally creates a Windows user named MysqlSys with + limited privileges, which would then run the MySQL + Server. + User accounts may also be added and configured in MySQL + Workbench. + + 5. If the "Advanced Configuration" option is checked, then + the Logging Options are also configured. This includes + defining file paths for the error log, general log, slow + query log (including the configuration of seconds it + requires to execute a query), and the binary log. + + MySQL Installer can optionally check for updated components + and download them for you. + +2.3.3.1 MySQL Installer GUI + + Installing MySQL Installer adds a link to the Start menu + under the MySQL group. Click Start, All Programs MySQL, MySQL + Installer to reload the MySQL Installer GUI. + Note + + Files that are generated by MySQL Installer grant full + permissions to the user that executes MySQL Installer, + including my.ini. This does not apply to files and + directories for specific products such as the MySQL Server + data directory in %ProgramData% that is owned by SYSTEM. + + The initial execution of MySQL Installer requires you to + accept the license agreement before installing MySQL + products. + + Figure 2.7 MySQL Installer - License Agreement + MySQL Installer - License Agreement + +Installing New Packages + + Choose the appropriate Setup Type for your system. The + selected type determines which MySQL products are installed + on your system, or select Custom to manually choose + individual products. + + * Developer: Install all products needed to develop + applications with MySQL. This is the default option. + + * Server only: Only install the MySQL server. + + * Client only: Only install the MySQL client products, + which does not include the MySQL server. + + * Full: Install all MySQL products. + + * Custom: Manually select the MySQL products to install. + Note + After the initial installation, you may use MySQL + Installer to manually select MySQL products to install or + remove. In other words, MySQL Installer becomes a MySQL + product management system. + + Figure 2.8 MySQL Installer - Choosing a Setup Type + MySQL Installer - Choosing a Setup Type + + After you select a setup type, the MySQL Installer will check + your system for the necessary external requirements for each + of the selected MySQL products. MySQL Installer will either + download and install the missing components onto your system, + or point you to the download location and set Status to + "Manual". + + The next window lists the MySQL products that are scheduled + to be installed: + + Figure 2.9 MySQL Installer - Installation Progress + MySQL Installer - Installation Progress + + As components are installed, their Status changes from a + progress percentage to "Complete". + + After all components are installed, the next step configures + some of the recently installed MySQL products. The + Configuration Overview window displays the progress and then + loads a configuration window, if required. Our example + configures MySQL Server 5.6.x. + +Configuring MySQL Server + + Configuring the MySQL server begins with defining several + Type and Networking options. + + Figure 2.10 MySQL Installer - Configuration Overview + MySQL Installer - Configuration Overview + + Server Configuration Type + + Choose the MySQL server configuration type that describes + your setup. This setting defines the amount of system + resources that will be assigned to your MySQL server + instance. + + * Developer: A machine that will host many other + applications, and typically this is your personal + workstation. This option configures MySQL to use the + least amount of memory. + + * Server: Several other applications will be running on + this machine, such as a web server. This option + configures MySQL to use a medium amount of memory. + + * Dedicated: A machine that is dedicated to running the + MySQL server. Because no other major applications are + running on the server, such as web servers, this option + configures MySQL to use all available memory. + + Connectivity + + Connectivity options control how you will connect to MySQL. + Options include: + + * TCP/IP: You may enable TCP/IP Networking here as + otherwise only localhost connections are allowed. Also + define the Port Number and whether to open the firewall + port for network access. + + * Named Pipe: Enable and define the pipe name, similar to + using the --enable-named-pipe option. + + * Shared Memory: Enable and then define the memory name, + similar to using the --shared-memory option. + + Advanced Configuration + + Checking the "Advanced Configuration" option provides + additional Logging Options to configure. This includes + defining file paths for the error log, general log, slow + query log (including the configuration of seconds it requires + to execute a query), and the binary log. + + Figure 2.11 MySQL Installer - MySQL Server Configuration: + Type and Networking + MySQL Installer- MySQL Server Configuration: Type and + Networking + +Accounts and Roles + + Next, define your MySQL account information. Assigning a root + password is required. + + Optionally, you can add additional MySQL user accounts with + predefined user roles. Each predefined role, such as "DB + Admin", are configured with their own set of privileges. For + example, the "DB Admin" role has more privileges than the "DB + Designer" role. Click the Role dropdown for a list of role + descriptions. + Note + + If the MySQL Server is already installed, then you must also + enter the Current Root Password. + + Figure 2.12 MySQL Installer - MySQL Server Configuration: + User Accounts and Roles + MySQL Installer - MySQL Server Configuration: User Accounts + and Roles + + Figure 2.13 MySQL Installer - MySQL Server Configuration: + User Accounts and Roles: Adding a User + MySQL Installer - MySQL Server Configuration: User Accounts + and Roles: Adding a User + +Windows Service + + Next, configure the Windows Service details. This includes + the service name, whether the MySQL Server should be loaded + at startup, and how the Windows Service for MySQL Server is + executed. + + Figure 2.14 MySQL Installer - MySQL Server Configuration: + Windows Service + MySQL Installer - MySQL Server Configuration: Windows Service Note - A single host can not have both community and commercial editions - of MySQL Server installed. For example, if you want both MySQL - Server 5.5 and 5.6 installed on a single host, then both must be - the same commercial or community edition. + When configuring Run Windows Services as ... using a Custom + User, the custom user must have privileges to log on to + Microsoft Windows as a service. And the Next button will be + disabled until this user is configured with these user + rights. + + On Microsoft Windows 7, this is configured by loading the + Start Menu, Control Panel, Administrative Tools, Local + Security Policy, Local Policies, User Rights Assignment, then + Log On As A Service. Choose Add User or Group here to add the + custom user, and then OK, OK to save. + +Advanced Options + + The next configuration step is available if the Advanced + Configuration option was checked. This section includes + options that are related to the MySQL log files: + + Figure 2.15 MySQL Installer - MySQL Server Configuration: + Logging Options + MySQL Installer - MySQL Server Configuration: Logging Options + + Click Next to continue on to the final page before all of the + requested changes are applied. This Apply Server + Configuration page details the configuration steps that will + be performed. - MySQL Installer handles the initial configuration and setup of the - applications. For example: + Figure 2.16 MySQL Installer - MySQL Server Configuration: + Apply Server Configuration + MySQL Installer - MySQL Server Configuration: Apply Server + Configuration - 1. It will create MySQL Server connections in MySQL Workbench. + Click Execute to execute the configuration steps. The icon + for each step toggles from white to green on success, or the + process stops on failure. Click the Log tab to view the log. - 2. It creates the configuration file (my.ini) that is used to - configure the MySQL Server. The values written to this file - are influenced by choices you make during the installation - process. + After the MySQL Installer configuration process is finished, + MySQL Installer reloads the opening page where you can + execute other installation and configuration related actions. - 3. It imports example databases. + MySQL Installer is added to the Microsoft Windows Start menu + under the MySQL group. Opening MySQL Installer loads its + dashboard where installed MySQL products are listed, and + other MySQL Installer actions are available: - 4. It creates MySQL Server user accounts with configurable - permissions based on general roles, such as DB Administrator, - DB Designer, and Backup Admin. It optionally creates a Windows - user named MysqlSys with limited privileges, which would then - run the MySQL Server. - This feature is only available during the initial installation - of the MySQL Server, and not during future updates. User - accounts may also be added with MySQL Workbench. + Figure 2.17 MySQL Installer - Main Dashboard + MySQL Installer - Main Dashboard - 5. If the "Advanced Configuration" option is checked, then the - Logging Options are also configured. This includes defining - file paths for the error log, general log, slow query log - (including the configuration of seconds it requires to execute - a query), and the binary log. +Adding MySQL Products - MySQL Installer can optionally check for updated components and - download them for you automatically. + Click Add to add new products. This loads the Select Products + and Features page: -2.3.3.1. MySQL Installer GUI + Figure 2.18 MySQL Installer - Select Products and Features + MySQL Installer - Select Products and Features - After installation of the GUI version, the installer will have add - its own Start Menu item under MySQL. + From here, choose the MySQL products you want to install from + the left Available Products pane, and then click the green + right arrow to queue products for installation. + + Optionally, click Edit to open the product and features + search filter: + + Figure 2.19 MySQL Installer - Select Products and Features + Filter + MySQL Installer - Select Products and Features Filter + + For example, you might choose to include Pre-Release products + in your selections, such as a Beta product that has not yet + reached GA status. Note - Files that are generated by MySQL Installer grant full permissions - to the user that executes MySQL Installer, including my.ini. This - does not apply to files and directories for specific products such - as the MySQL Server data directory in ProgramData, that is owned - by SYSTEM. + The ability to install Pre-Release versions of MySQL products + was added in MySQL Installer 1.4.0. + + Select all of the MySQL products you want to install, then + click Next to continue, and then Execute to execute the + installation process to install all of the selected products. - After the installer itself has been installed and started, the - following screen is displayed: +2.3.3.1.1 MySQL Product Catalog - Figure 2.7. MySQL Installer - Welcome Screen - MySQL Installer - Welcome Screen + MySQL Installer stores a MySQL product catalog. The catalog + can be updated either manually or automatically, and the + catalog change history is also available. + Note - There are three main options: + The MySQL product catalog was added in MySQL Installer 1.4.0. - 1. Install MySQL Products - The Installation Wizard. + Manual updates - 2. About MySQL - Learn about MySQL products and features. + You can update the MySQL product catalog at any time by + clicking Catalog on the Installer dashboard. - 3. Resources - Information to help install and configure MySQL. + Figure 2.20 MySQL Installer - Open the MySQL Product Catalog + MySQL Installer - Open the MySQL Product Catalog - To Install MySQL Products after executing MySQL Installer for the - first time, you must accept the license agreement before - proceeding with the installation process. + From there, click Execute to update the product catalog. - Figure 2.8. MySQL Installer - License Agreement - MySQL Installer - License Agreement + Automatic updates - If you are connected to the Internet, then the Installer will - search for the latest MySQL components and add them to the - installation bundle. Click Connect to the Internet to complete - this step, or otherwise check the Skip checkbox and then Continue. - - Figure 2.9. MySQL Installer - Find latest products - MySQL Installer - Find latest products - - If you chose "Connect to the Internet," the next page will show - the progress of MySQL Installer's search for available updates. - When the search is complete (or if you opted to skip the search), - you will be taken to the Choose Setup Type page: + You can configure MySQL Installer to automatically update the + MySQL product catalog once per day. To enable this feature + and set the update time, click the wrench icon on the + Installer dashboard. - Figure 2.10. MySQL Installer - Choosing a Setup Type - MySQL Installer - Choosing a Setup Type + The next window configures the Automatic Catalog Update. + Enable or disable this feature, and also set the hour. - Determine the option most compatible with your preferences by - reading the Setup Type Description descriptions. + Figure 2.21 MySQL Installer - Configure the Catalog Scheduler + MySQL Installer - Configure the Catalog Scheduler - The Installation and Data paths are also defined here, and a - caution flag will notify you if the data path you define already - exists. + This option uses the Windows Task Scheduler to schedule a + task named "ManifestUpdate". - After you select a setup type, the MySQL Installer will check your - system for the necessary external requirements and download then - install missing components onto your system. + Change History - Figure 2.11. MySQL Installer - Check Requirements - MySQL Installer - Check Requirements + MySQL Installer tracks the change history for all of the + MySQL products. Click Catalog from the dashboard, optionally + update the catalog (or, toggle the Do not update at this time + checkbox), click Next/Execute, and then view the change + history. - The next window lists the MySQL products that are scheduled to be - installed: + Figure 2.22 MySQL Installer - Catalog Change History + MySQL Installer - Catalog Change History - Figure 2.12. MySQL Installer - Installation Progress - MySQL Installer - Installation Progress +2.3.3.1.2 Remove MySQL Products - As components are installed, you'll see their status change from - "to be installed" to "install success." + MySQL Installer can also remove MySQL products from your + system. To remove a MySQL product, click Remove from the + Installer dashboard. This opens a window with a list of + installed MySQL products. Select the MySQL products you want + to remove (uninstall), and then click Execute to begin the + removal process. + Note - Figure 2.13. MySQL Installer - Installation Progress status - MySQL Installer - Installation Progress status + To select all MySQL products, click the [ ] checkbox to the + left of the Product label. - After all components are installed, the next step involves - configuring the products. The Configuration Overview window - displays the progress and then loads a configuration window if it - is required. + Figure 2.23 MySQL Installer - Removing Products: Select + MySQL Installer - Removing Products: Select - Figure 2.14. MySQL Installer - Configuration Overview - MySQL Installer - Configuration Overview + Figure 2.24 MySQL Installer - Removing Products: Executed + MySQL Installer - Removing Products: Executed + +2.3.3.1.3 Alter MySQL Products + + MySQL Installer offers several options to alter your MySQL + product installations. + +Upgrade + + MySQL products with an available upgrade are highlighted on + the main dashboard. Products with available upgrades will + have an upgrade icon next to their version number. + + Figure 2.25 MySQL Installer - Upgrade a MySQL Product + MySQL Installer - Upgrade a MySQL Product + Note + + Available upgrades are determined by having a current + catalog. For information about keeping your MySQL product + catalog current, see Section 2.3.3.1.1, "MySQL Product + Catalog." + + Click Upgrade to view a list upgradable products. Our example + indicates that MySQL server 5.6.19 can be upgraded to version + 5.6.20. + + Figure 2.26 MySQL Installer - Select Products To Upgrade + MySQL Installer - Select Products To Upgrade + + Select (check) the products to upgrade, and optionally click + the changes link to view the product's release notes in your + browser. Click Next to begin the upgrade process. + + Figure 2.27 MySQL Installer - Apply Updates + MySQL Installer - Apply Updates + + A MySQL server upgrade will also check and upgrade the + server's database. Although optional, this step is + recommended. + + Figure 2.28 MySQL Installer - Check and Upgrade Database + MySQL Installer - Check and Upgrade Database + + Upon completion, your upgraded products will be upgraded and + available to use. A MySQL server upgrade also restarts the + MySQL server. + +Reconfigure + + Some MySQL products, such as the MySQL server, include a + Reconfigure option. It opens the same configuration options + that were set when the MySQL product was installed, and is + pre-populated with the current values. + + To execute, click the Reconfigure link under the Quick Action + column on the main dashboard for the MySQL product that you + want to reconfigure. + + Figure 2.29 MySQL Installer - Reconfigure a MySQL Product + MySQL Installer - Reconfigure a MySQL Product + + In the case of the MySQL server, this opens the familiar + configuration wizard. + + Figure 2.30 MySQL Installer - Reconfiguration Wizard + MySQL Installer - Reconfiguration Wizard - The ideal MySQL Server configuration depends on your intended use, - as explained in the next window. Choose the description that most - closely applies to your machine. - - You may enable TCP/IP Networking here as otherwise only localhost - connections are allowed. - - Checking the "Advanced Configuration" option provides additional - Logging Options to configure. This includes defining file paths - for the error log, general log, slow query log (including the - configuration of seconds it requires to execute a query), and the - binary log. - - Figure 2.15. MySQL Installer - MySQL Server Configuration: Define - platform, networking, and logging options - MySQL Installer- MySQL Server Configuration: Define platform, - networking, and logging options - - Next, choose your account information. Defining a root password is - required, whereas it's optional to create additional users. There - are several different predefined user roles that each have - different permission levels. For example, a "DB Admin" will have - more privileges than a "DB Designer.". - - Figure 2.16. MySQL Installer - MySQL Server Configuration: User - accounts - MySQL Installer - MySQL Server Configuration: User accounts - Note - - If the MySQL Server is already installed, then the Current Root - Password will also be needed. - - Next, configure the Windows Service Details. This includes the - service name, how the MySQL Server should be loaded at startup, - and how the Windows Service for MySQL Server will be run. - - Figure 2.17. MySQL Installer - MySQL Server Configuration: Windows - service details - MySQL Installer - MySQL Server Configuration: Windows service - details - Note - - When configuring Run Windows Services as ... using a Custom User, - the custom user must have privileges to log on to Windows as a - service. And the Next button will be disabled until this user is - given these user rights. - - On Microsoft Windows 7, this is configured by loading the Start - Menu, Control Panel, Administrative Tools, Local Security Policy, - Local Policies, User Rights Assignment, then Log On As A Service. - Choose Add User or Group here to add the custom user, and then OK, - OK to save. - - The final configuration step is available if the Advanced - Configuration option was checked, and it includes configuration - options related to log file names: - - Figure 2.18. MySQL Installer - MySQL Server Configuration: Logging - options - MySQL Installer - MySQL Server Configuration: Logging options - - After the MySQL Installer configuration process is completed, you - may save the installation log, and then load MySQL Workbench if - the Start MySQL Workbench after Setup option is checked: - - Figure 2.19. MySQL Installer - Installation Complete - MySQL Installer - Installation Complete - - You can now open MySQL Installer from the Microsoft Windows Start - menu under the MySQL group, which will load the MySQL Installer - Maintenance Screen. This is used to add, update, and remove - features. - - Figure 2.20. MySQL Installer - Maintenance Screen - MySQL Installer - Maintenance Screen - Note - - An Update Screen screen is shown if MySQL Installer is used on a - machine with older products installed, as opposed to the - Maintenance Screen shown above. However, the functionality remains - the same. - - Add/Modify Products and Features will list all installed and - available MySQL products. - - Figure 2.21. MySQL Installer - Add/Modify Products and Features - MySQL Installer - Add/Modify Products and Features - - The installation is now complete. MySQL Server should be running, - and most MySQL products installed and available for use. - - See also the MySQL Workbench documentation - (http://dev.mysql.com/doc/workbench/en/). - -2.3.3.2. MySQL Installer Console - - MySQLInstallerConsole provides functionality similar to the GUI - version of MySQL Installer, but from the command-line. It is - installed when MySQL Installer is initially executed, and then - available within the MySQL Installer directory. Typically that is - in C:\Program Files (x86)\MySQL\MySQL Installer\, and the console - must be executed with administrative privileges. - - To use, invoke the Command Prompt with administrative privileges - by choosing Start, Accessories, then right-click on Command Prompt - and choose Run as administrator. And from the command-line, - optionally change the directory to where MySQLInstallerConsole is - located: +Modify + + Many MySQL products contain feature components that can be + added or removed. For example, Debug binaries and Client + Programs are subcomponents of the MySQL server. + + The modify the features of a product, click Modify on the + main dashboard. + + Figure 2.31 MySQL Installer - Modify Product Features + MySQL Installer - Modify Product Features + + Click Execute to execute the modification request. + +2.3.3.2 MySQL Installer Console + + MySQLInstallerConsole provides functionality similar to the + GUI version of MySQL Installer, but from the command-line. It + is installed when MySQL Installer is initially executed, and + then available within the MySQL Installer directory. + Typically that is in C:\Program Files (x86)\MySQL\MySQL + Installer\, and the console must be executed with + administrative privileges. + + To use, invoke the Command Prompt with administrative + privileges by choosing Start, Accessories, then right-click + on Command Prompt and choose Run as administrator. And from + the command-line, optionally change the directory to where + MySQLInstallerConsole is located: C:\> cd "C:\Program Files (x86)\MySQL\MySQL Installer" +C:\> MySQLInstallerConsole.exe help - MySQLInstallerConsole supports the following options, which are - specified on the command line: +C:\Program Files (x86)\MySQL\MySQL Installer for Windows>MySQLInstalle +rConsole.exe help - * --help, -h, or -? - Displays a help message with usage examples, and then exits. -C:\> MySQLInstallerConsole --help - - * --updates (or -u) - Checks for new products before any further action is taken. - Disabled by default. - - * --nowait - Skips the final pause when the program finishes. Otherwise, a - "Press Enter to continue." dialogue is generated. It is used - in conjunction with other options. - - * --catalog=catalog_name (or -c) - Sets the default catalog. Use --list to view a list of - available catalogs. - - * --type=installation_type (or -t) - Sets the installation type. - The possible values for installation_type are: developer, - server, client, full, and custom. - - * --action=action_name - The action being performed. - The possible values are: install, remove, upgrade, list, and - status. - - + install: Installs a product or products, as defined by - --products - - + upgrade: Upgrades a product or products, as defined by - --products. - - + remove: Removes a product or products, as defined by - --products. - - + list: Lists the product manifest, both installed and - available products. - - + status: Shows the status after another action is - performed. - - * --product=product_name[:feature1],[feature2], [...] (or -p) - Set the feature list of a product. Use --list to view - available products, or pass in --product=* (an asterisk) to - install all available products. - - * --config=product_name:passwd=root_password[;parameter1=value], - [;parameter2=value], ... - The configuration parameters for the most recently listed - products. +The following commands are available: + +Configure - Configures one or more of your installed programs. +Help - Provides list of available commands. +Install - Install and configure one or more available MySQL programs +. +List - Provides an interactive way to list all products available +. +Modify - Modifies the features of installed products. +Remove - Removes one or more products from your system. +Status - Shows the status of all installed products. +Update - Update the current product catalog. +Upgrade - Upgrades one or more of your installed programs. + + MySQLInstallerConsole supports the following options, which + are specified on the command line: + + * configure [product1]:[setting]=[value]; + [product2]:[setting]=[value]; [...] + Configure one or more MySQL products on your system. + Switches include: + + + -showsettings : Displays the available options for + the selected product, by passing in the product name + after -showsettings. + + + -silent : Disable confirmation prompts. +C:\> MySQLInstallerConsole configure -showsettings server +C:\> MySQLInstallerConsole configure server:port=3307 + + + * help [command] + Displays a help message with usage examples, and then + exits. Pass in an additional command to receive help + specific to that command. +C:\> MySQLInstallerConsole help +C:\> MySQLInstallerConsole help install + + + * install [product]:[features]:[config block]:[config + block]:[config block]; [...] + Install one or more MySQL products on your system. + Switches and syntax options include: + + + -type=[SetupType] : Installs a predefined set of + software. The "SetupType" can be one of the + following: + Note + Non-custom setup types can only be chosen if no + other MySQL products are installed. + o Developer: Installs a complete development + environment. + o Server: Installs a single MySQL server + o Client: Installs client programs and libraries + o Full: Installs everything + o Custom: Installs user selected products. This + is the default option. + + + -showsettings : Displays the available options for + the selected product, by passing in the product name + after -showsettings. + + + -silent : Disable confirmation prompts. + + + [config block]: One or more configuration blocks can + be specified. Each configuration block is a + semicolon separated list of key value pairs. A block + can include either a "config" or "user" type key, + where "config" is the default type if one is not + defined. + Only one "config" type block can be defined per + product. A "user" block should be defined for each + user that should be created during the product's + installation. + Note + Adding users is not supported when a product is + being reconfigured. + + + [feature]: The feature block is a semicolon + separated list of features, or '*' to select all + features. +C:\> MySQLInstallerConsole install server;5.6.22:*:port=3307;serverid= +2:type=user;username=foo;password=bar;role=DBManager +C:\> MySQLInstallerConsole install server;5.6.22;x64 -silent + + + * list + Lists an interactive console where all of the available + MySQL products can be searched. Execute + MySQLInstallerConsole list to launch the console, and + enter in a substring to search. +C:\> MySQLInstallerConsole list + + + * modify [product1:-removelist|+addlist] + [product2:-removelist|+addlist] [...] + Modifies or displays features of a previously installed + MySQL product. + + + -silent : Disable confirmation prompts. +C:\> MySQLInstallerConsole modify server +C:\> MySQLInstallerConsole modify server:+documentation +C:\> MySQLInstallerConsole modify server:-debug + + + * remove [product1] [product2] [...] + Removes one ore more products from your system. + + + * : Pass in * to remove all of the MySQL products. + + + -continue : Continue the operation even if an error + occurs. + + + -silent : Disable confirmation prompts. +C:\> MySQLInstallerConsole remove * +C:\> MySQLInstallerConsole remove server + + + * status + Provides a quick overview of the MySQL products that are + installed on the system. Information includes product + name and version, architecture, date installed, and + install location. +C:\> MySQLInstallerConsole status + + + * upgrade [product1:version] [product2:version], [...] + Upgrades one or more products on your system. Syntax + options include: + + + * : Pass in * to upgrade all products to the latest + version, or pass in specific products. + + + ! : Pass in ! as a version number to upgrade the + MySQL product to its latest version. + + + -silent : Disable confirmation prompts. +C:\> MySQLInstallerConsole upgrade * +C:\> MySQLInstallerConsole upgrade workbench:6.2.2 +C:\> MySQLInstallerConsole upgrade workbench:! +C:\> MySQLInstallerConsole upgrade workbench:6.2.2 excel:1.3.2 + + + * update + Downloads the latest MySQL product catalog to your + system. On success, the download catalog will be applied + the next time either MySQLInstaller or + MySQLInstallerConsole is executed. +C:\> MySQLInstallerConsole update + + Note + The Automatic Catalog Update GUI option executes this + command from the Windows Task Scheduler. + +2.3.4 MySQL Notifier - * --user=product_name:name=username,host:hostname,role=rolename, - password=password or - --user=product_name:name=username,host:hostname,role=rolename, - tokens=tokens - Creates a new user. - Requires: name, host, role, and the password or tokens. Tokens - are separated by pipe ("|") characters. - -2.3.4. MySQL Notifier for Microsoft Windows - - The MySQL Notifier for Microsoft Windows is a tool that enables - you to monitor and adjust the status of your local and remote - MySQL Server instances through an indicator that resides in the - system tray. The MySQL Notifier for Microsoft Windows also gives - quick access to several MySQL GUI tools (such as MySQL Workbench) - through its context menu. - - The MySQL Notifier for Microsoft Windows is installed by MySQL - Installer, and (by default) will start-up when Microsoft Windows - is started. + The MySQL Notifier is a tool that enables you to monitor and + adjust the status of your local and remote MySQL Server + instances through an indicator that resides in the system + tray. The MySQL Notifier also gives quick access to several + MySQL GUI tools (such as MySQL Workbench) through its context + menu. + + The MySQL Notifier is installed by MySQL Installer, and (by + default) will start-up when Microsoft Windows is started. Note To install, download and execute the MySQL Installer - (http://dev.mysql.com/downloads/installer/), be sure the MySQL - Notifier for Microsoft Windows product is selected, then proceed - with the installation. See the MySQL Installer manual for - additional details. - - For release notes detailing the changes in each release of MySQL - Notifier for Microsoft Windows, see the MySQL Notifier Release - Notes (http://dev.mysql.com/doc/relnotes/mysql-notifier/en/). + (http://dev.mysql.com/downloads/installer/), be sure the + MySQL Notifier product is selected, then proceed with the + installation. See the MySQL Installer manual for additional + details. + + For notes detailing the changes in each release of MySQL + Notifier, see the MySQL Notifier Release Notes + (http://dev.mysql.com/doc/relnotes/mysql-notifier/en/). Visit the MySQL Notifier forum (http://forums.mysql.com/list.php?173) for additional MySQL - Notifier for Microsoft Windows help and support. + Notifier help and support. Features include: * Start, Stop, and Restart instances of the MySQL Server. - * Automatically detects (and adds) new MySQL Server services. - These are listed under Manage Monitored Items, and may also be - configured. - - * The Tray icon changes, depending on the status. It's green if - all monitored MySQL Server instances are running, or red if at - least one service is stopped. The Update MySQL Notifier tray - icon based on service status option, which dictates this - behavior, is enabled by default for each service. + * Automatically detects (and adds) new MySQL Server + services. These are listed under Manage Monitored Items, + and may also be configured. + + * The Tray icon changes, depending on the status. It's + green if all monitored MySQL Server instances are + running, or red if at least one service is stopped. The + Update MySQL Notifier tray icon based on service status + option, which dictates this behavior, is enabled by + default for each service. * Links to other applications like MySQL Workbench, MySQL Installer, and the MySQL Utilities. For example, choosing @@ -1624,463 +1909,481 @@ Administration window for that particular instance. * If MySQL Workbench is also installed, then the Configure - Instance and SQL Editor options are available for local (but - not remote) MySQL instances. + Instance and SQL Editor options are available for local + (but not remote) MySQL instances. * Monitoring of both local and remote MySQL instances. Note - Remote monitoring is available since MySQL Notifier for Microsoft - Windows 1.1.0. + Remote monitoring is available since MySQL Notifier 1.1.0. - The MySQL Notifier for Microsoft Windows resides in the system - tray and provides visual status information for your MySQL Server - instances. A green icon is displayed at the top left corner of the - tray icon if the current MySQL Server is running, or a red icon if + The MySQL Notifier resides in the system tray and provides + visual status information for your MySQL Server instances. A + green icon is displayed at the top left corner of the tray + icon if the current MySQL Server is running, or a red icon if the service is stopped. - The MySQL Notifier for Microsoft Windows automatically adds - discovered MySQL Services on the local machine, and each service - is saved and configurable. By default, the Automatically add new - services whose name contains option is enabled and set to mysql. + The MySQL Notifier automatically adds discovered MySQL + Services on the local machine, and each service is saved and + configurable. By default, the Automatically add new services + whose name contains option is enabled and set to mysql. Related Notifications Options include being notified when new - services are either discovered or experience status changes, and - are also enabled by default. And uninstalling a service will also - remove the service from the MySQL Notifier for Microsoft Windows. + services are either discovered or experience status changes, + and are also enabled by default. And uninstalling a service + will also remove the service from the MySQL Notifier. Note The Automatically add new services whose name contains option - default changed from ".*mysqld.*" to "mysql" in Notifier 1.1.0. - - Clicking the system tray icon will reveal several options, as seen - in the screenshots below: + default changed from ".*mysqld.*" to "mysql" in Notifier + 1.1.0. - The Service Instance menu is the main MySQL Notifier for Microsoft - Windows window, and enables you to Stop, Start, and Restart the - MySQL Server. + Clicking the system tray icon will reveal several options, as + seen in the screenshots below: - Figure 2.22. MySQL Notifier for Microsoft Windows Service Instance - menu - MySQL Notifier for Microsoft Windows Service Instance menu + The Service Instance menu is the main MySQL Notifier window, + and enables you to Stop, Start, and Restart the MySQL Server. - The Actions menu includes several links to external applications - (if they are installed), and a a Refresh Status option to manually - refresh the status of all monitored services (in both local and - remote computers) and MySQL instances. + Figure 2.32 MySQL Notifier Service Instance menu + MySQL Notifier Service Instance menu + + The Actions menu includes several links to external + applications (if they are installed), and a Refresh Status + option to manually refresh the status of all monitored + services (in both local and remote computers) and MySQL + instances. Note - The main menu will not show the Actions menu when there are no - services being monitored by MySQL Notifier for Microsoft Windows. + The main menu will not show the Actions menu when there are + no services being monitored by MySQL Notifier. Note - The Refresh Status feature is available since MySQL Notifier for - Microsoft Windows 1.1.0. - - Figure 2.23. MySQL Notifier for Microsoft Windows Actions menu - MySQL Notifier for Microsoft Windows Actions menu - - The Actions, Options menu configures MySQL Notifier for Microsoft - Windows and includes options to: - - * Use colorful status icons: Enables a colorful style of icons - for the tray of the MySQL Notifier for Microsoft Windows. + The Refresh Status feature is available since MySQL Notifier + 1.1.0. - * Run at Windows Startup: Allows the application to be loaded - when Microsoft Windows starts. - - * Automatically Check For Updates Every # Weeks: Checks for a - new version of MySQL Notifier for Microsoft Windows, and runs - this check every # weeks. - - * Automatically add new services whose name contains: The text - used to filter services and add them automatically to the - monitored list of the local computer running MySQL Notifier, - and on remote computers already monitoring Windows services. - monitored services, and also filters the list of the Microsoft - Windows services for the Add New Service dialog. - Prior to version 1.1.0, this option was named "Automatically - add new services that match this pattern." - - * Notify me when a service is automatically added: Will display - a balloon notification from the taskbar when a newly - discovered service is added to the monitored services list. + Figure 2.33 MySQL Notifier Actions menu + MySQL Notifier Actions menu + + The Actions, Options menu configures MySQL Notifier and + includes options to: + + * Use colorful status icons: Enables a colorful style of + icons for the tray of the MySQL Notifier. + + * Run at Windows Startup: Allows the application to be + loaded when Microsoft Windows starts. + + * Automatically Check For Updates Every # Weeks: Checks for + a new version of MySQL Notifier, and runs this check + every # weeks. + + * Automatically add new services whose name contains: The + text used to filter services and add them automatically + to the monitored list of the local computer running MySQL + Notifier, and on remote computers already monitoring + Windows services. monitored services, and also filters + the list of the Microsoft Windows services for the Add + New Service dialog. + Prior to version 1.1.0, this option was named + "Automatically add new services that match this pattern." + + * Notify me when a service is automatically added: Will + display a balloon notification from the taskbar when a + newly discovered service is added to the monitored + services list. * Notify me when a service changes status: Will display a - balloon notification from the taskbar when a monitored service - changes its status. + balloon notification from the taskbar when a monitored + service changes its status. + + Figure 2.34 MySQL Notifier Options menu + MySQL Notifier Options menu - Figure 2.24. MySQL Notifier for Microsoft Windows Options menu - MySQL Notifier for Microsoft Windows Options menu + The Actions, Manage Monitored Items menu enables you to + configure the monitored services and MySQL instances. First, + with the Services tab open: - The Actions, Manage Monitored Items menu enables you to configure - the monitored services and MySQL instances. First, with the - Services tab open: - - Figure 2.25. MySQL Notifier for Microsoft Windows Manage Services - menu - MySQL Notifier for Microsoft Windows Manage Services menu + Figure 2.35 MySQL Notifier Manage Services menu + MySQL Notifier Manage Services menu The Instances tab is similar: - Figure 2.26. MySQL Notifier for Microsoft Windows Manage Instances - menu - MySQL Notifier for Microsoft Windows Manage Instances menu - - Adding a service or instance (after clicking Add in the Manage - Monitored Items window) enables you to select a running Microsoft - Windows service or instance connection, and configure MySQL - Notifier for Microsoft Windows to monitor it. Add a new service or + Figure 2.36 MySQL Notifier Manage Instances menu + MySQL Notifier Manage Instances menu + + Adding a service or instance (after clicking Add in the + Manage Monitored Items window) enables you to select a + running Microsoft Windows service or instance connection, and + configure MySQL Notifier to monitor it. Add a new service or instance by clicking service name from the list, then OK to accept. Multiple services and instances may be selected. - Figure 2.27. MySQL Notifier for Microsoft Windows Adding new - services - MySQL Notifier for Microsoft Windows Adding new services + Figure 2.37 MySQL Notifier Adding new services + MySQL Notifier Adding new services And instances: - Figure 2.28. MySQL Notifier for Microsoft Windows Adding new - instances - MySQL Notifier for Microsoft Windows Adding new instances + Figure 2.38 MySQL Notifier Adding new instances + MySQL Notifier Adding new instances Note - The Instances tab available since MySQL Notifier for Microsoft - Windows 1.1.0. + The Instances tab available since MySQL Notifier 1.1.0. -2.3.4.1. Remote monitoring set up and installation instructions +2.3.4.1 Remote monitoring set up and installation instructions - The MySQL Notifier for Microsoft Windows uses Windows Management - Instrumentation (WMI) to manage and monitor services in remote - computers running Windows XP or later. This guide explains how it + The MySQL Notifier uses Windows Management Instrumentation + (WMI) to manage and monitor services in remote computers + running Windows XP or later. This guide explains how it works, and how to set up your system to monitor remote MySQL instances. Note - Remote monitoring is available since MySQL Notifier for Microsoft - Windows 1.1.0. + Remote monitoring is available since MySQL Notifier 1.1.0. - In order to configure WMI, it is important to understand that the - underlying Distributed Component Object Model (DCOM) architecture - is doing the WMI work. Specifically, MySQL Notifier for Microsoft - Windows is using asynchronous notification queries on remote + In order to configure WMI, it is important to understand that + the underlying Distributed Component Object Model (DCOM) + architecture is doing the WMI work. Specifically, MySQL + Notifier is using asynchronous notification queries on remote Microsoft Windows hosts as .NET events. These events send an - asynchronous callback to the computer running the MySQL Notifier - for Microsoft Windows so it knows when a service status has - changed on the remote computer. Asynchronous notifications offer - the best performance compared to semi-synchronous notifications or + asynchronous callback to the computer running the MySQL + Notifier so it knows when a service status has changed on the + remote computer. Asynchronous notifications offer the best + performance compared to semisynchronous notifications or synchronous notifications that use timers. - Asynchronous notifications requires the remote computer to send a - callback to the client computer (thus opening a reverse - connection), so the Windows Firewall and DCOM settings must be - properly configured for the communication to function properly. - - Figure 2.29. MySQL Notifier for Microsoft Windows Distributed - Component Object Model (DCOM) - MySQL Notifier for Microsoft Windows Distributed Component Object - Model (DCOM) - - Most of the common errors thrown by asynchronous WMI notifications - are related to Windows Firewall blocking the communication, or to - DCOM / WMI settings not being set up properly. For a list of - common errors with solutions, see Section 2.3.4.1, "." - - The following steps are required to make WMI function. These steps - are divided between two machines. A single host computer that runs - MySQL Notifier for Microsoft Windows (Computer A), and multiple + Asynchronous notifications requires the remote computer to + send a callback to the client computer (thus opening a + reverse connection), so the Windows Firewall and DCOM + settings must be properly configured for the communication to + function properly. + + Figure 2.39 MySQL Notifier Distributed Component Object Model + (DCOM) + MySQL Notifier Distributed Component Object Model (DCOM) + + Most of the common errors thrown by asynchronous WMI + notifications are related to Windows Firewall blocking the + communication, or to DCOM / WMI settings not being set up + properly. For a list of common errors with solutions, see + Section 2.3.4.1, "." + + The following steps are required to make WMI function. These + steps are divided between two machines. A single host + computer that runs MySQL Notifier (Computer A), and multiple remote machines that are being monitored (Computer B). -Computer running MySQL Notifier for Microsoft Windows (Computer A) +Computer running MySQL Notifier (Computer A) - 1. Allow for remote administration by either editing the Group - Policy Editor, or using NETSH: + 1. Allow for remote administration by either editing the + Group Policy Editor, or using NETSH: Using the Group Policy Editor: - a. Click Start, click Run, type GPEDIT.MSC, and then click - OK. - b. Under the Local Computer Policy heading, double-click - Computer Configuration. + a. Click Start, click Run, type GPEDIT.MSC, and then + click OK. + b. Under the Local Computer Policy heading, + double-click Computer Configuration. c. Double-click Administrative Templates, then Network, Network Connections, and then Windows Firewall. d. If the computer is in the domain, then double-click - Domain Profile; otherwise, double-click Standard Profile. + Domain Profile; otherwise, double-click Standard + Profile. e. Click Windows Firewall: Allow inbound remote administration exception. - f. On the Action menu either select Edit, or double-click - the selection from the previous step. + f. On the Action menu either select Edit, or + double-click the selection from the previous step. g. Check the Enabled radio button, and then click OK. Using the NETSH command: - a. Open a command prompt window with Administrative rights - (you can right-click the Command Prompt icon and click - Run as Administrator). + a. Open a command prompt window with Administrative + rights (you can right-click the Command Prompt icon + and click Run as Administrator). b. Execute the following command: NETSH firewall set service RemoteAdmin enable + 2. Open the DCOM port TCP 135: - a. Open a command prompt window with Administrative rights - (you can right-click the Command Prompt icon and click - Run as Administrator) . + a. Open a command prompt window with Administrative + rights (you can right-click the Command Prompt icon + and click Run as Administrator) . b. Execute the following command: NETSH firewall add portopening protocol=tcp port=135 name=DCOM_TCP135 - 3. Add the client application which contains the sink for the - callback (MySqlNotifier.exe) to the Windows Firewall - Exceptions List (use either the Windows Firewall configuration - or NETSH): + + 3. Add the client application which contains the sink for + the callback (MySqlNotifier.exe) to the Windows Firewall + Exceptions List (use either the Windows Firewall + configuration or NETSH): Using the Windows Firewall configuration: a. In the Control Panel, double-click Windows Firewall. - b. In the Windows Firewall window's left panel, click Allow - a program or feature through Windows Firewall. - c. In the Allowed Programs window, click Change Settings. + b. In the Windows Firewall window's left panel, click + Allow a program or feature through Windows Firewall. + c. In the Allowed Programs window, click Change + Settings. d. If MySqlNotifier.exe is in the Allowed programs and - features list, make sure it is checked for the type of - networks the computer connects to (Private, Public or - both). + features list, make sure it is checked for the type + of networks the computer connects to (Private, + Public or both). e. If MySqlNotifier.exe is not in the list, click Allow another program.... - f. In the Add a Program window, select the MySqlNotifier.exe - if it exists in the Programs list, otherwise click - Browse... and go to the directory where MySqlNotifier.exe - was installed to select it, then click Add. - g. Make sure MySqlNotifier.exe is checked for the type of - networks the computer connects to (Private, Public or - both). + f. In the Add a Program window, select the + MySqlNotifier.exe if it exists in the Programs list, + otherwise click Browse... and go to the directory + where MySqlNotifier.exe was installed to select it, + then click Add. + g. Make sure MySqlNotifier.exe is checked for the type + of networks the computer connects to (Private, + Public or both). Using the NETSH command: - a. Open a command prompt window with Administrative rights - (you can right-click the Command Prompt icon and click - Run as Administrator). + a. Open a command prompt window with Administrative + rights (you can right-click the Command Prompt icon + and click Run as Administrator). b. Execute the following command, where you change "[YOUR_INSTALL_DIRECTORY]": -NETSH firewall add allowedprogram program=[YOUR_INSTALL_DIRECTORY]\My -SqlNotifier.exe name=MySqlNotifier +NETSH firewall add allowedprogram program=[YOUR_INSTALL_DIRECTORY]\MyS +qlNotifier.exe name=MySqlNotifier + 4. If Computer B is either a member of WORKGROUP or is in a - different domain that is untrusted by Computer A, then the - callback connection (Connection 2) is created as an Anonymous - connection. To grant Anonymous connections DCOM Remote Access - permissions: - a. Click Start, click Run, type DCOMCNFG, and then click OK. - b. In the Component Services dialog box, expand Component - Services, expand Computers, and then right-click My - Computer and click Properties. - c. In the My Computer Properties dialog box, click the COM - Security tab. + different domain that is untrusted by Computer A, then + the callback connection (Connection 2) is created as an + Anonymous connection. To grant Anonymous connections DCOM + Remote Access permissions: + a. Click Start, click Run, type DCOMCNFG, and then + click OK. + b. In the Component Services dialog box, expand + Component Services, expand Computers, and then + right-click My Computer and click Properties. + c. In the My Computer Properties dialog box, click the + COM Security tab. d. Under Access Permissions, click Edit Limits. - e. In the Access Permission dialog box, select ANONYMOUS - LOGON name in the Group or user names box. In the Allow - column under Permissions for User, select Remote Access, - and then click OK. + e. In the Access Permission dialog box, select + ANONYMOUS LOGON name in the Group or user names box. + In the Allow column under Permissions for User, + select Remote Access, and then click OK. Monitored Remote Computer (Computer B) - If the user account that is logged into the computer running the - MySQL Notifier for Microsoft Windows (Computer A) is a local - administrator on the remote computer (Computer B), such that the - same account is an administrator on Computer B, you can skip to - the "Allow for remote administration" step. - - Setting DCOM security to allow a non-administrator user to access - a computer remotely: - - 1. Grant "DCOM remote launch" and activation permissions for a - user or group: - a. Click Start, click Run, type DCOMCNFG, and then click OK. - b. In the Component Services dialog box, expand Component - Services, expand Computers, and then right-click My - Computer and click Properties. - c. In the My Computer Properties dialog box, click the COM - Security tab. + If the user account that is logged into the computer running + the MySQL Notifier (Computer A) is a local administrator on + the remote computer (Computer B), such that the same account + is an administrator on Computer B, you can skip to the "Allow + for remote administration" step. + + Setting DCOM security to allow a non-administrator user to + access a computer remotely: + + 1. Grant "DCOM remote launch" and activation permissions for + a user or group: + a. Click Start, click Run, type DCOMCNFG, and then + click OK. + b. In the Component Services dialog box, expand + Component Services, expand Computers, and then + right-click My Computer and click Properties. + c. In the My Computer Properties dialog box, click the + COM Security tab. d. Under Access Permissions, click Edit Limits. - e. In the Launch Permission dialog box, follow these steps - if your name or your group does not appear in the Groups - or user names list: + e. In the Launch Permission dialog box, follow these + steps if your name or your group does not appear in + the Groups or user names list: i. In the Launch Permission dialog box, click Add. - ii. In the Select Users, Computers, or Groups dialog - box, add your name and the group in the "Enter the - object names to select" box, and then click OK. - f. In the Launch Permission dialog box, select your user and - group in the Group or user names box. In the Allow column - under Permissions for User, select Remote Launch, select - Remote Activation, and then click OK. + ii. In the Select Users, Computers, or Groups + dialog box, add your name and the group in the + "Enter the object names to select" box, and + then click OK. + f. In the Launch Permission dialog box, select your + user and group in the Group or user names box. In + the Allow column under Permissions for User, select + Remote Launch, select Remote Activation, and then + click OK. Grant DCOM remote access permissions: - a. Click Start, click Run, type DCOMCNFG, and then click OK. - b. In the Component Services dialog box, expand Component - Services, expand Computers, and then right-click My - Computer and click Properties. - c. In the My Computer Properties dialog box, click the COM - Security tab. + a. Click Start, click Run, type DCOMCNFG, and then + click OK. + b. In the Component Services dialog box, expand + Component Services, expand Computers, and then + right-click My Computer and click Properties. + c. In the My Computer Properties dialog box, click the + COM Security tab. d. Under Access Permissions, click Edit Limits. - e. In the Access Permission dialog box, select ANONYMOUS - LOGON name in the Group or user names box. In the Allow - column under Permissions for User, select Remote Access, - and then click OK. + e. In the Access Permission dialog box, select + ANONYMOUS LOGON name in the Group or user names box. + In the Allow column under Permissions for User, + select Remote Access, and then click OK. 2. Allowing non-administrator users access to a specific WMI namespace: - a. In the Control Panel, double-click Administrative Tools. - b. In the Administrative Tools window, double-click Computer - Management. - c. In the Computer Management window, expand the Services - and Applications tree and double-click the WMI Control. - d. Right-click the WMI Control icon and select Properties. - e. In the WMI Control Properties window, click the Security - tab. + a. In the Control Panel, double-click Administrative + Tools. + b. In the Administrative Tools window, double-click + Computer Management. + c. In the Computer Management window, expand the + Services and Applications tree and double-click the + WMI Control. + d. Right-click the WMI Control icon and select + Properties. + e. In the WMI Control Properties window, click the + Security tab. f. In the Security tab, select the namespace and click Security. - g. Locate the appropriate account and check Remote Enable in - the Permissions list. + g. Locate the appropriate account and check Remote + Enable in the Permissions list. - 3. Allow for remote administration by either editing the Group - Policy Editor or using NETSH: + 3. Allow for remote administration by either editing the + Group Policy Editor or using NETSH: Using the Group Policy Editor: - a. Click Start, click Run, type GPEDIT.MSC, and then click - OK. - b. Under the Local Computer Policy heading, double-click - Computer Configuration. + a. Click Start, click Run, type GPEDIT.MSC, and then + click OK. + b. Under the Local Computer Policy heading, + double-click Computer Configuration. c. Double-click Administrative Templates, then Network, Network Connections, and then Windows Firewall. d. If the computer is in the domain, then double-click - Domain Profile; otherwise, double-click Standard Profile. + Domain Profile; otherwise, double-click Standard + Profile. e. Click Windows Firewall: Allow inbound remote administration exception. - f. On the Action menu either select Edit, or double-click - the selection from the previous step. + f. On the Action menu either select Edit, or + double-click the selection from the previous step. g. Check the Enabled radio button, and then click OK. Using the NETSH command: - a. Open a command prompt window with Administrative rights - (you can right-click the Command Prompt icon and click - Run as Administrator). + a. Open a command prompt window with Administrative + rights (you can right-click the Command Prompt icon + and click Run as Administrator). b. Execute the following command: NETSH firewall set service RemoteAdmin enable - 4. Now, be sure the user you are logging in with uses the Name - value and not the Full Name value: - a. In the Control Panel, double-click Administrative Tools. - b. In the Administrative Tools window, double-click Computer - Management. + + 4. Now, be sure the user you are logging in with uses the + Name value and not the Full Name value: + a. In the Control Panel, double-click Administrative + Tools. + b. In the Administrative Tools window, double-click + Computer Management. c. In the Computer Management window, expand the System Tools then Local Users and Groups. - d. Click the Users node, and on the right side panel locate - your user and make sure it uses the Name value to - connect, and not the Full Name value. - - 5. If the remote computer is running on Windows XP Professional, - make sure that remote logins are not being forcefully changed - to the guest account user (also known as ForceGuest), which is - enabled by default on computers that are not attached to a - domain. - a. Click Start, click Run, type SECPOL.MSC, and then click - OK. + d. Click the Users node, and on the right side panel + locate your user and make sure it uses the Name + value to connect, and not the Full Name value. + + 5. If the remote computer is running on Windows XP + Professional, make sure that remote logins are not being + forcefully changed to the guest account user (also known + as ForceGuest), which is enabled by default on computers + that are not attached to a domain. + a. Click Start, click Run, type SECPOL.MSC, and then + click OK. b. Under the Local Policies node, double-click Security Options. - c. Select Network Access: Sharing and security model for - local accounts and save. + c. Select Network Access: Sharing and security model + for local accounts and save. Common Errors * 0x80070005 - + DCOM Security was not configured properly (see Computer - B, the Setting DCOM security... step). + + DCOM Security was not configured properly (see + Computer B, the Setting DCOM security... step). - + The remote computer (Computer B) is a member of WORKGROUP - or is in a domain that is untrusted by the client - computer (Computer A) (see Computer A, the Grant - Anonymous connections DCOM Remote Access permissions - step). + + The remote computer (Computer B) is a member of + WORKGROUP or is in a domain that is untrusted by the + client computer (Computer A) (see Computer A, the + Grant Anonymous connections DCOM Remote Access + permissions step). * 0x8007000E - + The remote computer (Computer B) is a member of WORKGROUP - or is in a domain that is untrusted by the client - computer (Computer A) (see Computer A, the Grant - Anonymous connections DCOM Remote Access permissions - step). + + The remote computer (Computer B) is a member of + WORKGROUP or is in a domain that is untrusted by the + client computer (Computer A) (see Computer A, the + Grant Anonymous connections DCOM Remote Access + permissions step). * 0x80041003 - + Access to the remote WMI namespace was not configured - properly (see Computer B, the Allowing non-administrator - users access to a specific WMI namespace step). + + Access to the remote WMI namespace was not + configured properly (see Computer B, the Allowing + non-administrator users access to a specific WMI + namespace step). * 0x800706BA + The DCOM port is not open on the client computers - (Computer A) firewall. See the Open the DCOM port TCP 135 - step for Computer A. + (Computer A) firewall. See the Open the DCOM port + TCP 135 step for Computer A. - + The remote computer (Computer B) is inaccessible because - its network location is set to Public. Make sure you can - access it through the Windows Explorer. - -2.3.5. Installing MySQL on Microsoft Windows Using an MSI Package - - The MSI package is designed to install and configure MySQL in such - a way that you can immediately get started using MySQL. - - The MySQL Installation Wizard and MySQL Configuration Wizard are - available in the Complete install package, which is recommended - for most standard MySQL installations. Exceptions include users - who need to install multiple instances of MySQL on a single server - host and advanced users who want complete control of server - configuration. + + The remote computer (Computer B) is inaccessible + because its network location is set to Public. Make + sure you can access it through the Windows Explorer. + +2.3.5 Installing MySQL on Microsoft Windows Using an MSI Package + + The MSI package is designed to install and configure MySQL in + such a way that you can immediately get started using MySQL. + + The MySQL Installation Wizard and MySQL Configuration Wizard + are available in the Complete install package, which is + recommended for most standard MySQL installations. Exceptions + include users who need to install multiple instances of MySQL + on a single server host and advanced users who want complete + control of server configuration. * For information on installing using the GUI MSI installer - process, see Section 2.3.5.1, "Using the MySQL Installation - Wizard." + process, see Section 2.3.5.1, "Using the MySQL + Installation Wizard." - * For information on installing using the command line using the - MSI package, see Section 2.3.5.2, "Automating MySQL - Installation on Microsoft Windows Using the MSI Package." - - * If you have previously installed MySQL using the MSI package - and want to remove MySQL, see Section 2.3.5.3, "Removing MySQL - When Installed from the MSI Package." + * For information on installing using the command line + using the MSI package, see Section 2.3.5.2, "Automating + MySQL Installation on Microsoft Windows Using the MSI + Package." + + * If you have previously installed MySQL using the MSI + package and want to remove MySQL, see Section 2.3.5.3, + "Removing MySQL When Installed from the MSI Package." The workflow sequence for using the installer is shown in the figure below: - Figure 2.30. Installation Workflow for Windows Using MSI Installer + Figure 2.40 Installation Workflow for Windows Using MSI + Installer Installation Workflow for Windows using MSI Installer Note Microsoft Windows XP and later include a firewall which - specifically blocks ports. If you plan on using MySQL through a - network port then you should open and create an exception for this - port before performing the installation. To check and if necessary - add an exception to the firewall settings: + specifically blocks ports. If you plan on using MySQL through + a network port then you should open and create an exception + for this port before performing the installation. To check + and if necessary add an exception to the firewall settings: - 1. First ensure that you are logged in as an Administrator or a - user with Administrator privileges. + 1. First ensure that you are logged in as an Administrator + or a user with Administrator privileges. - 2. Go to the Control Panel, and double click the Windows Firewall - icon. + 2. Go to the Control Panel, and double click the Windows + Firewall icon. - 3. Choose the Allow a program through Windows Firewall option and - click the Add port button. + 3. Choose the Allow a program through Windows Firewall + option and click the Add port button. - 4. Enter MySQL into the Name text box and 3306 (or the port of - your choice) into the Port number text box. + 4. Enter MySQL into the Name text box and 3306 (or the port + of your choice) into the Port number text box. - 5. Also ensure that the TCP protocol radio button is selected. + 5. Also ensure that the TCP protocol radio button is + selected. - 6. If you wish, you can also limit access to the MySQL server by - choosing the Change scope button. + 6. If you wish, you can also limit access to the MySQL + server by choosing the Change scope button. 7. Confirm your choices by clicking the OK button. Additionally, when running the MySQL Installation Wizard on - Windows Vista or newer, ensure that you are logged in as a user - with administrative rights. + Windows Vista or newer, ensure that you are logged in as a + user with administrative rights. Note - When using Windows Vista or newer, you may want to disable User - Account Control (UAC) before performing the installation. If you - do not do so, then MySQL may be identified as a security risk, - which will mean that you need to enable MySQL. You can disable the - security checking by following these instructions: + When using Windows Vista or newer, you may want to disable + User Account Control (UAC) before performing the + installation. If you do not do so, then MySQL may be + identified as a security risk, which will mean that you need + to enable MySQL. You can disable the security checking by + following these instructions: 1. Open Control Panel. @@ -2090,199 +2393,213 @@ 3. Click the Got to the main User Accounts page link. 4. Click on Turn User Account Control on or off. You may be - prompted to provide permission to change this setting. Click - Continue. + prompted to provide permission to change this setting. + Click Continue. - 5. Deselect or uncheck the check box next to Use User Account - Control (UAC) to help protect your computer. Click OK to save - the setting. - - You will need to restart to complete the process. Click Restart - Now to reboot the machine and apply the changes. You can then - follow the instructions below for installing Windows. - -2.3.5.1. Using the MySQL Installation Wizard - - MySQL Installation Wizard is an installer for the MySQL server - that uses the latest installer technologies for Microsoft Windows. - The MySQL Installation Wizard, in combination with the MySQL - Configuration Wizard, enables a user to install and configure a - MySQL server that is ready for use immediately after installation. - - The MySQL Installation Wizard is the standard installer for all - MySQL server distributions, version 4.1.5 and higher. Users of - previous versions of MySQL need to shut down and remove their - existing MySQL installations manually before installing MySQL with - the MySQL Installation Wizard. See Section 2.3.5.1.6, "Upgrading - MySQL with the Installation Wizard," for more information on - upgrading from a previous version. + 5. Deselect or uncheck the check box next to Use User + Account Control (UAC) to help protect your computer. + Click OK to save the setting. + + You will need to restart to complete the process. Click + Restart Now to reboot the machine and apply the changes. You + can then follow the instructions below for installing + Windows. + +2.3.5.1 Using the MySQL Installation Wizard + + MySQL Installation Wizard is an installer for the MySQL + server that uses the latest installer technologies for + Microsoft Windows. The MySQL Installation Wizard, in + combination with the MySQL Configuration Wizard, enables a + user to install and configure a MySQL server that is ready + for use immediately after installation. + + The MySQL Installation Wizard is the standard installer for + all MySQL server distributions, version 4.1.5 and higher. + Users of previous versions of MySQL need to shut down and + remove their existing MySQL installations manually before + installing MySQL with the MySQL Installation Wizard. See + Section 2.3.5.1.6, "Upgrading MySQL with the Installation + Wizard," for more information on upgrading from a previous + version. Microsoft has included an improved version of their Microsoft - Windows Installer (MSI) in the recent versions of Windows. MSI has - become the de-facto standard for application installations on - Windows 2000, Windows XP, and Windows Server 2003. The MySQL - Installation Wizard makes use of this technology to provide a - smoother and more flexible installation process. + Windows Installer (MSI) in the recent versions of Windows. + MSI has become the de-facto standard for application + installations on Windows 2000, Windows XP, and Windows Server + 2003. The MySQL Installation Wizard makes use of this + technology to provide a smoother and more flexible + installation process. The Microsoft Windows Installer Engine was updated with the - release of Windows XP; those using a previous version of Windows - can reference this Microsoft Knowledge Base article - (http://support.microsoft.com/default.aspx?scid=kb;EN-US;292539) - for information on upgrading to the latest version of the Windows - Installer Engine. - - In addition, Microsoft has introduced the WiX (Windows Installer - XML) toolkit recently. This is the first highly acknowledged Open - Source project from Microsoft. We have switched to WiX because it - is an Open Source project and it enables us to handle the complete - Windows installation process in a flexible manner using scripts. - - Improving the MySQL Installation Wizard depends on the support and - feedback of users like you. If you find that the MySQL - Installation Wizard is lacking some feature important to you, or - if you discover a bug, please report it in our bugs database using - the instructions given in Section 1.7, "How to Report Bugs or - Problems." + release of Windows XP; those using a previous version of + Windows can reference this Microsoft Knowledge Base article + (http://support.microsoft.com/default.aspx?scid=kb;EN-US;2925 + 39) for information on upgrading to the latest version of the + Windows Installer Engine. + + In addition, Microsoft has introduced the WiX (Windows + Installer XML) toolkit recently. This is the first highly + acknowledged Open Source project from Microsoft. We have + switched to WiX because it is an Open Source project and it + enables us to handle the complete Windows installation + process in a flexible manner using scripts. + + Improving the MySQL Installation Wizard depends on the + support and feedback of users like you. If you find that the + MySQL Installation Wizard is lacking some feature important + to you, or if you discover a bug, please report it in our + bugs database using the instructions given in Section 1.7, + "How to Report Bugs or Problems." -2.3.5.1.1. Downloading and Starting the MySQL Installation Wizard +2.3.5.1.1 Downloading and Starting the MySQL Installation Wizard The MySQL installation packages can be downloaded from - http://dev.mysql.com/downloads/. If the package you download is - contained within a Zip archive, you need to extract the archive - first. - Note - - If you are installing on Windows Vista or newer, it is best to - open a network port before beginning the installation. To do this, - first ensure that you are logged in as an Administrator, go to the - Control Panel, and double-click the Windows Firewall icon. Choose - the Allow a program through Windows Firewall option and click the - Add port button. Enter MySQL into the Name text box and 3306 (or - the port of your choice) into the Port number text box. Also - ensure that the TCP protocol radio button is selected. If you - wish, you can also limit access to the MySQL server by choosing - the Change scope button. Confirm your choices by clicking the OK - button. If you do not open a port prior to installation, you - cannot configure the MySQL server immediately after installation. + http://dev.mysql.com/downloads/. If the package you download + is contained within a Zip archive, you need to extract the + archive first. + Note + + If you are installing on Windows Vista or newer, it is best + to open a network port before beginning the installation. To + do this, first ensure that you are logged in as an + Administrator, go to the Control Panel, and double-click the + Windows Firewall icon. Choose the Allow a program through + Windows Firewall option and click the Add port button. Enter + MySQL into the Name text box and 3306 (or the port of your + choice) into the Port number text box. Also ensure that the + TCP protocol radio button is selected. If you wish, you can + also limit access to the MySQL server by choosing the Change + scope button. Confirm your choices by clicking the OK button. + If you do not open a port prior to installation, you cannot + configure the MySQL server immediately after installation. Additionally, when running the MySQL Installation Wizard on - Windows Vista or newer, ensure that you are logged in as a user - with administrative rights. + Windows Vista or newer, ensure that you are logged in as a + user with administrative rights. - The process for starting the wizard depends on the contents of the - installation package you download. If there is a setup.exe file - present, double-click it to start the installation process. If - there is an .msi file present, double-click it to start the - installation process. - -2.3.5.1.2. Choosing an Install Type - - There are three installation types available: Typical, Complete, - and Custom. + The process for starting the wizard depends on the contents + of the installation package you download. If there is a + setup.exe file present, double-click it to start the + installation process. If there is an .msi file present, + double-click it to start the installation process. + +2.3.5.1.2 Choosing an Install Type + + There are three installation types available: Typical, + Complete, and Custom. + + The Typical installation type installs the MySQL server, the + mysql command-line client, and the command-line utilities. + The command-line clients and utilities include mysqldump, + myisamchk, and several other tools to help you manage the + MySQL server. - The Typical installation type installs the MySQL server, the mysql - command-line client, and the command-line utilities. The - command-line clients and utilities include mysqldump, myisamchk, - and several other tools to help you manage the MySQL server. - - The Complete installation type installs all components included in - the installation package. The full installation package includes - components such as the embedded server library, the benchmark - suite, support scripts, and documentation. - - The Custom installation type gives you complete control over which - packages you wish to install and the installation path that is - used. See Section 2.3.5.1.3, "The Custom Install Dialog," for more - information on performing a custom install. - - If you choose the Typical or Complete installation types and click - the Next button, you advance to the confirmation screen to verify - your choices and begin the installation. If you choose the Custom - installation type and click the Next button, you advance to the - custom installation dialog, described in Section 2.3.5.1.3, "The - Custom Install Dialog." + The Complete installation type installs all components + included in the installation package. The full installation + package includes components such as the embedded server + library, the benchmark suite, support scripts, and + documentation. + + The Custom installation type gives you complete control over + which packages you wish to install and the installation path + that is used. See Section 2.3.5.1.3, "The Custom Install + Dialog," for more information on performing a custom install. + + If you choose the Typical or Complete installation types and + click the Next button, you advance to the confirmation screen + to verify your choices and begin the installation. If you + choose the Custom installation type and click the Next + button, you advance to the custom installation dialog, + described in Section 2.3.5.1.3, "The Custom Install Dialog." -2.3.5.1.3. The Custom Install Dialog +2.3.5.1.3 The Custom Install Dialog If you wish to change the installation path or the specific - components that are installed by the MySQL Installation Wizard, - choose the Custom installation type. + components that are installed by the MySQL Installation + Wizard, choose the Custom installation type. - A tree view on the left side of the custom install dialog lists - all available components. Components that are not installed have a - red X icon; components that are installed have a gray icon. To - change whether a component is installed, click that component's - icon and choose a new option from the drop-down list that appears. + A tree view on the left side of the custom install dialog + lists all available components. Components that are not + installed have a red X icon; components that are installed + have a gray icon. To change whether a component is installed, + click that component's icon and choose a new option from the + drop-down list that appears. You can change the default installation path by clicking the - Change... button to the right of the displayed installation path. + Change... button to the right of the displayed installation + path. - After choosing your installation components and installation path, - click the Next button to advance to the confirmation dialog. - -2.3.5.1.4. The Confirmation Dialog - - Once you choose an installation type and optionally choose your - installation components, you advance to the confirmation dialog. - Your installation type and installation path are displayed for you - to review. - - To install MySQL if you are satisfied with your settings, click - the Install button. To change your settings, click the Back - button. To exit the MySQL Installation Wizard without installing - MySQL, click the Cancel button. + After choosing your installation components and installation + path, click the Next button to advance to the confirmation + dialog. + +2.3.5.1.4 The Confirmation Dialog + + Once you choose an installation type and optionally choose + your installation components, you advance to the confirmation + dialog. Your installation type and installation path are + displayed for you to review. + + To install MySQL if you are satisfied with your settings, + click the Install button. To change your settings, click the + Back button. To exit the MySQL Installation Wizard without + installing MySQL, click the Cancel button. The final screen of the installer provides a summary of the installation and gives you the option to launch the MySQL - Configuration Wizard, which you can use to create a configuration - file, install the MySQL service, and configure security settings. - -2.3.5.1.5. Changes Made by MySQL Installation Wizard - - Once you click the Install button, the MySQL Installation Wizard - begins the installation process and makes certain changes to your - system which are described in the sections that follow. + Configuration Wizard, which you can use to create a + configuration file, install the MySQL service, and configure + security settings. + +2.3.5.1.5 Changes Made by MySQL Installation Wizard + + Once you click the Install button, the MySQL Installation + Wizard begins the installation process and makes certain + changes to your system which are described in the sections + that follow. Changes to the Registry - The MySQL Installation Wizard creates one Windows registry key in - a typical install situation, located in + The MySQL Installation Wizard creates one Windows registry + key in a typical install situation, located in HKEY_LOCAL_MACHINE\SOFTWARE\MySQL AB. - The MySQL Installation Wizard creates a key named after the major - version of the server that is being installed, such as MySQL - Server 5.5. It contains two string values, Location and Version. - The Location string contains the path to the installation - directory. In a default installation it contains C:\Program - Files\MySQL\MySQL Server 5.5\. The Version string contains the - release number. For example, for an installation of MySQL Server - 5.5.36, the key contains a value of 5.5.36. - - These registry keys are used to help external tools identify the - installed location of the MySQL server, preventing a complete scan - of the hard-disk to determine the installation path of the MySQL - server. The registry keys are not required to run the server, and - if you install MySQL using the noinstall Zip archive, the registry - keys are not created. + The MySQL Installation Wizard creates a key named after the + major version of the server that is being installed, such as + MySQL Server 5.5. It contains two string values, Location and + Version. The Location string contains the path to the + installation directory. In a default installation it contains + C:\Program Files\MySQL\MySQL Server 5.5\. The Version string + contains the release number. For example, for an installation + of MySQL Server 5.5.44, the key contains a value of 5.5.44. + + These registry keys are used to help external tools identify + the installed location of the MySQL server, preventing a + complete scan of the hard-disk to determine the installation + path of the MySQL server. The registry keys are not required + to run the server, and if you install MySQL using the + noinstall Zip archive, the registry keys are not created. Changes to the Start Menu - The MySQL Installation Wizard creates a new entry in the Windows - Start menu under a common MySQL menu heading named after the major - version of MySQL that you have installed. For example, if you - install MySQL 5.5, the MySQL Installation Wizard creates a MySQL - Server 5.5 section in the Start menu. + The MySQL Installation Wizard creates a new entry in the + Windows Start menu under a common MySQL menu heading named + after the major version of MySQL that you have installed. For + example, if you install MySQL 5.5, the MySQL Installation + Wizard creates a MySQL Server 5.5 section in the Start menu. The following entries are created within the new Start menu section: - * MySQL Command-Line Client: This is a shortcut to the mysql - command-line client and is configured to connect as the root - user. The shortcut prompts for a root user password when you - connect. - - * MySQL Server Instance Config Wizard: This is a shortcut to the - MySQL Configuration Wizard. Use this shortcut to configure a - newly installed server, or to reconfigure an existing server. + * MySQL Command-Line Client: This is a shortcut to the + mysql command-line client and is configured to connect as + the root user. The shortcut prompts for a root user + password when you connect. + + * MySQL Server Instance Config Wizard: This is a shortcut + to the MySQL Configuration Wizard. Use this shortcut to + configure a newly installed server, or to reconfigure an + existing server. * MySQL Documentation: This is a link to the MySQL server documentation that is stored locally in the MySQL server @@ -2290,118 +2607,122 @@ Changes to the File System - The MySQL Installation Wizard by default installs the MySQL 5.5 - server to C:\Program Files\MySQL\MySQL Server 5.5, where Program - Files is the default location for applications in your system, and - 5.5 is the major version of your MySQL server. This is the - recommended location for the MySQL server, replacing the former - default location C:\mysql. + The MySQL Installation Wizard by default installs the MySQL + 5.5 server to C:\Program Files\MySQL\MySQL Server 5.5, where + Program Files is the default location for applications in + your system, and 5.5 is the major version of your MySQL + server. This is the recommended location for the MySQL + server, replacing the former default location C:\mysql. By default, all MySQL applications are stored in a common - directory at C:\Program Files\MySQL, where Program Files is the - default location for applications in your Windows installation. A - typical MySQL installation on a developer machine might look like - this: + directory at C:\Program Files\MySQL, where Program Files is + the default location for applications in your Windows + installation. A typical MySQL installation on a developer + machine might look like this: C:\Program Files\MySQL\MySQL Server 5.5 C:\Program Files\MySQL\MySQL Workbench 5.1 OSS - This approach makes it easier to manage and maintain all MySQL - applications installed on a particular system. + This approach makes it easier to manage and maintain all + MySQL applications installed on a particular system. The default location of the data directory is the AppData directory configured for the user that installed the MySQL application. -2.3.5.1.6. Upgrading MySQL with the Installation Wizard +2.3.5.1.6 Upgrading MySQL with the Installation Wizard The MySQL Installation Wizard can perform server upgrades - automatically using the upgrade capabilities of MSI. That means - you do not need to remove a previous installation manually before - installing a new release. The installer automatically shuts down - and removes the previous MySQL service before installing the new - version. + automatically using the upgrade capabilities of MSI. That + means you do not need to remove a previous installation + manually before installing a new release. The installer + automatically shuts down and removes the previous MySQL + service before installing the new version. Automatic upgrades are available only when upgrading between - installations that have the same major and minor version numbers. - For example, you can upgrade automatically from MySQL 5.5.5 to - MySQL 5.5.6, but not from MySQL 5.1 to MySQL 5.5. + installations that have the same major and minor version + numbers. For example, you can upgrade automatically from + MySQL 5.5.5 to MySQL 5.5.6, but not from MySQL 5.1 to MySQL + 5.5. See Section 2.3.9, "Upgrading MySQL on Windows." -2.3.5.2. Automating MySQL Installation on Microsoft Windows Using the -MSI Package +2.3.5.2 Automating MySQL Installation on Microsoft Windows Using +the MSI Package The Microsoft Installer (MSI) supports a both a quiet and a passive mode that can be used to install MySQL automatically - without requiring intervention. You can use this either in scripts - to automatically install MySQL or through a terminal connection - such as Telnet where you do not have access to the standard - Windows user interface. The MSI packages can also be used in - combination with Microsoft's Group Policy system (part of Windows - Server 2003 and Windows Server 2008) to install MySQL across - multiple machines. - - To install MySQL from one of the MSI packages automatically from - the command line (or within a script), you need to use the - msiexec.exe tool. For example, to perform a quiet installation - (which shows no dialog boxes or progress): -shell> msiexec /i mysql-5.5.36.msi /quiet - - The /i indicates that you want to perform an installation. The - /quiet option indicates that you want no interactive elements. - - To provide a dialog box showing the progress during installation, - and the dialog boxes providing information on the installation and - registration of MySQL, use /passive mode instead of /quiet: -shell> msiexec /i mysql-5.5.36.msi /passive - - Regardless of the mode of the installation, installing the package - in this manner performs a 'Typical' installation, and installs the - default components into the standard location. + without requiring intervention. You can use this either in + scripts to automatically install MySQL or through a terminal + connection such as Telnet where you do not have access to the + standard Windows user interface. The MSI packages can also be + used in combination with Microsoft's Group Policy system + (part of Windows Server 2003 and Windows Server 2008) to + install MySQL across multiple machines. + + To install MySQL from one of the MSI packages automatically + from the command line (or within a script), you need to use + the msiexec.exe tool. For example, to perform a quiet + installation (which shows no dialog boxes or progress): +shell> msiexec /i mysql-5.5.44.msi /quiet + + The /i indicates that you want to perform an installation. + The /quiet option indicates that you want no interactive + elements. + + To provide a dialog box showing the progress during + installation, and the dialog boxes providing information on + the installation and registration of MySQL, use /passive mode + instead of /quiet: +shell> msiexec /i mysql-5.5.44.msi /passive + + Regardless of the mode of the installation, installing the + package in this manner performs a 'Typical' installation, and + installs the default components into the standard location. You can also use this method to uninstall MySQL by using the /uninstall or /x options: -shell> msiexec /x mysql-5.5.36.msi /uninstall +shell> msiexec /x mysql-5.5.44.msi /uninstall - To install MySQL and configure a MySQL instance from the command - line, see Section 2.3.6.13, "MySQL Server Instance Config Wizard: - Creating an Instance from the Command Line." + To install MySQL and configure a MySQL instance from the + command line, see Section 2.3.6.13, "MySQL Server Instance + Config Wizard: Creating an Instance from the Command Line." For information on using MSI packages to install software - automatically using Group Policy, see How to use Group Policy to - remotely install software in Windows Server 2003 + automatically using Group Policy, see How to use Group Policy + to remotely install software in Windows Server 2003 (http://support.microsoft.com/kb/816102). -2.3.5.3. Removing MySQL When Installed from the MSI Package +2.3.5.3 Removing MySQL When Installed from the MSI Package - To uninstall a MySQL where you have used the MSI packages, you - must use the Add/Remove Programs tool within Control Panel. To do - this: + To uninstall a MySQL where you have used the MSI packages, + you must use the Add/Remove Programs tool within Control + Panel. To do this: 1. Right-click the start menu and choose Control Panel. - 2. If the Control Panel is set to category mode (you will see - Pick a category at the top of the Control Panel window), - double-click Add or Remove Programs. If the Control is set to - classic mode, double-click the Add or Remove Programs icon. - - 3. Find MySQL in the list of installed software. MySQL Server is - installed against major version numbers (MySQL 5.1, MySQL 5.5, - etc.). Select the version that you want to remove and click - Remove. + 2. If the Control Panel is set to category mode (you will + see Pick a category at the top of the Control Panel + window), double-click Add or Remove Programs. If the + Control is set to classic mode, double-click the Add or + Remove Programs icon. + + 3. Find MySQL in the list of installed software. MySQL + Server is installed against major version numbers (MySQL + 5.1, MySQL 5.5, etc.). Select the version that you want + to remove and click Remove. 4. You will be prompted to confirm the removal. Click Yes to remove MySQL. When MySQL is removed using this method, only the installed - components are removed. Any database information (including the - tables and data), import or export files, log files, and binary - logs produced during execution are kept in their configured - location. - - If you try to install MySQL again the information will be retained - and you will be prompted to enter the password configured with the - original installation. + components are removed. Any database information (including + the tables and data), import or export files, log files, and + binary logs produced during execution are kept in their + configured location. + + If you try to install MySQL again the information will be + retained and you will be prompted to enter the password + configured with the original installation. If you want to delete MySQL completely: @@ -2413,86 +2734,92 @@ * On Windows 7 and Windows Server 2008, the default data directory location is C:\ProgramData\Mysql. Note - The C:\ProgramData directory is hidden by default. You must - change your folder options to view the hidden file. Choose - Organize, Folder and search options, Show hidden folders. - -2.3.6. MySQL Server Instance Configuration Wizard - - The MySQL Server Instance Configuration Wizard helps automate the - process of configuring your server. It creates a custom MySQL - configuration file (my.ini or my.cnf) by asking you a series of - questions and then applying your responses to a template to - generate the configuration file that is tuned to your - installation. - - The MySQL Server Instance Configuration Wizard is included with - the MySQL 5.5 server. The MySQL Server Instance Configuration - Wizard is only available for Windows. - -2.3.6.1. Starting the MySQL Server Instance Configuration Wizard - - The MySQL Server Instance Configuration Wizard is normally started - as part of the installation process. You should only need to run - the MySQL Server Instance Configuration Wizard again when you need - to change the configuration parameters of your server. + The C:\ProgramData directory is hidden by default. You + must change your folder options to view the hidden file. + Choose Organize, Folder and search options, Show hidden + folders. + +2.3.6 MySQL Server Instance Configuration Wizard + + The MySQL Server Instance Configuration Wizard helps automate + the process of configuring your server. It creates a custom + MySQL configuration file (my.ini or my.cnf) by asking you a + series of questions and then applying your responses to a + template to generate the configuration file that is tuned to + your installation. + + The MySQL Server Instance Configuration Wizard is included + with the MySQL 5.5 server. The MySQL Server Instance + Configuration Wizard is only available for Windows. + +2.3.6.1 Starting the MySQL Server Instance Configuration Wizard + + The MySQL Server Instance Configuration Wizard is normally + started as part of the installation process. You should only + need to run the MySQL Server Instance Configuration Wizard + again when you need to change the configuration parameters of + your server. If you chose not to open a port prior to installing MySQL on - Windows Vista or newer, you can choose to use the MySQL Server - Configuration Wizard after installation. However, you must open a - port in the Windows Firewall. To do this see the instructions - given in Section 2.3.5.1.1, "Downloading and Starting the MySQL - Installation Wizard." Rather than opening a port, you also have - the option of adding MySQL as a program that bypasses the Windows - Firewall. One or the other option is sufficient---you need not do - both. Additionally, when running the MySQL Server Configuration - Wizard on Windows Vista or newer, ensure that you are logged in as - a user with administrative rights. + Windows Vista or newer, you can choose to use the MySQL + Server Configuration Wizard after installation. However, you + must open a port in the Windows Firewall. To do this see the + instructions given in Section 2.3.5.1.1, "Downloading and + Starting the MySQL Installation Wizard." Rather than opening + a port, you also have the option of adding MySQL as a program + that bypasses the Windows Firewall. One or the other option + is sufficient---you need not do both. Additionally, when + running the MySQL Server Configuration Wizard on Windows + Vista or newer, ensure that you are logged in as a user with + administrative rights. MySQL Server Instance Configuration Wizard You can launch the MySQL Configuration Wizard by clicking the - MySQL Server Instance Config Wizard entry in the MySQL section of - the Windows Start menu. - - Alternatively, you can navigate to the bin directory of your MySQL - installation and launch the MySQLInstanceConfig.exe file directly. - - The MySQL Server Instance Configuration Wizard places the my.ini - file in the installation directory for the MySQL server. This - helps associate configuration files with particular server - instances. + MySQL Server Instance Config Wizard entry in the MySQL + section of the Windows Start menu. - To ensure that the MySQL server knows where to look for the my.ini - file, an argument similar to this is passed to the MySQL server as - part of the service installation: + Alternatively, you can navigate to the bin directory of your + MySQL installation and launch the MySQLInstanceConfig.exe + file directly. + + The MySQL Server Instance Configuration Wizard places the + my.ini file in the installation directory for the MySQL + server. This helps associate configuration files with + particular server instances. + + To ensure that the MySQL server knows where to look for the + my.ini file, an argument similar to this is passed to the + MySQL server as part of the service installation: --defaults-file="C:\Program Files\MySQL\MySQL Server 5.5\my.ini" - Here, C:\Program Files\MySQL\MySQL Server 5.5 is replaced with the - installation path to the MySQL Server. The --defaults-file option - instructs the MySQL server to read the specified file for - configuration options when it starts. - - Apart from making changes to the my.ini file by running the MySQL - Server Instance Configuration Wizard again, you can modify it by - opening it with a text editor and making any necessary changes. - You can also modify the server configuration with the - http://www.mysql.com/products/administrator/ utility. For more - information about server configuration, see Section 5.1.3, "Server - Command Options." + Here, C:\Program Files\MySQL\MySQL Server 5.5 is replaced + with the installation path to the MySQL Server. The + --defaults-file option instructs the MySQL server to read the + specified file for configuration options when it starts. + + Apart from making changes to the my.ini file by running the + MySQL Server Instance Configuration Wizard again, you can + modify it by opening it with a text editor and making any + necessary changes. You can also modify the server + configuration with the + http://www.mysql.com/products/administrator/ utility. For + more information about server configuration, see Section + 5.1.3, "Server Command Options." MySQL clients and utilities such as the mysql and mysqldump command-line clients are not able to locate the my.ini file - located in the server installation directory. To configure the - client and utility applications, create a new my.ini file in the - Windows installation directory (for example, C:\WINDOWS). - - Under Windows Server 2003, Windows Server 2000, Windows XP, and - Windows Vista, MySQL Server Instance Configuration Wizard will - configure MySQL to work as a Windows service. To start and stop - MySQL you use the Services application that is supplied as part of - the Windows Administrator Tools. + located in the server installation directory. To configure + the client and utility applications, create a new my.ini file + in the Windows installation directory (for example, + C:\WINDOWS). + + Under Windows Server 2003, Windows Server 2000, Windows XP, + and Windows Vista, MySQL Server Instance Configuration Wizard + will configure MySQL to work as a Windows service. To start + and stop MySQL you use the Services application that is + supplied as part of the Windows Administrator Tools. -2.3.6.2. Choosing a Maintenance Option +2.3.6.2 Choosing a Maintenance Option If the MySQL Server Instance Configuration Wizard detects an existing configuration file, you have the option of either @@ -2502,118 +2829,119 @@ To reconfigure an existing server, choose the Re-configure Instance option and click the Next button. Any existing - configuration file is not overwritten, but renamed (within the - same directory) using a timestamp (Windows) or sequential number - (Linux). To remove the existing server instance, choose the Remove - Instance option and click the Next button. + configuration file is not overwritten, but renamed (within + the same directory) using a timestamp (Windows) or sequential + number (Linux). To remove the existing server instance, + choose the Remove Instance option and click the Next button. If you choose the Remove Instance option, you advance to a - confirmation window. Click the Execute button. The MySQL Server - Configuration Wizard stops and removes the MySQL service, and then - deletes the configuration file. The server installation and its - data folder are not removed. - - If you choose the Re-configure Instance option, you advance to the - Configuration Type dialog where you can choose the type of - installation that you wish to configure. - -2.3.6.3. Choosing a Configuration Type - - When you start the MySQL Server Instance Configuration Wizard for - a new MySQL installation, or choose the Re-configure Instance - option for an existing installation, you advance to the - Configuration Type dialog. - MySQL Server Instance Configuration Wizard: Configuration Type + confirmation window. Click the Execute button. The MySQL + Server Configuration Wizard stops and removes the MySQL + service, and then deletes the configuration file. The server + installation and its data folder are not removed. + + If you choose the Re-configure Instance option, you advance + to the Configuration Type dialog where you can choose the + type of installation that you wish to configure. + +2.3.6.3 Choosing a Configuration Type + + When you start the MySQL Server Instance Configuration Wizard + for a new MySQL installation, or choose the Re-configure + Instance option for an existing installation, you advance to + the Configuration Type dialog. + MySQL Server Instance Configuration Wizard: Configuration + Type There are two configuration types available: Detailed Configuration and Standard Configuration. The Standard - Configuration option is intended for new users who want to get - started with MySQL quickly without having to make many decisions - about server configuration. The Detailed Configuration option is - intended for advanced users who want more fine-grained control - over server configuration. + Configuration option is intended for new users who want to + get started with MySQL quickly without having to make many + decisions about server configuration. The Detailed + Configuration option is intended for advanced users who want + more fine-grained control over server configuration. If you are new to MySQL and need a server configured as a - single-user developer machine, the Standard Configuration should - suit your needs. Choosing the Standard Configuration option causes - the MySQL Configuration Wizard to set all configuration options - automatically with the exception of Service Options and Security - Options. - - The Standard Configuration sets options that may be incompatible - with systems where there are existing MySQL installations. If you - have an existing MySQL installation on your system in addition to - the installation you wish to configure, the Detailed Configuration - option is recommended. + single-user developer machine, the Standard Configuration + should suit your needs. Choosing the Standard Configuration + option causes the MySQL Configuration Wizard to set all + configuration options automatically with the exception of + Service Options and Security Options. + + The Standard Configuration sets options that may be + incompatible with systems where there are existing MySQL + installations. If you have an existing MySQL installation on + your system in addition to the installation you wish to + configure, the Detailed Configuration option is recommended. To complete the Standard Configuration, please refer to the sections on Service Options and Security Options in Section - 2.3.6.10, "The Service Options Dialog," and Section 2.3.6.11, "The - Security Options Dialog," respectively. + 2.3.6.10, "The Service Options Dialog," and Section 2.3.6.11, + "The Security Options Dialog," respectively. -2.3.6.4. The Server Type Dialog +2.3.6.4 The Server Type Dialog - There are three different server types available to choose from. - The server type that you choose affects the decisions that the - MySQL Server Instance Configuration Wizard makes with regard to - memory, disk, and processor usage. + There are three different server types available to choose + from. The server type that you choose affects the decisions + that the MySQL Server Instance Configuration Wizard makes + with regard to memory, disk, and processor usage. MySQL Server Instance Configuration Wizard: Server Type - * Developer Machine: Choose this option for a typical desktop - workstation where MySQL is intended only for personal use. It - is assumed that many other desktop applications are running. - The MySQL server is configured to use minimal system - resources. - - * Server Machine: Choose this option for a server machine where - the MySQL server is running alongside other server - applications such as FTP, email, and Web servers. The MySQL - server is configured to use a moderate portion of the system - resources. + * Developer Machine: Choose this option for a typical + desktop workstation where MySQL is intended only for + personal use. It is assumed that many other desktop + applications are running. The MySQL server is configured + to use minimal system resources. + + * Server Machine: Choose this option for a server machine + where the MySQL server is running alongside other server + applications such as FTP, email, and Web servers. The + MySQL server is configured to use a moderate portion of + the system resources. * Dedicated MySQL Server Machine: Choose this option for a - server machine that is intended to run only the MySQL server. - It is assumed that no other applications are running. The - MySQL server is configured to use all available system - resources. + server machine that is intended to run only the MySQL + server. It is assumed that no other applications are + running. The MySQL server is configured to use all + available system resources. Note - By selecting one of the preconfigured configurations, the values - and settings of various options in your my.cnf or my.ini will be - altered accordingly. The default values and options as described - in the reference manual may therefore be different to the options - and values that were created during the execution of the - configuration wizard. + By selecting one of the preconfigured configurations, the + values and settings of various options in your my.cnf or + my.ini will be altered accordingly. The default values and + options as described in the reference manual may therefore be + different to the options and values that were created during + the execution of the configuration wizard. -2.3.6.5. The Database Usage Dialog +2.3.6.5 The Database Usage Dialog The Database Usage dialog enables you to indicate the storage - engines that you expect to use when creating MySQL tables. The - option you choose determines whether the InnoDB storage engine is - available and what percentage of the server resources are - available to InnoDB. + engines that you expect to use when creating MySQL tables. + The option you choose determines whether the InnoDB storage + engine is available and what percentage of the server + resources are available to InnoDB. MySQL Server Instance Configuration Wizard: Usage Dialog - * Multifunctional Database: This option enables both the InnoDB - and MyISAM storage engines and divides resources evenly - between the two. This option is recommended for users who use - both storage engines on a regular basis. + * Multifunctional Database: This option enables both the + InnoDB and MyISAM storage engines and divides resources + evenly between the two. This option is recommended for + users who use both storage engines on a regular basis. * Transactional Database Only: This option enables both the - InnoDB and MyISAM storage engines, but dedicates most server - resources to the InnoDB storage engine. This option is - recommended for users who use InnoDB almost exclusively and - make only minimal use of MyISAM. + InnoDB and MyISAM storage engines, but dedicates most + server resources to the InnoDB storage engine. This + option is recommended for users who use InnoDB almost + exclusively and make only minimal use of MyISAM. * Non-Transactional Database Only: This option disables the InnoDB storage engine completely and dedicates all server resources to the MyISAM storage engine. This option is recommended for users who do not use InnoDB. - The Configuration Wizard uses a template to generate the server - configuration file. The Database Usage dialog sets one of the - following option strings: + The Configuration Wizard uses a template to generate the + server configuration file. The Database Usage dialog sets one + of the following option strings: Multifunctional Database: MIXED Transactional Database Only: INNODB Non-Transactional Database Only: MYISAM @@ -2637,213 +2965,229 @@ resources dedicated to MyISAM. The remaining resources are allocated to InnoDB. -2.3.6.6. The InnoDB Tablespace Dialog +2.3.6.6 The InnoDB Tablespace Dialog - Some users may want to locate the InnoDB tablespace files in a - different location than the MySQL server data directory. Placing - the tablespace files in a separate location can be desirable if - your system has a higher capacity or higher performance storage - device available, such as a RAID storage system. - MySQL Server Instance Configuration Wizard: InnoDB Data Tablespace - - To change the default location for the InnoDB tablespace files, - choose a new drive from the drop-down list of drive letters and - choose a new path from the drop-down list of paths. To create a - custom path, click the ... button. - - If you are modifying the configuration of an existing server, you - must click the Modify button before you change the path. In this - situation you must move the existing tablespace files to the new - location manually before starting the server. + Some users may want to locate the InnoDB tablespace files in + a different location than the MySQL server data directory. + Placing the tablespace files in a separate location can be + desirable if your system has a higher capacity or higher + performance storage device available, such as a RAID storage + system. + MySQL Server Instance Configuration Wizard: InnoDB Data + Tablespace + + To change the default location for the InnoDB tablespace + files, choose a new drive from the drop-down list of drive + letters and choose a new path from the drop-down list of + paths. To create a custom path, click the ... button. + + If you are modifying the configuration of an existing server, + you must click the Modify button before you change the path. + In this situation you must move the existing tablespace files + to the new location manually before starting the server. -2.3.6.7. The Concurrent Connections Dialog +2.3.6.7 The Concurrent Connections Dialog To prevent the server from running out of resources, it is - important to limit the number of concurrent connections to the - MySQL server that can be established. The Concurrent Connections - dialog enables you to choose the expected usage of your server, - and sets the limit for concurrent connections accordingly. It is - also possible to set the concurrent connection limit manually. + important to limit the number of concurrent connections to + the MySQL server that can be established. The Concurrent + Connections dialog enables you to choose the expected usage + of your server, and sets the limit for concurrent connections + accordingly. It is also possible to set the concurrent + connection limit manually. MySQL Server Instance Configuration Wizard: Connections - * Decision Support (DSS)/OLAP: Choose this option if your server - does not require a large number of concurrent connections. The - maximum number of connections is set at 100, with an average - of 20 concurrent connections assumed. - - * Online Transaction Processing (OLTP): Choose this option if - your server requires a large number of concurrent connections. - The maximum number of connections is set at 500. - - * Manual Setting: Choose this option to set the maximum number - of concurrent connections to the server manually. Choose the - number of concurrent connections from the drop-down box - provided, or enter the maximum number of connections into the - drop-down box if the number you desire is not listed. + * Decision Support (DSS)/OLAP: Choose this option if your + server does not require a large number of concurrent + connections. The maximum number of connections is set at + 100, with an average of 20 concurrent connections + assumed. + + * Online Transaction Processing (OLTP): Choose this option + if your server requires a large number of concurrent + connections. The maximum number of connections is set at + 500. + + * Manual Setting: Choose this option to set the maximum + number of concurrent connections to the server manually. + Choose the number of concurrent connections from the + drop-down box provided, or enter the maximum number of + connections into the drop-down box if the number you + desire is not listed. -2.3.6.8. The Networking and Strict Mode Options Dialog +2.3.6.8 The Networking and Strict Mode Options Dialog Use the Networking Options dialog to enable or disable TCP/IP networking and to configure the port number that is used to connect to the MySQL server. - MySQL Server Instance Configuration Wizard: Network Configuration + MySQL Server Instance Configuration Wizard: Network + Configuration TCP/IP networking is enabled by default. To disable TCP/IP - networking, uncheck the box next to the Enable TCP/IP Networking - option. + networking, uncheck the box next to the Enable TCP/IP + Networking option. - Port 3306 is used by default. To change the port used to access - MySQL, choose a new port number from the drop-down box or type a - new port number directly into the drop-down box. If the port - number you choose is in use, you are prompted to confirm your - choice of port number. - - Set the Server SQL Mode to either enable or disable strict mode. - Enabling strict mode (default) makes MySQL behave more like other - database management systems. If you run applications that rely on - MySQL's old "forgiving" behavior, make sure to either adapt those - applications or to disable strict mode. For more information about - strict mode, see Section 5.1.7, "Server SQL Modes." + Port 3306 is used by default. To change the port used to + access MySQL, choose a new port number from the drop-down box + or type a new port number directly into the drop-down box. If + the port number you choose is in use, you are prompted to + confirm your choice of port number. + + Set the Server SQL Mode to either enable or disable strict + mode. Enabling strict mode (default) makes MySQL behave more + like other database management systems. If you run + applications that rely on MySQL's old "forgiving" behavior, + make sure to either adapt those applications or to disable + strict mode. For more information about strict mode, see + Section 5.1.7, "Server SQL Modes." -2.3.6.9. The Character Set Dialog +2.3.6.9 The Character Set Dialog The MySQL server supports multiple character sets and it is - possible to set a default server character set that is applied to - all tables, columns, and databases unless overridden. Use the - Character Set dialog to change the default character set of the - MySQL server. + possible to set a default server character set that is + applied to all tables, columns, and databases unless + overridden. Use the Character Set dialog to change the + default character set of the MySQL server. MySQL Server Instance Configuration Wizard: Character Set - * Standard Character Set: Choose this option if you want to use - latin1 as the default server character set. latin1 is used for - English and many Western European languages. - - * Best Support For Multilingualism: Choose this option if you - want to use utf8 as the default server character set. This is - a Unicode character set that can store characters from many - different languages. - - * Manual Selected Default Character Set / Collation: Choose this - option if you want to pick the server's default character set - manually. Choose the desired character set from the provided - drop-down list. + * Standard Character Set: Choose this option if you want to + use latin1 as the default server character set. latin1 is + used for English and many Western European languages. + + * Best Support For Multilingualism: Choose this option if + you want to use utf8 as the default server character set. + This is a Unicode character set that can store characters + from many different languages. + + * Manual Selected Default Character Set / Collation: Choose + this option if you want to pick the server's default + character set manually. Choose the desired character set + from the provided drop-down list. -2.3.6.10. The Service Options Dialog +2.3.6.10 The Service Options Dialog On Windows platforms, the MySQL server can be installed as a - Windows service. When installed this way, the MySQL server can be - started automatically during system startup, and even restarted - automatically by Windows in the event of a service failure. - - The MySQL Server Instance Configuration Wizard installs the MySQL - server as a service by default, using the service name MySQL. If - you do not wish to install the service, uncheck the box next to - the Install As Windows Service option. You can change the service - name by picking a new service name from the drop-down box provided - or by entering a new service name into the drop-down box. - Note - - Service names can include any legal character except forward (/) - or backward (\) slashes, and must be less than 256 characters - long. + Windows service. When installed this way, the MySQL server + can be started automatically during system startup, and even + restarted automatically by Windows in the event of a service + failure. + + The MySQL Server Instance Configuration Wizard installs the + MySQL server as a service by default, using the service name + MySQL. If you do not wish to install the service, uncheck the + box next to the Install As Windows Service option. You can + change the service name by picking a new service name from + the drop-down box provided or by entering a new service name + into the drop-down box. + Note + + Service names can include any legal character except forward + (/) or backward (\) slashes, and must be less than 256 + characters long. Warning - If you are installing multiple versions of MySQL onto the same - machine, you must choose a different service name for each version - that you install. If you do not choose a different service for - each installed version then the service manager information will - be inconsistent and this will cause problems when you try to - uninstall a previous version. - - If you have already installed multiple versions using the same - service name, you must manually edit the contents of the - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services parameters - within the Windows registry to update the association of the - service name with the correct server version. - - Typically, when installing multiple versions you create a service - name based on the version information. For example, you might - install MySQL 5.x as mysql5, or specific versions such as MySQL - 5.5.0 as mysql50500. - - To install the MySQL server as a service but not have it started - automatically at startup, uncheck the box next to the Launch the - MySQL Server Automatically option. - -2.3.6.11. The Security Options Dialog - - The content of the security options portion of the MySQL Server - Instance Configuration Wizard will depend on whether this is a new - installation, or modifying an existing installation. + If you are installing multiple versions of MySQL onto the + same machine, you must choose a different service name for + each version that you install. If you do not choose a + different service for each installed version then the service + manager information will be inconsistent and this will cause + problems when you try to uninstall a previous version. + + If you have already installed multiple versions using the + same service name, you must manually edit the contents of the + HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services + parameters within the Windows registry to update the + association of the service name with the correct server + version. + + Typically, when installing multiple versions you create a + service name based on the version information. For example, + you might install MySQL 5.x as mysql5, or specific versions + such as MySQL 5.5.0 as mysql50500. + + To install the MySQL server as a service but not have it + started automatically at startup, uncheck the box next to the + Launch the MySQL Server Automatically option. + +2.3.6.11 The Security Options Dialog + + The content of the security options portion of the MySQL + Server Instance Configuration Wizard will depend on whether + this is a new installation, or modifying an existing + installation. * Setting the root password for a new installation - It is strongly recommended that you set a root password for - your MySQL server, and the MySQL Server Instance Config Wizard - requires by default that you do so. If you do not wish to set - a root password, uncheck the box next to the Modify Security - Settings option. + It is strongly recommended that you set a root password + for your MySQL server, and the MySQL Server Instance + Config Wizard requires by default that you do so. If you + do not wish to set a root password, uncheck the box next + to the Modify Security Settings option. MySQL Server Instance Config Wizard: Security - * To set the root password, enter the desired password into both - the New root password and Confirm boxes. + * To set the root password, enter the desired password into + both the New root password and Confirm boxes. Setting the root password for an existing installation If you are modifying the configuration of an existing - configuration, or you are installing an upgrade and the MySQL - Server Instance Configuration Wizard has detected an existing - MySQL system, then you must enter the existing password for - root before changing the configuration information. + configuration, or you are installing an upgrade and the + MySQL Server Instance Configuration Wizard has detected + an existing MySQL system, then you must enter the + existing password for root before changing the + configuration information. MySQL Server Instance Config Wizard: Security (Existing Installation) - If you want to change the current root password, enter the - desired new password into both the New root password and - Confirm boxes. - - To permit root logins from across the network, check the box next - to the Enable root access from remote machines option. This - decreases the security of your root account. - - To create an anonymous user account, check the box next to the - Create An Anonymous Account option. Creating an anonymous account - can decrease server security and cause login and permission - difficulties. For this reason, it is not recommended. - -2.3.6.12. The Confirmation Dialog - - The final dialog in the MySQL Server Instance Configuration Wizard - is the Confirmation Dialog. To start the configuration process, - click the Execute button. To return to a previous dialog, click - the Back button. To exit the MySQL Server Instance Configuration - Wizard without configuring the server, click the Cancel button. + If you want to change the current root password, enter + the desired new password into both the New root password + and Confirm boxes. + + To permit root logins from across the network, check the box + next to the Enable root access from remote machines option. + This decreases the security of your root account. + + To create an anonymous user account, check the box next to + the Create An Anonymous Account option. Creating an anonymous + account can decrease server security and cause login and + permission difficulties. For this reason, it is not + recommended. + +2.3.6.12 The Confirmation Dialog + + The final dialog in the MySQL Server Instance Configuration + Wizard is the Confirmation Dialog. To start the configuration + process, click the Execute button. To return to a previous + dialog, click the Back button. To exit the MySQL Server + Instance Configuration Wizard without configuring the server, + click the Cancel button. MySQL Server Instance Configuration Wizard: Confirmation After you click the Execute button, the MySQL Server Instance - Configuration Wizard performs a series of tasks and displays the - progress onscreen as the tasks are performed. - - The MySQL Server Instance Configuration Wizard first determines - configuration file options based on your choices using a template - prepared by MySQL developers and engineers. This template is named - my-template.ini and is located in your server installation - directory. - - The MySQL Configuration Wizard then writes these options to the - corresponding configuration file. + Configuration Wizard performs a series of tasks and displays + the progress onscreen as the tasks are performed. - If you chose to create a service for the MySQL server, the MySQL - Server Instance Configuration Wizard creates and starts the - service. If you are reconfiguring an existing service, the MySQL - Server Instance Configuration Wizard restarts the service to apply - your configuration changes. + The MySQL Server Instance Configuration Wizard first + determines configuration file options based on your choices + using a template prepared by MySQL developers and engineers. + This template is named my-template.ini and is located in your + server installation directory. + + The MySQL Configuration Wizard then writes these options to + the corresponding configuration file. + + If you chose to create a service for the MySQL server, the + MySQL Server Instance Configuration Wizard creates and starts + the service. If you are reconfiguring an existing service, + the MySQL Server Instance Configuration Wizard restarts the + service to apply your configuration changes. If you chose to set a root password, the MySQL Configuration - Wizard connects to the server, sets your new root password, and - applies any other security settings you may have selected. + Wizard connects to the server, sets your new root password, + and applies any other security settings you may have + selected. + + After the MySQL Server Instance Configuration Wizard has + completed its tasks, it displays a summary. Click the Finish + button to exit the MySQL Server Configuration Wizard. - After the MySQL Server Instance Configuration Wizard has completed - its tasks, it displays a summary. Click the Finish button to exit - the MySQL Server Configuration Wizard. - -2.3.6.13. MySQL Server Instance Config Wizard: Creating an Instance +2.3.6.13 MySQL Server Instance Config Wizard: Creating an Instance from the Command Line In addition to using the GUI interface to the MySQL Server @@ -2851,25 +3195,27 @@ automatically from the command line. To use the MySQL Server Instance Config Wizard on the command - line, you need to use the MySQLInstanceConfig.exe command that is - installed with MySQL in the bin directory within the installation - directory. MySQLInstanceConfig.exe takes a number of command-line - arguments the set the properties that would normally be selected - through the GUI interface, and then creates a new configuration - file (my.ini) by combining these selections with a template - configuration file to produce the working configuration file. - - The main command line options are provided in the table below. - Some of the options are required, while some options are optional. + line, you need to use the MySQLInstanceConfig.exe command + that is installed with MySQL in the bin directory within the + installation directory. MySQLInstanceConfig.exe takes a + number of command-line arguments the set the properties that + would normally be selected through the GUI interface, and + then creates a new configuration file (my.ini) by combining + these selections with a template configuration file to + produce the working configuration file. + + The main command line options are provided in the table + below. Some of the options are required, while some options + are optional. - Table 2.5. MySQL Server Instance Config Wizard Command Line + Table 2.5 MySQL Server Instance Config Wizard Command Line Options Option Description Required Parameters -nPRODUCTNAME The name of the instance when installed -pPATH Path of the base directory for installation. This is - equivalent to the directory when using the basedir configuration - parameter + equivalent to the directory when using the basedir + configuration parameter -vVERSION The version tag to use for this installation Action to Perform -i Install an instance @@ -2878,95 +3224,97 @@ -q Perform the operation quietly -lFILENAME Sae the installation progress in a logfile Config File to Use - -tFILENAME Path to the template config file that will be used to - generate the installed configuration file + -tFILENAME Path to the template config file that will be used + to generate the installed configuration file -cFILENAME Path to a config file to be generated The -t and -c options work together to set the configuration parameters for a new instance. The -t option specifies the - template configuration file to use as the basic configuration, - which are then merged with the configuration parameters generated - by the MySQL Server Instance Config Wizard into the configuration - file specified by the -c option. + template configuration file to use as the basic + configuration, which are then merged with the configuration + parameters generated by the MySQL Server Instance Config + Wizard into the configuration file specified by the -c + option. A sample template file, my-template.ini is provided in the - toplevel MySQL installation directory. The file contains elements - are replaced automatically by the MySQL Server Instance Config - Wizard during configuration. + toplevel MySQL installation directory. The file contains + elements are replaced automatically by the MySQL Server + Instance Config Wizard during configuration. If you specify a configuration file that already exists, the - existing configuration file will be saved in the file with the - original, with the date and time added. For example, the mysql.ini - will be copied to mysql 2009-10-27 1646.ini.bak. + existing configuration file will be saved in the file with + the original, with the date and time added. For example, the + mysql.ini will be copied to mysql 2009-10-27 1646.ini.bak. - The parameters that you can specify on the command line are listed - in the table below. + The parameters that you can specify on the command line are + listed in the table below. - Table 2.6. MySQL Server Instance Config Wizard Parameters + Table 2.6 MySQL Server Instance Config Wizard Parameters Parameter Description ServiceName=$ Specify the name of the service to be created AddBinToPath={yes | no} Specifies whether to add the binary directory of MySQL to the standard PATH environment variable - ServerType={DEVELOPMENT | SERVER | DEDICATED} Specify the server - type. For more information, see Section 2.3.6.4, "The Server Type - Dialog" + ServerType={DEVELOPMENT | SERVER | DEDICATED} Specify the + server type. For more information, see Section 2.3.6.4, "The + Server Type Dialog" DatabaseType={MIXED | INNODB | MYISAM} Specify the default - database type. For more information, see Section 2.3.6.5, "The - Database Usage Dialog" + database type. For more information, see Section 2.3.6.5, + "The Database Usage Dialog" ConnectionUsage={DSS | OLTP} Specify the type of connection - support, this automates the setting for the number of concurrent - connections (see the ConnectionCount parameter). For more - information, see Section 2.3.6.7, "The Concurrent Connections - Dialog" - ConnectionCount=# Specify the number of concurrent connections to - support. For more information, see Section 2.3.6.4, "The Server - Type Dialog" - SkipNetworking={yes | no} Specify whether network support should - be supported. Specifying yes disables network access altogether + support, this automates the setting for the number of + concurrent connections (see the ConnectionCount parameter). + For more information, see Section 2.3.6.7, "The Concurrent + Connections Dialog" + ConnectionCount=# Specify the number of concurrent + connections to support. For more information, see Section + 2.3.6.4, "The Server Type Dialog" + SkipNetworking={yes | no} Specify whether network support + should be supported. Specifying yes disables network access + altogether Port=# Specify the network port number to use for network connections. For more information, see Section 2.3.6.8, "The Networking and Strict Mode Options Dialog" - StrictMode={yes | no} Specify whether to use the strict SQL mode. - For more information, see Section 2.3.6.8, "The Networking and - Strict Mode Options Dialog" - Charset=$ Specify the default character set. For more information, - see Section 2.3.6.9, "The Character Set Dialog" + StrictMode={yes | no} Specify whether to use the strict SQL + mode. For more information, see Section 2.3.6.8, "The + Networking and Strict Mode Options Dialog" + Charset=$ Specify the default character set. For more + information, see Section 2.3.6.9, "The Character Set Dialog" RootPassword=$ Specify the root password RootCurrentPassword=$ Specify the current root password then stopping or reconfiguring an existing service Note - When specifying options on the command line, you can enclose the - entire command-line option and the value you are specifying using - double quotation marks. This enables you to use spaces in the - options. For example, "-cC:\mysql.ini". - - The following command installs a MySQL Server 5.5 instance from - the directory C:\Program Files\MySQL\MySQL Server 5.5 using the - service name MySQL55 and setting the root password to 1234. + When specifying options on the command line, you can enclose + the entire command-line option and the value you are + specifying using double quotation marks. This enables you to + use spaces in the options. For example, "-cC:\mysql.ini". + + The following command installs a MySQL Server 5.5 instance + from the directory C:\Program Files\MySQL\MySQL Server 5.5 + using the service name MySQL55 and setting the root password + to 1234. shell> MySQLInstanceConfig.exe -i -q "-lC:\mysql_install_log.txt" » - "-nMySQL Server 5.5" "-pC:\Program Files\MySQL\MySQL Server 5.5" - -v5.5.36 » - "-tmy-template.ini" "-cC:\mytest.ini" ServerType=DEVELOPMENT Datab -aseType=MIXED » - ConnectionUsage=DSS Port=3311 ServiceName=MySQL55 RootPassword=123 -4 + "-nMySQL Server 5.5" "-pC:\Program Files\MySQL\MySQL Server 5.5" -v +5.5.44 » + "-tmy-template.ini" "-cC:\mytest.ini" ServerType=DEVELOPMENT Databa +seType=MIXED » + ConnectionUsage=DSS Port=3311 ServiceName=MySQL55 RootPassword=1234 In the above example, a log file will be generated in mysql_install_log.txt containing the information about the - instance creation process. The log file generated by the above - example is shown below: + instance creation process. The log file generated by the + above example is shown below: Welcome to the MySQL Server Instance Configuration Wizard 1.0.16.0 Date: 2009-10-27 17:07:21 Installing service ... Product Name: MySQL Server 5.5 -Version: 5.5.36 +Version: 5.5.44 Installation Path: C:\Program Files\MySQL\MySQL Server 5.5\ -Creating configuration file C:\mytest.ini using template my-template. -ini. +Creating configuration file C:\mytest.ini using template my-template.i +ni. Options: DEVELOPMENT MIXED @@ -2982,14 +3330,16 @@ Creating Windows service entry. Service name: "MySQL55" -Parameters: "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld" -- -defaults-file="C:\mytest.ini" MySQL55. +Parameters: "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld" --d +efaults-file="C:\mytest.ini" MySQL55. Windows service MySQL55 installed. - When using the command line, the return values in the following - table indicate an error performing the specified option. + When using the command line, the return values in the + following table indicate an error performing the specified + option. - Table 2.7. Return Value from MySQL Server Instance Config Wizard + Table 2.7 Return Value from MySQL Server Instance Config + Wizard Value Description 2 Configuration template file cannot be found 3 The Windows service entry cannot be created @@ -3000,17 +3350,18 @@ 8 The configuration file cannot be written 9 The Windows service entry cannot be removed - You can perform an installation of MySQL automatically using the - MSI package. For more information, see Section 2.3.5.2, - "Automating MySQL Installation on Microsoft Windows Using the MSI - Package." + You can perform an installation of MySQL automatically using + the MSI package. For more information, see Section 2.3.5.2, + "Automating MySQL Installation on Microsoft Windows Using the + MSI Package." -2.3.7. Installing MySQL on Microsoft Windows Using a noinstall Zip +2.3.7 Installing MySQL on Microsoft Windows Using a noinstall Zip Archive - Users who are installing from the noinstall package can use the - instructions in this section to manually install MySQL. The - process for installing MySQL from a Zip archive is as follows: + Users who are installing from the noinstall package can use + the instructions in this section to manually install MySQL. + The process for installing MySQL from a Zip archive is as + follows: 1. Extract the archive to the desired install directory @@ -3024,195 +3375,208 @@ This process is described in the sections that follow. -2.3.7.1. Extracting the Install Archive +2.3.7.1 Extracting the Install Archive To install MySQL manually, do the following: - 1. If you are upgrading from a previous version please refer to - Section 2.3.9, "Upgrading MySQL on Windows," before beginning - the upgrade process. + 1. If you are upgrading from a previous version please refer + to Section 2.3.9, "Upgrading MySQL on Windows," before + beginning the upgrade process. - 2. Make sure that you are logged in as a user with administrator - privileges. + 2. Make sure that you are logged in as a user with + administrator privileges. 3. Choose an installation location. Traditionally, the MySQL - server is installed in C:\mysql. The MySQL Installation Wizard - installs MySQL under C:\Program Files\MySQL. If you do not - install MySQL at C:\mysql, you must specify the path to the - install directory during startup or in an option file. See - Section 2.3.7.2, "Creating an Option File." + server is installed in C:\mysql. The MySQL Installation + Wizard installs MySQL under C:\Program Files\MySQL. If + you do not install MySQL at C:\mysql, you must specify + the path to the install directory during startup or in an + option file. See Section 2.3.7.2, "Creating an Option + File." + Note + The MySQL Installer installs MySQL under C:\Program + Files\MySQL. 4. Extract the install archive to the chosen installation - location using your preferred Zip archive tool. Some tools may - extract the archive to a folder within your chosen - installation location. If this occurs, you can move the - contents of the subfolder into the chosen installation - location. - -2.3.7.2. Creating an Option File - - If you need to specify startup options when you run the server, - you can indicate them on the command line or place them in an - option file. For options that are used every time the server - starts, you may find it most convenient to use an option file to - specify your MySQL configuration. This is particularly true under - the following circumstances: - - * The installation or data directory locations are different - from the default locations (C:\Program Files\MySQL\MySQL - Server 5.5 and C:\Program Files\MySQL\MySQL Server 5.5\data). - - * You need to tune the server settings, such as memory, cache, - or InnoDB configuration information. - - When the MySQL server starts on Windows, it looks for option files - in several locations, such as the Windows directory, C:\, and the - MySQL installation directory (for the full list of locations, see - Section 4.2.3.3, "Using Option Files"). The Windows directory - typically is named something like C:\WINDOWS. You can determine - its exact location from the value of the WINDIR environment - variable using the following command: + location using your preferred Zip archive tool. Some + tools may extract the archive to a folder within your + chosen installation location. If this occurs, you can + move the contents of the subfolder into the chosen + installation location. + +2.3.7.2 Creating an Option File + + If you need to specify startup options when you run the + server, you can indicate them on the command line or place + them in an option file. For options that are used every time + the server starts, you may find it most convenient to use an + option file to specify your MySQL configuration. This is + particularly true under the following circumstances: + + * The installation or data directory locations are + different from the default locations (C:\Program + Files\MySQL\MySQL Server 5.5 and C:\Program + Files\MySQL\MySQL Server 5.5\data). + + * You need to tune the server settings, such as memory, + cache, or InnoDB configuration information. + + When the MySQL server starts on Windows, it looks for option + files in several locations, such as the Windows directory, + C:\, and the MySQL installation directory (for the full list + of locations, see Section 4.2.6, "Using Option Files"). The + Windows directory typically is named something like + C:\WINDOWS. You can determine its exact location from the + value of the WINDIR environment variable using the following + command: C:\> echo %WINDIR% - MySQL looks for options in each location first in the my.ini file, - and then in the my.cnf file. However, to avoid confusion, it is - best if you use only one file. If your PC uses a boot loader where - C: is not the boot drive, your only option is to use the my.ini - file. Whichever option file you use, it must be a plain text file. - Note - - When using the MySQL Installer to install MySQL Server, it will - create the my.ini at the default location. And as of MySQL Server - 5.5.27, the user running MySQL Installer is granted full - permissions to this new my.ini. - - In other words, be sure that the MySQL Server user has permission - to read the my.ini file. - - You can also make use of the example option files included with - your MySQL distribution; see Section 5.1.2, "Server Configuration - Defaults." - - An option file can be created and modified with any text editor, - such as Notepad. For example, if MySQL is installed in E:\mysql - and the data directory is in E:\mydata\data, you can create an - option file containing a [mysqld] section to specify values for - the basedir and datadir options: + MySQL looks for options in each location first in the my.ini + file, and then in the my.cnf file. However, to avoid + confusion, it is best if you use only one file. If your PC + uses a boot loader where C: is not the boot drive, your only + option is to use the my.ini file. Whichever option file you + use, it must be a plain text file. + Note + + When using the MySQL Installer to install MySQL Server, it + will create the my.ini at the default location. And as of + MySQL Server 5.5.27, the user running MySQL Installer is + granted full permissions to this new my.ini. + + In other words, be sure that the MySQL Server user has + permission to read the my.ini file. + + You can also make use of the example option files included + with your MySQL distribution; see Section 5.1.2, "Server + Configuration Defaults." + + An option file can be created and modified with any text + editor, such as Notepad. For example, if MySQL is installed + in E:\mysql and the data directory is in E:\mydata\data, you + can create an option file containing a [mysqld] section to + specify values for the basedir and datadir options: [mysqld] # set basedir to your installation path basedir=E:/mysql # set datadir to the location of your data directory datadir=E:/mydata/data - Note that Windows path names are specified in option files using - (forward) slashes rather than backslashes. If you do use - backslashes, double them: + Microsoft Windows path names are specified in option files + using (forward) slashes rather than backslashes. If you do + use backslashes, double them: [mysqld] # set basedir to your installation path basedir=E:\\mysql # set datadir to the location of your data directory datadir=E:\\mydata\\data - The rules for use of backslash in option file values are given in - Section 4.2.3.3, "Using Option Files." + The rules for use of backslash in option file values are + given in Section 4.2.6, "Using Option Files." - The data directory is located within the AppData directory for the - user running MySQL. + The data directory is located within the AppData directory + for the user running MySQL. - If you would like to use a data directory in a different location, - you should copy the entire contents of the data directory to the - new location. For example, if you want to use E:\mydata as the - data directory instead, you must do two things: - - 1. Move the entire data directory and all of its contents from - the default location (for example C:\Program Files\MySQL\MySQL - Server 5.5\data) to E:\mydata. + If you would like to use a data directory in a different + location, you should copy the entire contents of the data + directory to the new location. For example, if you want to + use E:\mydata as the data directory instead, you must do two + things: + + 1. Move the entire data directory and all of its contents + from the default location (for example C:\Program + Files\MySQL\MySQL Server 5.5\data) to E:\mydata. 2. Use a --datadir option to specify the new data directory location each time you start the server. -2.3.7.3. Selecting a MySQL Server Type +2.3.7.3 Selecting a MySQL Server Type - The following table shows the available servers for Windows in - MySQL 5.5. + The following table shows the available servers for Windows + in MySQL 5.5. Binary Description mysqld Optimized binary with named-pipe support - mysqld-debug Like mysqld, but compiled with full debugging and - automatic memory allocation checking + mysqld-debug Like mysqld, but compiled with full debugging + and automatic memory allocation checking All of the preceding binaries are optimized for modern Intel processors, but should work on any Intel i386-class or higher processor. Each of the servers in a distribution support the same set of - storage engines. The SHOW ENGINES statement displays which engines - a given server supports. + storage engines. The SHOW ENGINES statement displays which + engines a given server supports. - All Windows MySQL 5.5 servers have support for symbolic linking of - database directories. + All Windows MySQL 5.5 servers have support for symbolic + linking of database directories. - MySQL supports TCP/IP on all Windows platforms. MySQL servers on - Windows support named pipes as indicated in the following list. - However, the default is to use TCP/IP regardless of platform. - (Named pipes are slower than TCP/IP in many Windows - configurations.) - - Named pipes are enabled only if you start the server with the - --enable-named-pipe option. It is necessary to use this option - explicitly because some users have experienced problems with - shutting down the MySQL server when named pipes were used. + MySQL supports TCP/IP on all Windows platforms. MySQL servers + on Windows also support named pipes, if you start the server + with the --enable-named-pipe option. It is necessary to use + this option explicitly because some users have experienced + problems with shutting down the MySQL server when named pipes + were used. The default is to use TCP/IP regardless of + platform because named pipes are slower than TCP/IP in many + Windows configurations. -2.3.7.4. Starting the Server for the First Time +2.3.7.4 Starting the Server for the First Time This section gives a general overview of starting the MySQL - server. The following sections provide more specific information - for starting the MySQL server from the command line or as a - Windows service. + server. The following sections provide more specific + information for starting the MySQL server from the command + line or as a Windows service. The information here applies primarily if you installed MySQL - using the Noinstall version, or if you wish to configure and test - MySQL manually rather than with the GUI tools. + using the Noinstall version, or if you wish to configure and + test MySQL manually rather than with the GUI tools. + Note + + The MySQL server will automatically start after using the + MySQL Installer, and the MySQL Notifier GUI can be used to + start/stop/restart at any time. The examples in these sections assume that MySQL is installed - under the default location of C:\Program Files\MySQL\MySQL Server - 5.5. Adjust the path names shown in the examples if you have MySQL - installed in a different location. - - Clients have two options. They can use TCP/IP, or they can use a - named pipe if the server supports named-pipe connections. - - MySQL for Windows also supports shared-memory connections if the - server is started with the --shared-memory option. Clients can - connect through shared memory by using the --protocol=MEMORY - option. + under the default location of C:\Program Files\MySQL\MySQL + Server 5.5. Adjust the path names shown in the examples if + you have MySQL installed in a different location. + + Clients have two options. They can use TCP/IP, or they can + use a named pipe if the server supports named-pipe + connections. + + MySQL for Windows also supports shared-memory connections if + the server is started with the --shared-memory option. + Clients can connect through shared memory by using the + --protocol=MEMORY option. For information about which server binary to run, see Section 2.3.7.3, "Selecting a MySQL Server Type." - Testing is best done from a command prompt in a console window (or - "DOS window"). In this way you can have the server display status - messages in the window where they are easy to see. If something is - wrong with your configuration, these messages make it easier for - you to identify and fix any problems. + Testing is best done from a command prompt in a console + window (or "DOS window"). In this way you can have the server + display status messages in the window where they are easy to + see. If something is wrong with your configuration, these + messages make it easier for you to identify and fix any + problems. To start the server, enter this command: C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld" --console For a server that includes InnoDB support, you should see the - messages similar to those following as it starts (the path names - and sizes may differ): + messages similar to those following as it starts (the path + names and sizes may differ): InnoDB: The first specified datafile c:\ibdata\ibdata1 did not exist: InnoDB: a new database to be created! InnoDB: Setting file c:\ibdata\ibdata1 size to 209715200 InnoDB: Database physically writes the file full: wait... -InnoDB: Log file c:\iblogs\ib_logfile0 did not exist: new to be creat -ed +InnoDB: Log file c:\iblogs\ib_logfile0 did not exist: new to be create +d InnoDB: Setting log file c:\iblogs\ib_logfile0 size to 31457280 -InnoDB: Log file c:\iblogs\ib_logfile1 did not exist: new to be creat -ed +InnoDB: Log file c:\iblogs\ib_logfile1 did not exist: new to be create +d InnoDB: Setting log file c:\iblogs\ib_logfile1 size to 31457280 -InnoDB: Log file c:\iblogs\ib_logfile2 did not exist: new to be creat -ed +InnoDB: Log file c:\iblogs\ib_logfile2 did not exist: new to be create +d InnoDB: Setting log file c:\iblogs\ib_logfile2 size to 31457280 InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created @@ -3221,151 +3585,170 @@ 011024 10:58:25 InnoDB: Started When the server finishes its startup sequence, you should see - something like this, which indicates that the server is ready to - service client connections: + something like this, which indicates that the server is ready + to service client connections: mysqld: ready for connections -Version: '5.5.36' socket: '' port: 3306 +Version: '5.5.44' socket: '' port: 3306 The server continues to write to the console any further - diagnostic output it produces. You can open a new console window - in which to run client programs. + diagnostic output it produces. You can open a new console + window in which to run client programs. - If you omit the --console option, the server writes diagnostic - output to the error log in the data directory (C:\Program - Files\MySQL\MySQL Server 5.5\data by default). The error log is - the file with the .err extension, or may be specified by passing - in the --log-error option. + If you omit the --console option, the server writes + diagnostic output to the error log in the data directory + (C:\Program Files\MySQL\MySQL Server 5.5\data by default). + The error log is the file with the .err extension, and may be + set using the --log-error option. Note - The accounts that are listed in the MySQL grant tables initially - have no passwords. After starting the server, you should set up - passwords for them using the instructions in Section 2.11.2, - "Securing the Initial MySQL Accounts." + The accounts that are listed in the MySQL grant tables + initially have no passwords. After starting the server, you + should set up passwords for them using the instructions in + Section 2.10.2, "Securing the Initial MySQL Accounts." -2.3.7.5. Starting MySQL from the Windows Command Line +2.3.7.5 Starting MySQL from the Windows Command Line - The MySQL server can be started manually from the command line. - This can be done on any version of Windows. + The MySQL server can be started manually from the command + line. This can be done on any version of Windows. + Note + + The MySQL Notifier GUI can also be used to start/stop/restart + the MySQL server. - To start the mysqld server from the command line, you should start - a console window (or "DOS window") and enter this command: + To start the mysqld server from the command line, you should + start a console window (or "DOS window") and enter this + command: C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld" - The path to mysqld may vary depending on the install location of - MySQL on your system. + The path to mysqld may vary depending on the install location + of MySQL on your system. You can stop the MySQL server by executing this command: C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqladmin" -u root - shutdown +shutdown + + Note + + If the MySQL root user account has a password, you need to + invoke mysqladmin with the -p option and supply the password + when prompted. + This command invokes the MySQL administrative utility + mysqladmin to connect to the server and tell it to shut down. + The command connects as the MySQL root user, which is the + default administrative account in the MySQL grant system. Note - If the MySQL root user account has a password, you need to invoke - mysqladmin with the -p option and supply the password when - prompted. - - This command invokes the MySQL administrative utility mysqladmin - to connect to the server and tell it to shut down. The command - connects as the MySQL root user, which is the default - administrative account in the MySQL grant system. Note that users - in the MySQL grant system are wholly independent from any login - users under Windows. - - If mysqld doesn't start, check the error log to see whether the - server wrote any messages there to indicate the cause of the - problem. By default, the error log is located in the C:\Program - Files\MySQL\MySQL Server 5.5\data directory. It is the file with a - suffix of .err, or may be specified by passing in the --log-error - option. Alternatively, you can try to start the server as mysqld - --console; in this case, you may get some useful information on - the screen that may help solve the problem. + Users in the MySQL grant system are wholly independent from + any login users under Microsoft Windows. + + If mysqld doesn't start, check the error log to see whether + the server wrote any messages there to indicate the cause of + the problem. By default, the error log is located in the + C:\Program Files\MySQL\MySQL Server 5.5\data directory. It is + the file with a suffix of .err, or may be specified by + passing in the --log-error option. Alternatively, you can try + to start the server with the --console option; in this case, + the server may display some useful information on the screen + that will help solve the problem. The last option is to start mysqld with the --standalone and --debug options. In this case, mysqld writes a log file - C:\mysqld.trace that should contain the reason why mysqld doesn't - start. See Section 23.4.3, "The DBUG Package." + C:\mysqld.trace that should contain the reason why mysqld + doesn't start. See Section 24.4.3, "The DBUG Package." - Use mysqld --verbose --help to display all the options that mysqld - supports. + Use mysqld --verbose --help to display all the options that + mysqld supports. -2.3.7.6. Customizing the PATH for MySQL Tools +2.3.7.6 Customizing the PATH for MySQL Tools - To make it easier to invoke MySQL programs, you can add the path - name of the MySQL bin directory to your Windows system PATH - environment variable: + To make it easier to invoke MySQL programs, you can add the + path name of the MySQL bin directory to your Windows system + PATH environment variable: - * On the Windows desktop, right-click the My Computer icon, and - select Properties. + * On the Windows desktop, right-click the My Computer icon, + and select Properties. - * Next select the Advanced tab from the System Properties menu - that appears, and click the Environment Variables button. + * Next select the Advanced tab from the System Properties + menu that appears, and click the Environment Variables + button. - * Under System Variables, select Path, and then click the Edit - button. The Edit System Variable dialogue should appear. + * Under System Variables, select Path, and then click the + Edit button. The Edit System Variable dialogue should + appear. * Place your cursor at the end of the text appearing in the - space marked Variable Value. (Use the End key to ensure that - your cursor is positioned at the very end of the text in this - space.) Then enter the complete path name of your MySQL bin - directory (for example, C:\Program Files\MySQL\MySQL Server - 5.5\bin) + space marked Variable Value. (Use the End key to ensure + that your cursor is positioned at the very end of the + text in this space.) Then enter the complete path name of + your MySQL bin directory (for example, C:\Program + Files\MySQL\MySQL Server 5.5\bin) Note - There must be a semicolon separating this path from any values - present in this field. - Dismiss this dialogue, and each dialogue in turn, by clicking - OK until all of the dialogues that were opened have been - dismissed. You should now be able to invoke any MySQL - executable program by typing its name at the DOS prompt from - any directory on the system, without having to supply the - path. This includes the servers, the mysql client, and all - MySQL command-line utilities such as mysqladmin and mysqldump. - You should not add the MySQL bin directory to your Windows - PATH if you are running multiple MySQL servers on the same - machine. + There must be a semicolon separating this path from any + values present in this field. + Dismiss this dialogue, and each dialogue in turn, by + clicking OK until all of the dialogues that were opened + have been dismissed. You should now be able to invoke any + MySQL executable program by typing its name at the DOS + prompt from any directory on the system, without having + to supply the path. This includes the servers, the mysql + client, and all MySQL command-line utilities such as + mysqladmin and mysqldump. + You should not add the MySQL bin directory to your + Windows PATH if you are running multiple MySQL servers on + the same machine. Warning You must exercise great care when editing your system PATH by - hand; accidental deletion or modification of any portion of the - existing PATH value can leave you with a malfunctioning or even - unusable system. - -2.3.7.7. Starting MySQL as a Windows Service - - On Windows, the recommended way to run MySQL is to install it as a - Windows service, so that MySQL starts and stops automatically when - Windows starts and stops. A MySQL server installed as a service - can also be controlled from the command line using NET commands, - or with the graphical Services utility. Generally, to install - MySQL as a Windows service you should be logged in using an - account that has administrator rights. - - The Services utility (the Windows Service Control Manager) can be - found in the Windows Control Panel (under Administrative Tools on - Windows 2000, XP, Vista, and Server 2003). To avoid conflicts, it - is advisable to close the Services utility while performing server - installation or removal operations from the command line. + hand; accidental deletion or modification of any portion of + the existing PATH value can leave you with a malfunctioning + or even unusable system. + +2.3.7.7 Starting MySQL as a Windows Service + + On Windows, the recommended way to run MySQL is to install it + as a Windows service, so that MySQL starts and stops + automatically when Windows starts and stops. A MySQL server + installed as a service can also be controlled from the + command line using NET commands, or with the graphical + Services utility. Generally, to install MySQL as a Windows + service you should be logged in using an account that has + administrator rights. + Note + + The MySQL Notifier GUI can also be used to monitor the status + of the MySQL service. + + The Services utility (the Windows Service Control Manager) + can be found in the Windows Control Panel (under + Administrative Tools on Windows 2000, XP, Vista, and Server + 2003). To avoid conflicts, it is advisable to close the + Services utility while performing server installation or + removal operations from the command line. Installing the service - Before installing MySQL as a Windows service, you should first - stop the current server if it is running by using the following - command: + Before installing MySQL as a Windows service, you should + first stop the current server if it is running by using the + following command: C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqladmin" -u root shutdown Note - If the MySQL root user account has a password, you need to invoke - mysqladmin with the -p option and supply the password when - prompted. - - This command invokes the MySQL administrative utility mysqladmin - to connect to the server and tell it to shut down. The command - connects as the MySQL root user, which is the default - administrative account in the MySQL grant system. Note that users - in the MySQL grant system are wholly independent from any login - users under Windows. + If the MySQL root user account has a password, you need to + invoke mysqladmin with the -p option and supply the password + when prompted. + + This command invokes the MySQL administrative utility + mysqladmin to connect to the server and tell it to shut down. + The command connects as the MySQL root user, which is the + default administrative account in the MySQL grant system. + Note + + Users in the MySQL grant system are wholly independent from + any login users under Windows. Install the server as a service using this command: C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld" --install @@ -3373,406 +3756,477 @@ The service-installation command does not start the server. Instructions for that are given later in this section. - To make it easier to invoke MySQL programs, you can add the path - name of the MySQL bin directory to your Windows system PATH - environment variable: - - * On the Windows desktop, right-click the My Computer icon, and - select Properties. - - * Next select the Advanced tab from the System Properties menu - that appears, and click the Environment Variables button. - - * Under System Variables, select Path, and then click the Edit - button. The Edit System Variable dialogue should appear. + To make it easier to invoke MySQL programs, you can add the + path name of the MySQL bin directory to your Windows system + PATH environment variable: + + * On the Windows desktop, right-click the My Computer icon, + and select Properties. + + * Next select the Advanced tab from the System Properties + menu that appears, and click the Environment Variables + button. + + * Under System Variables, select Path, and then click the + Edit button. The Edit System Variable dialogue should + appear. * Place your cursor at the end of the text appearing in the - space marked Variable Value. (Use the End key to ensure that - your cursor is positioned at the very end of the text in this - space.) Then enter the complete path name of your MySQL bin - directory (for example, C:\Program Files\MySQL\MySQL Server - 5.5\bin), Note that there should be a semicolon separating - this path from any values present in this field. Dismiss this - dialogue, and each dialogue in turn, by clicking OK until all - of the dialogues that were opened have been dismissed. You - should now be able to invoke any MySQL executable program by - typing its name at the DOS prompt from any directory on the - system, without having to supply the path. This includes the - servers, the mysql client, and all MySQL command-line - utilities such as mysqladmin and mysqldump. - You should not add the MySQL bin directory to your Windows - PATH if you are running multiple MySQL servers on the same - machine. + space marked Variable Value. (Use the End key to ensure + that your cursor is positioned at the very end of the + text in this space.) Then enter the complete path name of + your MySQL bin directory (for example, C:\Program + Files\MySQL\MySQL Server 5.5\bin), and there should be a + semicolon separating this path from any values present in + this field. Dismiss this dialogue, and each dialogue in + turn, by clicking OK until all of the dialogues that were + opened have been dismissed. You should now be able to + invoke any MySQL executable program by typing its name at + the DOS prompt from any directory on the system, without + having to supply the path. This includes the servers, the + mysql client, and all MySQL command-line utilities such + as mysqladmin and mysqldump. + You should not add the MySQL bin directory to your + Windows PATH if you are running multiple MySQL servers on + the same machine. Warning You must exercise great care when editing your system PATH by - hand; accidental deletion or modification of any portion of the - existing PATH value can leave you with a malfunctioning or even - unusable system. + hand; accidental deletion or modification of any portion of + the existing PATH value can leave you with a malfunctioning + or even unusable system. - The following additional arguments can be used when installing the - service: + The following additional arguments can be used when + installing the service: * You can specify a service name immediately following the --install option. The default service name is MySQL. - * If a service name is given, it can be followed by a single - option. By convention, this should be - --defaults-file=file_name to specify the name of an option - file from which the server should read options when it starts. + * If a service name is given, it can be followed by a + single option. By convention, this should be + --defaults-file=file_name to specify the name of an + option file from which the server should read options + when it starts. The use of a single option other than --defaults-file is - possible but discouraged. --defaults-file is more flexible - because it enables you to specify multiple startup options for - the server by placing them in the named option file. + possible but discouraged. --defaults-file is more + flexible because it enables you to specify multiple + startup options for the server by placing them in the + named option file. - * You can also specify a --local-service option following the - service name. This causes the server to run using the + * You can also specify a --local-service option following + the service name. This causes the server to run using the LocalService Windows account that has limited system - privileges. This account is available only for Windows XP or - newer. If both --defaults-file and --local-service are given - following the service name, they can be in any order. - - For a MySQL server that is installed as a Windows service, the - following rules determine the service name and option files that - the server uses: - - * If the service-installation command specifies no service name - or the default service name (MySQL) following the --install - option, the server uses the a service name of MySQL and reads - options from the [mysqld] group in the standard option files. - - * If the service-installation command specifies a service name - other than MySQL following the --install option, the server - uses that service name. It reads options from the [mysqld] - group and the group that has the same name as the service in - the standard option files. This enables you to use the - [mysqld] group for options that should be used by all MySQL - services, and an option group with the service name for use by - the server installed with that service name. + privileges. This account is available only for Windows XP + or newer. If both --defaults-file and --local-service are + given following the service name, they can be in any + order. + + For a MySQL server that is installed as a Windows service, + the following rules determine the service name and option + files that the server uses: + + * If the service-installation command specifies no service + name or the default service name (MySQL) following the + --install option, the server uses the a service name of + MySQL and reads options from the [mysqld] group in the + standard option files. + + * If the service-installation command specifies a service + name other than MySQL following the --install option, the + server uses that service name. It reads options from the + [mysqld] group and the group that has the same name as + the service in the standard option files. This enables + you to use the [mysqld] group for options that should be + used by all MySQL services, and an option group with the + service name for use by the server installed with that + service name. * If the service-installation command specifies a --defaults-file option after the service name, the server - reads options the same way as described in the previous item, - except that it reads options only from the the named file and - ignores the standard option files. + reads options the same way as described in the previous + item, except that it reads options only from the named + file and ignores the standard option files. As a more complex example, consider the following command: C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld" --install MySQL --defaults-file=C:\my-opts.cnf Here, the default service name (MySQL) is given after the - --install option. If no --defaults-file option had been given, - this command would have the effect of causing the server to read - the [mysqld] group from the standard option files. However, - because the --defaults-file option is present, the server reads - options from the [mysqld] option group, and only from the named - file. + --install option. If no --defaults-file option had been + given, this command would have the effect of causing the + server to read the [mysqld] group from the standard option + files. However, because the --defaults-file option is + present, the server reads options from the [mysqld] option + group, and only from the named file. Note - On Windows, if the server is started with the --defaults-file and - --install options, --install must be first. Otherwise, mysqld.exe - will attempt to start the MySQL server. + On Windows, if the server is started with the --defaults-file + and --install options, --install must be first. Otherwise, + mysqld.exe will attempt to start the MySQL server. - You can also specify options as Start parameters in the Windows - Services utility before you start the MySQL service. + You can also specify options as Start parameters in the + Windows Services utility before you start the MySQL service. Starting the service Once a MySQL server has been installed as a service, Windows starts the service automatically whenever Windows starts. The - service also can be started immediately from the Services utility, - or by using a NET START MySQL command. The NET command is not case - sensitive. - - When run as a service, mysqld has no access to a console window, - so no messages can be seen there. If mysqld does not start, check - the error log to see whether the server wrote any messages there - to indicate the cause of the problem. The error log is located in - the MySQL data directory (for example, C:\Program - Files\MySQL\MySQL Server 5.5\data). It is the file with a suffix - of .err. + service also can be started immediately from the Services + utility, or by using a NET START MySQL command. The NET + command is not case sensitive. + + When run as a service, mysqld has no access to a console + window, so no messages can be seen there. If mysqld does not + start, check the error log to see whether the server wrote + any messages there to indicate the cause of the problem. The + error log is located in the MySQL data directory (for + example, C:\Program Files\MySQL\MySQL Server 5.5\data). It is + the file with a suffix of .err. When a MySQL server has been installed as a service, and the - service is running, Windows stops the service automatically when - Windows shuts down. The server also can be stopped manually by - using the Services utility, the NET STOP MySQL command, or the - mysqladmin shutdown command. + service is running, Windows stops the service automatically + when Windows shuts down. The server also can be stopped + manually by using the Services utility, the NET STOP MySQL + command, or the mysqladmin shutdown command. You also have the choice of installing the server as a manual service if you do not wish for the service to be started automatically during the boot process. To do this, use the --install-manual option rather than the --install option: -C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld" --install-m -anual +C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld" --install-ma +nual Removing the service - To remove a server that is installed as a service, first stop it - if it is running by executing NET STOP MySQL. Then use the + To remove a server that is installed as a service, first stop + it if it is running by executing NET STOP MySQL. Then use the --remove option to remove it: C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld" --remove - If mysqld is not running as a service, you can start it from the - command line. For instructions, see Section 2.3.7.5, "Starting - MySQL from the Windows Command Line." - - Please see Section 2.3.8, "Troubleshooting a Microsoft Windows - MySQL Server Installation," if you encounter difficulties during - installation. + If mysqld is not running as a service, you can start it from + the command line. For instructions, see Section 2.3.7.5, + "Starting MySQL from the Windows Command Line." + + If you encounter difficulties during installation. see + Section 2.3.8, "Troubleshooting a Microsoft Windows MySQL + Server Installation." -2.3.7.8. Testing The MySQL Installation +2.3.7.8 Testing The MySQL Installation - You can test whether the MySQL server is working by executing any - of the following commands: + You can test whether the MySQL server is working by executing + any of the following commands: C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqlshow" -C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqlshow" -u root -mysql +C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqlshow" -u root m +ysql C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqladmin" version - status proc +status proc C:\> "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysql" test - If mysqld is slow to respond to TCP/IP connections from client - programs, there is probably a problem with your DNS. In this case, - start mysqld with the --skip-name-resolve option and use only - localhost and IP addresses in the Host column of the MySQL grant - tables. - - You can force a MySQL client to use a named-pipe connection rather - than TCP/IP by specifying the --pipe or --protocol=PIPE option, or - by specifying . (period) as the host name. Use the --socket option - to specify the name of the pipe if you do not want to use the - default pipe name. - - Note that if you have set a password for the root account, deleted - the anonymous account, or created a new user account, then you - must use the appropriate -u and -p options with the commands shown - above to connect with the MySQL Server. See Section 4.2.2, - "Connecting to the MySQL Server." + If mysqld is slow to respond to TCP/IP connections from + client programs, there is probably a problem with your DNS. + In this case, start mysqld with the --skip-name-resolve + option and use only localhost and IP addresses in the Host + column of the MySQL grant tables. + + You can force a MySQL client to use a named-pipe connection + rather than TCP/IP by specifying the --pipe or + --protocol=PIPE option, or by specifying . (period) as the + host name. Use the --socket option to specify the name of the + pipe if you do not want to use the default pipe name. + + If you have set a password for the root account, deleted the + anonymous account, or created a new user account, then to + connect to the MySQL server you must use the appropriate -u + and -p options with the commands shown previously. See + Section 4.2.2, "Connecting to the MySQL Server." For more information about mysqlshow, see Section 4.5.6, - "mysqlshow --- Display Database, Table, and Column Information." + "mysqlshow --- Display Database, Table, and Column + Information." -2.3.8. Troubleshooting a Microsoft Windows MySQL Server Installation +2.3.8 Troubleshooting a Microsoft Windows MySQL Server Installation When installing and running MySQL for the first time, you may encounter certain errors that prevent the MySQL server from - starting. The purpose of this section is to help you diagnose and - correct some of these errors. + starting. This section helps you diagnose and correct some of + these errors. Your first resource when troubleshooting server issues is the error log. The MySQL server uses the error log to record - information relevant to the error that prevents the server from - starting. The error log is located in the data directory specified - in your my.ini file. The default data directory location is - C:\Program Files\MySQL\MySQL Server 5.5\data, or - C:\ProgramData\Mysql on Windows 7 and Windows Server 2008. The - C:\ProgramData directory is hidden by default. You need to change - your folder options to see the directory and contents. For more - information on the error log and understanding the content, see - Section 5.2.2, "The Error Log." - - Another source of information regarding possible errors is the - console messages displayed when the MySQL service is starting. Use - the NET START MySQL command from the command line after installing - mysqld as a service to see any error messages regarding the - starting of the MySQL server as a service. See Section 2.3.7.7, - "Starting MySQL as a Windows Service." - - The following examples show other common error messages you may - encounter when installing MySQL and starting the server for the - first time: + information relevant to the error that prevents the server + from starting. The error log is located in the data directory + specified in your my.ini file. The default data directory + location is C:\Program Files\MySQL\MySQL Server 5.5\data, or + C:\ProgramData\Mysql on Windows 7 and Windows Server 2008. + The C:\ProgramData directory is hidden by default. You need + to change your folder options to see the directory and + contents. For more information on the error log and + understanding the content, see Section 5.2.2, "The Error + Log." + + For information regarding possible errors, also consult the + console messages displayed when the MySQL service is + starting. Use the NET START MySQL command from the command + line after installing mysqld as a service to see any error + messages regarding the starting of the MySQL server as a + service. See Section 2.3.7.7, "Starting MySQL as a Windows + Service." - * If the MySQL server cannot find the mysql privileges database - or other critical files, you may see these messages: + The following examples show other common error messages you + might encounter when installing MySQL and starting the server + for the first time: + + * If the MySQL server cannot find the mysql privileges + database or other critical files, it displays these + messages: System error 1067 has occurred. -Fatal error: Can't open privilege tables: Table 'mysql.host' doesn't -exist +Fatal error: Can't open and lock privilege tables: +Table 'mysql.user' doesn't exist + These messages often occur when the MySQL base or data directories are installed in different locations than the - default locations (C:\Program Files\MySQL\MySQL Server 5.5 and - C:\Program Files\MySQL\MySQL Server 5.5\data, respectively). - This situation may occur when MySQL is upgraded and installed - to a new location, but the configuration file is not updated - to reflect the new location. In addition, there may be old and - new configuration files that conflict. Be sure to delete or - rename any old configuration files when upgrading MySQL. + default locations (C:\Program Files\MySQL\MySQL Server + 5.5 and C:\Program Files\MySQL\MySQL Server 5.5\data, + respectively). + This situation can occur when MySQL is upgraded and + installed to a new location, but the configuration file + is not updated to reflect the new location. In addition, + old and new configuration files might conflict. Be sure + to delete or rename any old configuration files when + upgrading MySQL. If you have installed MySQL to a directory other than - C:\Program Files\MySQL\MySQL Server 5.5, you need to ensure - that the MySQL server is aware of this through the use of a - configuration (my.ini) file. The my.ini file needs to be - located in your Windows directory, typically C:\WINDOWS. You - can determine its exact location from the value of the WINDIR - environment variable by issuing the following command from the - command prompt: + C:\Program Files\MySQL\MySQL Server 5.5, ensure that the + MySQL server is aware of this through the use of a + configuration (my.ini) file. Put the my.ini file in your + Windows directory, typically C:\WINDOWS. To determine its + exact location from the value of the WINDIR environment + variable, issue the following command from the command + prompt: C:\> echo %WINDIR% - An option file can be created and modified with any text - editor, such as Notepad. For example, if MySQL is installed in - E:\mysql and the data directory is D:\MySQLdata, you can - create the option file and set up a [mysqld] section to - specify values for the basedir and datadir options: + + You can create or modify an option file with any text + editor, such as Notepad. For example, if MySQL is + installed in E:\mysql and the data directory is + D:\MySQLdata, you can create the option file and set up a + [mysqld] section to specify values for the basedir and + datadir options: [mysqld] # set basedir to your installation path basedir=E:/mysql # set datadir to the location of your data directory datadir=D:/MySQLdata - Note that Windows path names are specified in option files - using (forward) slashes rather than backslashes. If you do use - backslashes, double them: + + Microsoft Windows path names are specified in option + files using (forward) slashes rather than backslashes. If + you do use backslashes, double them: [mysqld] # set basedir to your installation path basedir=C:\\Program Files\\MySQL\\MySQL Server 5.5 # set datadir to the location of your data directory datadir=D:\\MySQLdata - The rules for use of backslash in option file values are given - in Section 4.2.3.3, "Using Option Files." - If you change the datadir value in your MySQL configuration - file, you must move the contents of the existing MySQL data - directory before restarting the MySQL server. + + The rules for use of backslash in option file values are + given in Section 4.2.6, "Using Option Files." + If you change the datadir value in your MySQL + configuration file, you must move the contents of the + existing MySQL data directory before restarting the MySQL + server. See Section 2.3.7.2, "Creating an Option File." - * If you reinstall or upgrade MySQL without first stopping and - removing the existing MySQL service and install MySQL using - the MySQL Configuration Wizard, you may see this error: + * If you reinstall or upgrade MySQL without first stopping + and removing the existing MySQL service and install MySQL + using the MySQL Installer, you might see this error: Error: Cannot create Windows service for MySql. Error: 0 - This occurs when the Configuration Wizard tries to install the - service and finds an existing service with the same name. - One solution to this problem is to choose a service name other - than mysql when using the configuration wizard. This enables - the new service to be installed correctly, but leaves the - outdated service in place. Although this is harmless, it is - best to remove old services that are no longer in use. + + This occurs when the Configuration Wizard tries to + install the service and finds an existing service with + the same name. + One solution to this problem is to choose a service name + other than mysql when using the configuration wizard. + This enables the new service to be installed correctly, + but leaves the outdated service in place. Although this + is harmless, it is best to remove old services that are + no longer in use. To permanently remove the old mysql service, execute the - following command as a user with administrative privileges, on - the command-line: + following command as a user with administrative + privileges, on the command line: C:\> sc delete mysql [SC] DeleteService SUCCESS + If the sc utility is not available for your version of Windows, download the delsrv utility from - http://www.microsoft.com/windows2000/techinfo/reskit/tools/exi - sting/delsrv-o.asp and use the delsrv mysql syntax. + http://www.microsoft.com/windows2000/techinfo/reskit/tool + s/existing/delsrv-o.asp and use the delsrv mysql syntax. -2.3.9. Upgrading MySQL on Windows +2.3.9 Upgrading MySQL on Windows - This section lists some of the steps you should take when - upgrading MySQL on Windows. + To upgrade MySQL on Windows, follow these steps: - 1. Review Section 2.12.1, "Upgrading MySQL," for additional + 1. Review Section 2.11.1, "Upgrading MySQL," for additional information on upgrading MySQL that is not specific to Windows. - 2. You should always back up your current MySQL installation - before performing an upgrade. See Section 7.2, "Database - Backup Methods." + 2. Always back up your current MySQL installation before + performing an upgrade. See Section 7.2, "Database Backup + Methods." 3. Download the latest Windows distribution of MySQL from http://dev.mysql.com/downloads/. - 4. Before upgrading MySQL, you must stop the server. If the - server is installed as a service, stop the service with the + 4. Before upgrading MySQL, stop the server. If the server is + installed as a service, stop the service with the following command from the command prompt: C:\> NET STOP MySQL + If you are not running the MySQL server as a service, use mysqladmin to stop it. For example, before upgrading from - MySQL 5.1 to 5.5, use mysqladmin from MySQL 5.1 as follows: + MySQL 5.1 to 5.5, use mysqladmin from MySQL 5.1 as + follows: C:\> "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqladmin" -u root - shutdown +shutdown + Note - If the MySQL root user account has a password, you need to - invoke mysqladmin with the -p option and supply the password - when prompted. - - 5. Before upgrading a MySQL service from MySQL 5.1 to 5.5, you - should stop the 5.1 server and remove the instance. Run the - MySQL Instance Configuration Wizard, choose the Remove - Instance option and in the next screen, confirm removal. After - that it is safe to uninstall MySQL Server 5.1. - - 6. Before upgrading to MySQL 5.5 from a version previous to - 4.1.5, or from a version of MySQL installed from a Zip archive - to a version of MySQL installed with the MySQL Installation - Wizard, you must first manually remove the previous - installation and MySQL service (if the server is installed as - a service). + If the MySQL root user account has a password, invoke + mysqladmin with the -p option and enter the password when + prompted. + + 5. Before upgrading to MySQL 5.5 from a version previous to + 4.1.5, or from a version of MySQL installed from a Zip + archive to a version of MySQL installed with the MySQL + Installation Wizard, you must first manually remove the + previous installation and MySQL service (if the server is + installed as a service). To remove the MySQL service, use the following command: C:\> C:\mysql\bin\mysqld --remove + If you do not remove the existing service, the MySQL - Installation Wizard may fail to properly install the new MySQL - service. + Installation Wizard may fail to properly install the new + MySQL service. - 7. If you are using the MySQL Installation Wizard, start the + 6. If you are using the MySQL Installer, start it as + described in Section 2.3.3, "Installing MySQL on + Microsoft Windows Using MySQL Installer." + If you are using the MySQL Installation Wizard, start the wizard as described in Section 2.3.5.1, "Using the MySQL Installation Wizard." - 8. If you are installing MySQL from a Zip archive, extract the - archive. You may either overwrite your existing MySQL - installation (usually located at C:\mysql), or install it into - a different directory, such as C:\mysql5. Overwriting the - existing installation is recommended. - - 9. If you were running MySQL as a Windows service and you had to - remove the service earlier in this procedure, reinstall the - service. (See Section 2.3.7.7, "Starting MySQL as a Windows - Service.") - 10. Restart the server. For example, use NET START MySQL if you - run MySQL as a service, or invoke mysqld directly otherwise. - 11. As Administrator, run mysql_upgrade to check your tables, - attempt to repair them if necessary, and update your grant - tables if they have changed so that you can take advantage of - any new capabilities. See Section 4.4.7, "mysql_upgrade --- - Check and Upgrade MySQL Tables." - 12. If you encounter errors, see Section 2.3.8, "Troubleshooting a - Microsoft Windows MySQL Server Installation." - -2.3.10. Windows Postinstallation Procedures - - On Windows, you need not create the data directory and the grant - tables. MySQL Windows distributions include the grant tables with - a set of preinitialized accounts in the mysql database under the - data directory. Regarding passwords, if you installed MySQL using - the Windows Installation Wizard, you may have already assigned - passwords to the accounts. (See Section 2.3.5.1, "Using the MySQL - Installation Wizard.") Otherwise, use the password-assignment - procedure given in Section 2.11.2, "Securing the Initial MySQL - Accounts." + 7. If you are upgrading MySQL from a Zip archive, extract + the archive. You may either overwrite your existing MySQL + installation (usually located at C:\mysql), or install it + into a different directory, such as C:\mysql5. + Overwriting the existing installation is recommended. + However, for upgrades (as opposed to installing for the + first time), you must remove the data directory from your + existing MySQL installation to avoid replacing your + current data files. To do so, follow these steps: + a. Unzip the Zip archive in some location other than + your current MySQL installation + b. Remove the data directory + c. Rezip the Zip archive + d. Unzip the modified Zip archive on top of your + existing installation + Alternatively: + a. Unzip the Zip archive in some location other than + your current MySQL installation + b. Remove the data directory + c. Move the data directory from the current MySQL + installation to the location of the just-removed + data directory + d. Remove the current MySQL installation + e. Move the unzipped installation to the location of + the just-removed installation + + 8. If you were running MySQL as a Windows service and you + had to remove the service earlier in this procedure, + reinstall the service. (See Section 2.3.7.7, "Starting + MySQL as a Windows Service.") + + 9. Restart the server. For example, use NET START MySQL if + you run MySQL as a service, or invoke mysqld directly + otherwise. + 10. As Administrator, run mysql_upgrade to check your tables, + attempt to repair them if necessary, and update your + grant tables if they have changed so that you can take + advantage of any new capabilities. See Section 4.4.7, + "mysql_upgrade --- Check and Upgrade MySQL Tables." + 11. If you encounter errors, see Section 2.3.8, + "Troubleshooting a Microsoft Windows MySQL Server + Installation." - Before setting up passwords, you might want to try running some - client programs to make sure that you can connect to the server - and that it is operating properly. Make sure that the server is - running (see Section 2.3.7.4, "Starting the Server for the First - Time"), and then issue the following commands to verify that you - can retrieve information from the server. You may need to specify - directory different from C:\mysql\bin on the command line. If you - used the Windows Installation Wizard, the default directory is - C:\Program Files\MySQL\MySQL Server 5.5, and the mysql and - mysqlshow client programs are in C:\Program Files\MySQL\MySQL - Server 5.5\bin. See Section 2.3.5.1, "Using the MySQL Installation - Wizard," for more information. +2.3.10 Windows Postinstallation Procedures - Use mysqlshow to see what databases exist: -C:\> C:\mysql\bin\mysqlshow -+--------------------+ -| Databases | + GUI tools exist that perform most of the tasks described + below, including: + + * MySQL Installer: Used to install and upgrade MySQL + products. + + * MySQL Workbench: Manages the MySQL server and edits SQL + statements. + + * MySQL Notifier: Starts, stops, or restarts the MySQL + server, and monitors its status. + + * MySQL for Excel + (http://dev.mysql.com/doc/mysql-for-excel/en/index.html): + Edits MySQL data with Microsoft Excel. + + On Windows, you need not create the data directory and the + grant tables. MySQL Windows distributions include the grant + tables with a set of preinitialized accounts in the mysql + database under the data directory. Regarding passwords, if + you installed MySQL using the MySQL Installer, you may have + already assigned passwords to the accounts. (See Section + 2.3.3, "Installing MySQL on Microsoft Windows Using MySQL + Installer.") Otherwise, use the password-assignment procedure + given in Section 2.10.2, "Securing the Initial MySQL + Accounts." + + Before setting up passwords, you might want to try running + some client programs to make sure that you can connect to the + server and that it is operating properly. Make sure that the + server is running (see Section 2.3.7.4, "Starting the Server + for the First Time"). If you are running a version of Windows + that supports services, you can set up the MySQL server to + run automatically when Windows starts (see Section 2.3.7.7, + "Starting MySQL as a Windows Service"). + + With the server running, issue the following commands to + verify that you can retrieve information from the server. You + may need to specify a directory different from C:\mysql\bin + on the command line. If you installed MySQL using MySQL + Installer, the default directory is C:\Program + Files\MySQL\MySQL Server 5.5, and the mysql and mysqlshow + client programs are in C:\Program Files\MySQL\MySQL Server + 5.5\bin. See Section 2.3.3, "Installing MySQL on Microsoft + Windows Using MySQL Installer," for more information. + + Use mysqlshow to see what databases exist: +C:\> C:\mysql\bin\mysqlshow ++--------------------+ +| Databases | +--------------------+ | information_schema | | mysql | | test | +--------------------+ - The list of installed databases may vary, but will always include - the minimum of mysql and information_schema. In most cases, the - test database will also be installed automatically. - - The preceding command (and commands for other MySQL programs such - as mysql) may not work if the correct MySQL account does not - exist. For example, the program may fail with an error, or you may - not be able to view all databases. If you installed using the MSI - packages and used the MySQL Server Instance Config Wizard, then - the root user will have been created automatically with the - password you supplied. In this case, you should use the -u root - and -p options. (You will also need to use the -u root and -p - options if you have already secured the initial MySQL accounts.) - With -p, you will be prompted for the root password. For example: + The list of installed databases may vary, but will always + include the minimum of mysql and information_schema. In most + cases, the test database will also be installed + automatically. + + The preceding command (and commands for other MySQL programs + such as mysql) may not work if the correct MySQL account does + not exist. For example, the program may fail with an error, + or you may not be able to view all databases. If you + installed MySQL using MySQL Installer, the root user will + have been created automatically with the password you + supplied. In this case, you should use the -u root and -p + options. (You must use those options if you have already + secured the initial MySQL accounts.) With -p, the client + program prompts for the root password. For example: C:\> C:\mysql\bin\mysqlshow -u root -p Enter password: (enter root password here) +--------------------+ @@ -3783,8 +4237,8 @@ | test | +--------------------+ - If you specify a database name, mysqlshow displays a list of the - tables within the database: + If you specify a database name, mysqlshow displays a list of + the tables within the database: C:\> C:\mysql\bin\mysqlshow mysql Database: mysql +---------------------------+ @@ -3812,8 +4266,8 @@ | user | +---------------------------+ - Use the mysql program to select information from a table in the - mysql database: + Use the mysql program to select information from a table in + the mysql database: C:\> C:\mysql\bin\mysql -e "SELECT Host,Db,User FROM mysql.db" +------+--------+------+ | host | db | user | @@ -3822,180 +4276,155 @@ | % | test_% | | +------+--------+------+ - For more information about mysqlshow and mysql, see Section 4.5.6, - "mysqlshow --- Display Database, Table, and Column Information," - and Section 4.5.1, "mysql --- The MySQL Command-Line Tool." - - If you are running a version of Windows that supports services, - you can set up the MySQL server to run automatically when Windows - starts. See Section 2.3.7.7, "Starting MySQL as a Windows - Service." - -2.4. Installing MySQL on Mac OS X - - MySQL for Mac OS X is available in a number of different forms: + For more information about mysqlshow and mysql, see Section + 4.5.6, "mysqlshow --- Display Database, Table, and Column + Information," and Section 4.5.1, "mysql --- The MySQL + Command-Line Tool." + +2.4 Installing MySQL on OS X + + For a list of supported OS X versions that the MySQL server + supports, see + http://www.mysql.com/support/supportedplatforms/database.html + . + + MySQL for OS X is available in a number of different forms: + + * Native Package Installer format, which uses the native OS + X installer (DMG) to walk you through the installation of + MySQL. For more information, see Section 2.4.2, + "Installing MySQL on OS X Using Native Packages." You can + use the package installer with OS X. The user you use to + perform the installation must have administrator + privileges. - * Native Package Installer format, which uses the native Mac OS - X installer to walk you through the installation of MySQL. For - more information, see Section 2.4.2, "Installing MySQL on Mac - OS X Using Native Packages." You can use the package installer - with Mac OS X 10.3 and later, and the package is available for - both PowerPC and Intel architectures, and 32-bit and 64-bit - architectures. There is no Universal Binary available using - the package installation method. The user you use to perform - the installation must have administrator privileges. - - * Tar package format, which uses a file packaged using the Unix - tar and gzip commands. To use this method, you will need to - open a Terminal window. You do not need administrator - privileges using this method, as you can install the MySQL - server anywhere using this method. For more information on - using this method, you can use the generic instructions for - using a tarball, Section 2.2, "Installing MySQL on Unix/Linux - Using Generic Binaries."You can use the package installer with - Mac OS X 10.3 and later, and available for both PowerPC and - Intel architectures, and both 32-bit and 64-bit architectures. - A Universal Binary, incorporating both Power PC and Intel - architectures and 32-bit and 64-bit binaries is available. - In addition to the core installation, the Package Installer - also includes Section 2.4.3, "Installing the MySQL Startup - Item" and Section 2.4.4, "Installing and Using the MySQL - Preference Pane," both of which simplify the management of - your installation. - - * Mac OS X server includes a version of MySQL as standard. If - you want to use a more recent version than that supplied with - the Mac OS X server release, you can make use of the package - or tar formats. For more information on using the MySQL - bundled with Mac OS X, see Section 2.4.5, "Using the Bundled - MySQL on Mac OS X Server." + * Tar package format, which uses a file packaged using the + Unix tar and gzip commands. To use this method, you will + need to open a Terminal window. You do not need + administrator privileges using this method, as you can + install the MySQL server anywhere using this method. For + more information on using this method, you can use the + generic instructions for using a tarball, Section 2.2, + "Installing MySQL on Unix/Linux Using Generic Binaries." + In addition to the core installation, the Package + Installer also includes Section 2.4.4, "Installing the + MySQL Startup Item" and Section 2.4.5, "Installing and + Using the MySQL Preference Pane," both of which simplify + the management of your installation. - For additional information on using MySQL on Mac OS X, see Section - 2.4.1, "General Notes on Installing MySQL on Mac OS X." + For additional information on using MySQL on OS X, see + Section 2.4.1, "General Notes on Installing MySQL on OS X." -2.4.1. General Notes on Installing MySQL on Mac OS X +2.4.1 General Notes on Installing MySQL on OS X You should keep the following issues and notes in mind: - * The default location for the MySQL Unix socket is different on - Mac OS X and Mac OS X Server depending on the installation - type you chose. The following table shows the default - locations by installation type. - Table 2.8. MySQL Unix Socket Locations on Mac OS X by - Installation Type - - Installation Type Socket Location - Package Installer from MySQL /tmp/mysql.sock - Tarball from MySQL /tmp/mysql.sock - MySQL Bundled with Mac OS X Server /var/mysql/mysql.sock - To prevent issues, you should either change the configuration - of the socket used within your application (for example, - changing php.ini), or you should configure the socket location - using a MySQL configuration file and the socket option. For - more information, see Section 5.1.3, "Server Command Options." - - * You may need (or want) to create a specific mysql user to own - the MySQL directory and data. On Mac OS X 10.4 and lower you - can do this by using the Netinfo Manager application, located - within the Utilities folder within the Applications folder. On - Mac OS X 10.5 and later you can do this through the Directory - Utility. From Mac OS X 10.5 and later (including Mac OS X - Server 10.5) the mysql should already exist. For use in single - user mode, an entry for _mysql (note the underscore prefix) - should already exist within the system /etc/passwd file. - - * Due to a bug in the Mac OS X package installer, you may see - this error message in the destination disk selection dialog: -You cannot install this software on this disk. (null) - If this error occurs, click the Go Back button once to return - to the previous screen. Then click Continue to advance to the - destination disk selection again, and you should be able to - choose the destination disk correctly. We have reported this - bug to Apple and it is investigating this problem. + * OS X 10.4 deprecated startup items in favor of launchd + daemons, and as of OS X 10.10 (Yosemite), startup items + do not function. For these reasons, using launchd daemons + is preferred over startup items. + + * You may need (or want) to create a specific mysql user to + own the MySQL directory and data. You can do this through + the Directory Utility, and the mysql user should already + exist. For use in single user mode, an entry for _mysql + (note the underscore prefix) should already exist within + the system /etc/passwd file. * If you get an "insecure startup item disabled" error when MySQL launches, use the following procedure. Adjust the pathnames appropriately for your system. - 1. Modify the mysql.script using this command (enter it on a - single line): + 1. Modify the mysql.script using this command (enter it + on a single line): shell> sudo /Applications/TextEdit.app/Contents/MacOS/TextEdit /usr/local/mysql/support-files/mysql.server - 2. Locate the option file that defines the basedir value and - modify it to contain these lines: + + 2. Locate the option file that defines the basedir + value and modify it to contain these lines: basedir=/usr/local/mysql datadir=/usr/local/mysql/data - In the /Library/StartupItems/MySQLCOM/ directory, make - the following group ID changes from staff to wheel: + + In the /Library/StartupItems/MySQLCOM/ directory, + make the following group ID changes from staff to + wheel: shell> sudo chgrp wheel MySQLCOM StartupParameters.plist - 3. Start the server from System Preferences or Terminal.app. - * Because the MySQL package installer installs the MySQL - contents into a version and platform specific directory, you - can use this to upgrade and migrate your database between - versions. You will need to either copy the data directory from - the old version to the new version, or alternatively specify - an alternative datadir value to set location of the data - directory. + 3. Start the server from System Preferences or + Terminal.app. - * You might want to add aliases to your shell's resource file to - make it easier to access commonly used programs such as mysql - and mysqladmin from the command line. The syntax for bash is: + * Because the MySQL package installer installs the MySQL + contents into a version and platform specific directory, + you can use this to upgrade and migrate your database + between versions. You will need to either copy the data + directory from the old version to the new version, or + alternatively specify an alternative datadir value to set + location of the data directory. By default, the MySQL + directories are installed under /usr/local/. + + * You might want to add aliases to your shell's resource + file to make it easier to access commonly used programs + such as mysql and mysqladmin from the command line. The + syntax for bash is: alias mysql=/usr/local/mysql/bin/mysql alias mysqladmin=/usr/local/mysql/bin/mysqladmin + For tcsh, use: alias mysql /usr/local/mysql/bin/mysql alias mysqladmin /usr/local/mysql/bin/mysqladmin - Even better, add /usr/local/mysql/bin to your PATH environment - variable. You can do this by modifying the appropriate startup - file for your shell. For more information, see Section 4.2.1, - "Invoking MySQL Programs." - - * After you have copied over the MySQL database files from the - previous installation and have successfully started the new - server, you should consider removing the old installation - files to save disk space. Additionally, you should also remove - older versions of the Package Receipt directories located in + + Even better, add /usr/local/mysql/bin to your PATH + environment variable. You can do this by modifying the + appropriate startup file for your shell. For more + information, see Section 4.2.1, "Invoking MySQL + Programs." + + * After you have copied over the MySQL database files from + the previous installation and have successfully started + the new server, you should consider removing the old + installation files to save disk space. Additionally, you + should also remove older versions of the Package Receipt + directories located in /Library/Receipts/mysql-VERSION.pkg. -2.4.2. Installing MySQL on Mac OS X Using Native Packages + * Prior to OS X 10.7, MySQL server was bundled with OS X + Server. - You can install MySQL on Mac OS X 10.3.x ("Panther") or newer - using a Mac OS X binary package in DMG format instead of the - binary tarball distribution. Please note that older versions of - Mac OS X (for example, 10.1.x or 10.2.x) are not supported by this - package. - - The package is located inside a disk image (.dmg) file that you - first need to mount by double-clicking its icon in the Finder. It - should then mount the image and display its contents. +2.4.2 Installing MySQL on OS X Using Native Packages + + The package is located inside a disk image (.dmg) file that + you first need to mount by double-clicking its icon in the + Finder. It should then mount the image and display its + contents. Note Before proceeding with the installation, be sure to stop all - running MySQL server instances by using either the MySQL Manager - Application (on Mac OS X Server) or mysqladmin shutdown on the - command line. - - When installing from the package version, you should also install - the MySQL Preference Pane, which will enable you to control the - startup and execution of your MySQL server from System - Preferences. For more information, see Section 2.4.4, "Installing - and Using the MySQL Preference Pane." + running MySQL server instances by using either the MySQL + Manager Application (on OS X Server) or mysqladmin shutdown + on the command line. + + When installing from the package version, you can also + install the MySQL Preference Pane, which will enable you to + control the startup and execution of your MySQL server from + System Preferences. For more information, see Section 2.4.5, + "Installing and Using the MySQL Preference Pane." When installing using the package installer, the files are - installed into a directory within /usr/local matching the name of - the installation version and platform. For example, the installer - file mysql-5.1.39-osx10.5-x86_64.pkg installs MySQL into - /usr/local/mysql-5.1.39-osx10.5-x86_64 . The following table shows - the layout of the installation directory. + installed into a directory within /usr/local matching the + name of the installation version and platform. For example, + the installer file mysql-5.5-osx10.8-x86_64.dmg installs + MySQL into /usr/local/mysql-5.5-osx10.8-x86_64/ . The + following table shows the layout of the installation + directory. - Table 2.9. MySQL Installation Layout on Mac OS X + Table 2.8 MySQL Installation Layout on OS X Directory Contents of Directory bin Client programs and the mysqld server data Log files, databases - docs Manual in Info format + docs Helper documents, like the Release Notes and build + information include Include (header) files lib Libraries man Unix manual pages @@ -4012,300 +4441,319 @@ created during installation will be created automatically. 1. Download and open the MySQL package installer, which is - provided on a disk image (.dmg) that includes the main MySQL - installation package, the MySQLStartupItem.pkg installation - package, and the MySQL.prefPane. Double-click the disk image - to open it. - - 2. Double-click the MySQL installer package. It will be named - according to the version of MySQL you have downloaded. For - example, if you have downloaded MySQL 5.1.39, double-click - mysql-5.1.39-osx10.5-x86.pkg. - - 3. You will be presented with the opening installer dialog. Click - Continue to begin installation. - MySQL Package Installer: Step 1 - - 4. A copy of the installation instructions and other important - information relevant to this installation are displayed. Click - Continue . - - 5. If you have downloaded the community version of MySQL, you - will be shown a copy of the relevant GNU General Public - License. Click Continue . - - 6. Select the drive you want to use to install the MySQL Startup - Item. The drive must have a valid, bootable, Mac OS X - operating system installed. Click Continue. - MySQL Package Installer: Step 4 - - 7. You will be asked to confirm the details of the installation, - including the space required for the installation. To change - the drive on which the startup item is installed, click either - Go Back or Change Install Location.... To install the startup - item, click Install. - - 8. Once the installation has been completed successfully, you - will be shown an Install Succeeded message. - - For convenience, you may also want to install the startup item and - preference pane. See Section 2.4.3, "Installing the MySQL Startup - Item," and Section 2.4.4, "Installing and Using the MySQL - Preference Pane." + provided on a disk image (.dmg) that includes the main + MySQL installation package file. Double-click the disk + image to open it. + Figure 2.41 MySQL Package Installer: DMG Contents + MySQL Package Installer: DMG Contents + + 2. Double-click the MySQL installer package. It will be + named according to the version of MySQL you have + downloaded. For example, if you have downloaded MySQL + server 5.5.44, double-click + mysql-5.5.44-osx-10.8-x86_64.pkg. + + 3. You will be presented with the opening installer dialog. + Click Continue to begin installation. + Figure 2.42 MySQL Package Installer: Introduction + MySQL Package Installer: Introduction + + 4. If you have downloaded the community version of MySQL, + you will be shown a copy of the relevant GNU General + Public License. Click Continue and then Agree to + continue. + + 5. From the Installation Type page you can either click + Install to execute the installation wizard using all + defaults, click Customize to alter which components to + install (MySQL server, Startup Item, Preference Pane -- + all enabled by default), or click Change Installation + Location to change the type of installation for either + all users, only the user executing the Installer, or + define a custom location. + Figure 2.43 MySQL Package Installer: Installation Type + MySQL Package Installer: Installation Type + Figure 2.44 MySQL Package Installer: Destination Select + (Change Installation Location) + MySQL Package Installer: Destination Select (Change + Installation Location) + Figure 2.45 MySQL Package Installer: Customize + MySQL Package Installer: Customize + + 6. Click Install to begin the installation process. + + 7. Once the installation has been completed successfully, + you will be shown an Install Succeeded message with a + short summary. Now, Close the wizard and begin using the + MySQL server. + Figure 2.46 MySQL Package Installer: Summary + MySQL Package Installer: Summary + + For convenience, you may also want to install a launch daemon + and preference pane. See Section 2.4.3, "Installing a MySQL + Launch Daemon," and Section 2.4.5, "Installing and Using the + MySQL Preference Pane." + +2.4.3 Installing a MySQL Launch Daemon + + OS X uses launch daemons to automatically start, stop, and + manage processes and applications such as MySQL. Using launch + daemons is recommended over startup items on OS X. + Note + + OS X 10.4 deprecated startup items in favor of launchd + daemons, and as of OS X 10.10 (Yosemite), startup items do + not function. For these reasons, using launchd daemons is + preferred over startup items. + + Here is an example launchd file that starts MySQL: + + + + + + KeepAlive + + Label + com.mysql.mysqld + ProgramArguments + + /usr/local/mysql/bin/mysqld_safe + --user=mysql + + + + + + Adjust the ProgramArguments array according to your system, + as for example your path to mysqld_safe might be different. + After making the proper adjustments, do the following: + + * Save the XML as a file named + /Library/LaunchDaemons/com.mysql.mysql.plist + + * Adjust the file permissions using the Apple recommended + owner "root", owning group "wheel", and file permissions + "644" +shell> sudo chown root:wheel /Library/LaunchDaemons/com.mysql.mysql.pl +ist +shell> sudo chmod 644 /Library/LaunchDaemons/com.mysql.mysql.plist + + + * Enable this new MySQL service +shell> sudo launchctl load -w /Library/LaunchDaemons/com.mysql.mysql.p +list + + The MySQL daemon is now running, and automatically starts + when your system is rebooted. -2.4.3. Installing the MySQL Startup Item +2.4.4 Installing the MySQL Startup Item - The MySQL Installation Package includes a startup item that can be - used to automatically start and stop MySQL. + The MySQL Installation Package includes a startup item that + can be used to automatically start and stop MySQL. + Important + + Startup items are deprecated in favor of launchd daemons. For + additional information, see Section 2.4.3, "Installing a + MySQL Launch Daemon." To install the MySQL Startup Item: 1. Download and open the MySQL package installer, which is - provided on a disk image (.dmg) that includes the main MySQL - installation package, the MySQLStartupItem.pkg installation - package, and the MySQL.prefPane. Double-click the disk image - to open it. + provided on a disk image (.dmg) that includes the main + MySQL installation package. + Note + Previously, the OS X packages included separate + MySQLStartupItem.pkg and MySQL.prefPane files. They have + since been merged into the main package file. + Figure 2.47 MySQL Package Installer: DMG Contents + MySQL Package Installer: DMG Contents + + 2. Go through the process of installing the MySQL server as + described in the documentation at Section 2.4.2, + "Installing MySQL on OS X Using Native Packages." - 2. Double-click the MySQLStartItem.pkg file to start the - installation process. + 3. Click Customize at the Installation Type step. The + "Startup Item" option is listed there and enabled by + default. + Figure 2.48 MySQL Installer on OS X: Customize + MySQL Installer on OS X: Customize - 3. You will be presented with the Install MySQL Startup Item - dialog. - MySQL Startup Item Installer: Step 1 - Click Continue to continue the installation process. - - 4. A copy of the installation instructions and other important - information relevant to this installation are displayed. Click - Continue . - - 5. Select the drive you want to use to install the MySQL Startup - Item. The drive must have a valid, bootable, Mac OS X - operating system installed. Click Continue. - MySQL Startup Item Installer: Step 3 - - 6. You will be asked to confirm the details of the installation. - To change the drive on which the startup item is installed, - click either Go Back or Change Install Location.... To install - the startup item, click Install. - - 7. Once the installation has been completed successfully, you - will be shown an Install Succeeded message. - MySQL Startup Item Installer: Step 5 + 4. Complete the MySQL server installation process. The Startup Item for MySQL is installed into - /Library/StartupItems/MySQLCOM. The Startup Item installation adds - a variable MYSQLCOM=-YES- to the system configuration file - /etc/hostconfig. If you want to disable the automatic startup of - MySQL, change this variable to MYSQLCOM=-NO-. - - After the installation, you can start and stop MySQL by running - the following commands in a terminal window. You must have - administrator privileges to perform these tasks, and you may be - prompted for your password. + /Library/StartupItems/MySQLCOM. The Startup Item installation + adds a variable MYSQLCOM=-YES- to the system configuration + file /etc/hostconfig. If you want to disable the automatic + startup of MySQL, change this variable to MYSQLCOM=-NO-. + Note + + Deselecting Automatically Start MySQL Server on Startup from + the MySQL Preference Pane sets the MYSQLCOM variable to -NO-. + + After the installation, you can start and stop the MySQL + server from the MySQL Preference Pane (preferred), or by + running the following commands in a terminal window. You must + have administrator privileges to perform these tasks, and you + may be prompted for your password. - If you have installed the Startup Item, use this command to start - the server: + If you have installed the Startup Item, use this command to + start the server: shell> sudo /Library/StartupItems/MySQLCOM/MySQLCOM start - If you have installed the Startup Item, use this command to stop - the server: + If you have installed the Startup Item, use this command to + stop the server: shell> sudo /Library/StartupItems/MySQLCOM/MySQLCOM stop -2.4.4. Installing and Using the MySQL Preference Pane +2.4.5 Installing and Using the MySQL Preference Pane - The MySQL Package installer disk image also includes a custom - MySQL Preference Pane that enables you to start, stop, and control - automated startup during boot of your MySQL installation. + The MySQL Installation Package includes a MySQL preference + Pane that enables you to start, stop, and control automated + startup during boot of your MySQL installation. To install the MySQL Preference Pane: - 1. Download and open the MySQL package installer package, which - is provided on a disk image (.dmg) that includes the main - MySQL installation package, the MySQLStartupItem.pkg - installation package, and the MySQL.prefPane. Double-click the - disk image to open it. - - 2. Double-click the MySQL.prefPane. The MySQL System Preferences - will open. - - 3. If this is the first time you have installed the preference - pane, you will be asked to confirm installation and whether - you want to install the preference pane for all users, or only - the current user. To install the preference pane for all users - you will need administrator privileges. If necessary, you will - be prompted for the username and password for a user with - administrator privileges. + 1. Download and open the MySQL package installer, which is + provided on a disk image (.dmg) that includes the main + MySQL installation package. + Note + Previously, the OS X packages included separate + MySQLStartupItem.pkg and MySQL.prefPane files. They have + since been merged into the main package file. + Figure 2.49 MySQL Package Installer: DMG Contents + MySQL Package Installer: DMG Contents + + 2. Go through the process of installing the MySQL server, as + described in the documentation at Section 2.4.2, + "Installing MySQL on OS X Using Native Packages." - 4. If you already have the MySQL Preference Pane installed, you - will be asked to confirm whether you want to overwrite the - existing MySQL Preference Pane. + 3. Click Customize at the Installation Type step. The + "Preference Pane" option is listed there and enabled by + default. + Figure 2.50 MySQL Installer on OS X: Customize + MySQL Installer on OS X: Customize - Note + 4. Complete the MySQL server installation process. - The MySQL Preference Pane only starts and stops MySQL installation - installed from the MySQL package installation that have been - installed in the default location. - - Once the MySQL Preference Pane has been installed, you can control - your MySQL server instance using the preference pane. To use the - preference pane, open the System Preferences... from the Apple - menu. Select the MySQL preference pane by clicking the MySQL logo - within the Other section of the preference panes list. - MySQL Preference Pane - - The MySQL Preference Pane shows the current status of the MySQL - server, showing stopped (in red) if the server is not running and - running (in green) if the server has already been started. The - preference pane also shows the current setting for whether the - MySQL server has been set to start automatically. - - * To start MySQL using the preference pane: - Click Start MySQL Server. You may be prompted for the username - and password of a user with administrator privileges to start - the MySQL server. - - * To stop MySQL using the preference pane: - Click Stop MySQL Server. You may be prompted for the username - and password of a user with administrator privileges to stop - the MySQL server. - - * To automatically start the MySQL server when the system boots: - Check the check box next to Automatically Start MySQL Server - on Startup. + Note - * To disable automatic MySQL server startup when the system - boots: - Uncheck the check box next to Automatically Start MySQL Server - on Startup. + The MySQL Preference Pane only starts and stops MySQL + installation installed from the MySQL package installation + that have been installed in the default location. - You can close the System Preferences... window once you have - completed your settings. + Once the MySQL Preference Pane has been installed, you can + control your MySQL server instance using the preference pane. + To use the preference pane, open the System Preferences... + from the Apple menu. Select the MySQL preference pane by + clicking the MySQL logo within the bottom section of the + preference panes list. -2.4.5. Using the Bundled MySQL on Mac OS X Server + Figure 2.51 MySQL Preference Pane: Location + MySQL Preference Pane: Location - If you are running Mac OS X Server, a version of MySQL should - already be installed. The following table shows the versions of - MySQL that ship with Mac OS X Server versions. - - Table 2.10. MySQL Versions Preinstalled with Mac OS X Server - Mac OS X Server Version MySQL Version - 10.2-10.2.2 3.23.51 - 10.2.3-10.2.6 3.23.53 - 10.3 4.0.14 - 10.3.2 4.0.16 - 10.4.0 4.1.10a - 10.5.0 5.0.45 - 10.6.0 5.0.82 + The MySQL Preference Pane shows the current status of the + MySQL server, showing stopped (in red) if the server is not + running and running (in green) if the server has already been + started. The preference pane also shows the current setting + for whether the MySQL server has been set to start + automatically. - The following table shows the installation layout of MySQL on Mac - OS X Server. + * To start the MySQL server using the preference pane: + Click Start MySQL Server. You may be prompted for the + username and password of a user with administrator + privileges to start the MySQL server. - Table 2.11. MySQL Directory Layout for Preinstalled MySQL - Installations on Mac OS X Server - Directory Contents of Directory - /usr/bin Client programs - /var/mysql Log files, databases - /usr/libexec The mysqld server - /usr/share/man Unix manual pages - /usr/share/mysql/mysql-test MySQL test suite - /usr/share/mysql Miscellaneous support files, including error - messages, character set files, sample configuration files, SQL for - database installation - /var/mysql/mysql.sock Location of the MySQL Unix socket + * To stop the MySQL server using the preference pane: + Click Stop MySQL Server. You may be prompted for the + username and password of a user with administrator + privileges to stop the MySQL server. -Additional Resources + * To automatically start the MySQL server when the system + boots: + Check the check box next to Automatically Start MySQL + Server on Startup. + * To disable automatic MySQL server startup when the system + boots: + Uncheck the check box next to Automatically Start MySQL + Server on Startup. - * For more information on managing the bundled MySQL instance in - Mac OS X Server 10.5, see Mac OS X Server: Web Technologies - Administration For Version 10.5 Leopard - (http://images.apple.com/server/macosx/docs/Web_Technologies_A - dmin_v10.5.pdf). - - * For more information on managing the bundled MySQL instance in - Mac OS X Server 10.6, see Mac OS X Server: Web Technologies - Administration Version 10.6 Snow Leopard - (http://manuals.info.apple.com/en_US/WebTech_v10.6.pdf). - - * The MySQL server bundled with Mac OS X Server does not include - the MySQL client libraries and header files required to access - and use MySQL from a third-party driver, such as Perl DBI or - PHP. For more information on obtaining and installing MySQL - libraries, see Mac OS X Server version 10.5: MySQL libraries - available for download (http://support.apple.com/kb/TA25017). - Alternatively, you can ignore the bundled MySQL server and - install MySQL from the package or tarball installation. + You can close the System Preferences... window once you have + completed your settings. -2.5. Installing MySQL on Linux +2.5 Installing MySQL on Linux Linux supports a number of different solutions for installing - MySQL. The recommended method is to use one of the distributions - from Oracle. If you choose this method, there are several options - available: - - * Installing from a generic binary package in .tar.gz format. - See Section 2.2, "Installing MySQL on Unix/Linux Using Generic - Binaries" for more information. - - * Extracting and compiling MySQL from a source distribution. For - detailed instructions, see Section 2.10, "Installing MySQL - from Source." + MySQL. The recommended method is to use one of the + distributions from Oracle. If you choose this method, there + are several options available: + + * Installing from a generic binary package in .tar.gz + format. See Section 2.2, "Installing MySQL on Unix/Linux + Using Generic Binaries" for more information. + + * Extracting and compiling MySQL from a source + distribution. For detailed instructions, see Section 2.9, + "Installing MySQL from Source." * Installing using a precompiled RPM package. For more - information, see Section 2.5.1, "Installing MySQL on Linux - Using RPM Packages." + information, see Section 2.5.1, "Installing MySQL on + Linux Using RPM Packages." * Installing using a precompiled Debian package. For more - information, see Section 2.5.2, "Installing MySQL on Linux - Using Debian Packages." + information, see Section 2.5.2, "Installing MySQL on + Linux Using Debian Packages." - * Installing using Oracle's Unbreakable Linux Network (ULN). For - more information, see Section 2.6, "Installing MySQL Using - Unbreakable Linux Network (ULN)." - - As an alternative, you can use the native package manager within - your Linux distribution to automatically download and install - MySQL for you. Native package installations can take care of the - download and dependencies required to run MySQL, but the MySQL - version will often be some versions behind the currently available - release. You will also normally be unable to install development - releases, as these are not usually made available in the native - repository. For more information on using the native package - installers, see Section 2.5.3, "Installing MySQL on Linux Using - Native Package Managers." - Note - - For many Linux installations, you will want to set up MySQL to be - started automatically when your machine starts. Many of the native - package installations perform this operation for you, but for - source, binary and RPM solutions you may need to set this up - separately. The required script, mysql.server, can be found in the - support-files directory under the MySQL installation directory or - in a MySQL source tree. You can install it as /etc/init.d/mysql - for automatic MySQL startup and shutdown. See Section 2.11.1.2, - "Starting and Stopping MySQL Automatically." + * Installing using Oracle's Unbreakable Linux Network + (ULN). For more information, see Section 2.6, "Installing + MySQL Using Unbreakable Linux Network (ULN)." + + As an alternative, you can use the native package manager + within your Linux distribution to automatically download and + install MySQL for you. Native package installations can take + care of the download and dependencies required to run MySQL, + but the MySQL version will often be some versions behind the + currently available release. You will also normally be unable + to install development releases, as these are not usually + made available in the native repository. For more information + on using the native package installers, see Section 2.5.3, + "Installing MySQL on Linux Using Native Package Managers." + Note + + For many Linux installations, you will want to set up MySQL + to be started automatically when your machine starts. Many of + the native package installations perform this operation for + you, but for source, binary and RPM solutions you may need to + set this up separately. The required script, mysql.server, + can be found in the support-files directory under the MySQL + installation directory or in a MySQL source tree. You can + install it as /etc/init.d/mysql for automatic MySQL startup + and shutdown. See Section 2.10.3, "Starting and Stopping + MySQL Automatically." -2.5.1. Installing MySQL on Linux Using RPM Packages +2.5.1 Installing MySQL on Linux Using RPM Packages Note - To install or upgrade to MySQL 5.5.31, be sure to read the special - instructions at the end of this section. + To install or upgrade to MySQL 5.5.31, be sure to read the + special instructions at the end of this section. The recommended way to install MySQL on RPM-based Linux distributions is by using the RPM packages. The RPMs that we - provide to the community should work on all versions of Linux that - support RPM packages and use glibc 2.3. To obtain RPM packages, - see Section 2.1.3, "How to Get MySQL." + provide to the community should work on all versions of Linux + that support RPM packages and use glibc 2.3. To obtain RPM + packages, see Section 2.1.2, "How to Get MySQL." - For non-RPM Linux distributions, you can install MySQL using a - .tar.gz package. See Section 2.2, "Installing MySQL on Unix/Linux - Using Generic Binaries." + For non-RPM Linux distributions, you can install MySQL using + a .tar.gz package. See Section 2.2, "Installing MySQL on + Unix/Linux Using Generic Binaries." - Installations created from our Linux RPM distributions result in - files under the system directories shown in the following table. + Installations created from our Linux RPM distributions result + in files under the system directories shown in the following + table. - Table 2.12. MySQL Installation Layout for Linux RPM Packages + Table 2.9 MySQL Installation Layout for Linux RPM Packages Directory Contents of Directory /usr/bin Client programs and scripts /usr/sbin The mysqld server @@ -4315,93 +4763,141 @@ /usr/include/mysql Include (header) files /usr/lib/mysql Libraries /usr/share/mysql Miscellaneous support files, including error - messages, character set files, sample configuration files, SQL for - database installation + messages, character set files, sample configuration files, + SQL for database installation /usr/share/sql-bench Benchmarks Note - RPM distributions of MySQL are also provided by other vendors. Be - aware that they may differ from those built by us in features, - capabilities, and conventions (including communication setup), and - that the instructions in this manual do not necessarily apply to - installing them. The vendor's instructions should be consulted - instead. Because of these differences, RPM packages built by us - check whether such RPMs built by other vendors are installed. If - so, the RPM does not install and produces a message explaining - this. + RPM distributions of MySQL are also provided by other + vendors. Be aware that they may differ from those built by us + in features, capabilities, and conventions (including + communication setup), and that the instructions in this + manual do not necessarily apply to installing them. The + vendor's instructions should be consulted instead. Because of + these differences, RPM packages built by us check whether + such RPMs built by other vendors are installed. If so, the + RPM does not install and produces a message explaining this. + + Conflicts can arise when an RPM from another vendor is + already installed, such as when a vendor's convention about + which files belong with the server and which belong with the + client library differ from the breakdown used for Oracle + packages. In such cases, attempts to install an Oracle RPM + with rpm -i may result in messages that files in the RPM to + be installed conflict with files from an installed package + (denoted mysql-libs in the following paragraphs). + + We provide a MySQL-shared-compat package with each MySQL + release. This package is meant to replace mysql-libs and + provides a replacement-compatible client library for older + MySQL series. MySQL-shared-compat is set up to make + mysql-libs obsolete, but rpm explicitly refuses to replace + obsoleted packages when invoked with -i (unlike -U), which is + why installation with rpm -i produces a conflict. + + MySQL-shared-compat can safely be installed alongside + mysql-libs because libraries are installed to different + locations. Therefore, it is possible to install shared-compat + first, then manually remove mysql-libs before continuing with + the installation. After mysql-libs is removed, the dynamic + linker stops looking for the client library in the location + where mysql-libs puts it, and the library provided by the + MySQL-shared-compat package takes over. + + Another alternative is to install packages using yum. In a + directory containing all RPM packages for a MySQL release, + yum install MySQL*rpm installs them in the correct order and + removes mysql-libs in one step without conflicts. In most cases, you need to install only the MySQL-server and - MySQL-client packages to get a functional MySQL installation. The - other packages are not required for a standard installation. + MySQL-client packages to get a functional MySQL installation. + The other packages are not required for a standard + installation. - RPMs for MySQL Cluster. Standard MySQL server RPMs built by MySQL - do not provide support for the NDBCLUSTER storage engine. + RPMs for MySQL Cluster. Standard MySQL server RPMs built by + MySQL do not provide support for the NDBCLUSTER storage + engine. Important - When upgrading a MySQL Cluster RPM installation, you must upgrade - all installed RPMs, including the Server and Client RPMs. - - For more information about installing MySQL Cluster from RPMs, see - Section 17.2, "MySQL Cluster Installation and Upgrades." + When upgrading a MySQL Cluster RPM installation, you must + upgrade all installed RPMs, including the Server and Client + RPMs. + + For more information about installing MySQL Cluster from + RPMs, see Section 18.2, "MySQL Cluster Installation and + Upgrades." For upgrades, if your installation was originally produced by - installing multiple RPM packages, it is best to upgrade all the - packages, not just some. For example, if you previously installed - the server and client RPMs, do not upgrade just the server RPM. + installing multiple RPM packages, it is best to upgrade all + the packages, not just some. For example, if you previously + installed the server and client RPMs, do not upgrade just the + server RPM. + + If the data directory exists at RPM installation time, the + installation process does not modify existing data. This has + the effect, for example, that accounts in the grant tables + are not initialized to the default set of accounts. If you get a dependency failure when trying to install MySQL - packages (for example, error: removing these packages would break - dependencies: libmysqlclient.so.10 is needed by ...), you should - also install the MySQL-shared-compat package, which includes the - shared libraries for older releases for backward compatibility. - - The RPM packages shown in the following list are available. The - names shown here use a suffix of .glibc23.i386.rpm, but particular - packages can have different suffixes, described later. + packages (for example, error: removing these packages would + break dependencies: libmysqlclient.so.10 is needed by ...), + you should also install the MySQL-shared-compat package, + which includes the shared libraries for older releases for + backward compatibility. + + The RPM packages shown in the following list are available. + The names shown here use a suffix of .glibc23.i386.rpm, but + particular packages can have different suffixes, described + later. If you plan to install multiple RPM packages, you may + wish to download the RPM Bundle tar file instead, which + contains multiple RPM packages to that you need not download + them separately. * MySQL-server-VERSION.glibc23.i386.rpm The MySQL server. You need this unless you only want to connect to a MySQL server running on another machine. * MySQL-client-VERSION.glibc23.i386.rpm - The standard MySQL client programs. You probably always want - to install this package. + The standard MySQL client programs. You probably always + want to install this package. * MySQL-devel-VERSION.glibc23.i386.rpm - The libraries and include files that are needed if to compile - other MySQL clients, such as the Perl modules. Install this - RPM if you intend to compile C API applications. + The libraries and include files that are needed if to + compile other MySQL clients, such as the Perl modules. + Install this RPM if you intend to compile C API + applications. * MySQL-shared-VERSION.glibc23.i386.rpm This package contains the shared libraries - (libmysqlclient.so*) that certain languages and applications - need to dynamically load and use MySQL. It contains - single-threaded and thread-safe libraries. Install this RPM if - you intend to compile or run C API applications that depend on - the shared client library. Prior to MySQL 5.5.6, if you - install this package, do not install the MySQL-shared-compat - package. + (libmysqlclient.so*) that certain languages and + applications need to dynamically load and use MySQL. It + contains single-threaded and thread-safe libraries. + Install this RPM if you intend to compile or run C API + applications that depend on the shared client library. + Prior to MySQL 5.5.6, if you install this package, do not + install the MySQL-shared-compat package. * MySQL-shared-compat-VERSION.glibc23.i386.rpm - This package includes the shared libraries for older releases. - It contains single-threaded and thread-safe libraries. Install - this package if you have applications installed that are - dynamically linked against older versions of MySQL but you - want to upgrade to the current version without breaking the - library dependencies. Before MySQL 5.5.6, MySQL-shared-compat - also includes the libraries for the current release, so if you - install it, you should not also install MySQL-shared. As of - 5.5.6, MySQL-shared-compat does not include the current - library version, so there is no conflict. + This package includes the shared libraries for older + releases. It contains single-threaded and thread-safe + libraries. Install this package if you have applications + installed that are dynamically linked against older + versions of MySQL but you want to upgrade to the current + version without breaking the library dependencies. Before + MySQL 5.5.6, MySQL-shared-compat also includes the + libraries for the current release, so if you install it, + you should not also install MySQL-shared. As of 5.5.6, + MySQL-shared-compat does not include the current library + version, so there is no conflict. As of MySQL 5.5.23, the MySQL-shared-compat RPM package - enables users of Red Hat-provided mysql-*-5.1 RPM packages to - migrate to Oracle-provided MySQL-*-5.5 packages. - MySQL-shared-compat replaces the Red Hat mysql-libs package by - replacing libmysqlclient.so files of the latter package, thus - satisfying dependencies of other packages on mysql-libs. This - change affects only users of Red Hat (or Red Hat-compatible) - RPM packages. Nothing is different for users of Oracle RPM - packages. + enables users of Red Hat-provided mysql-*-5.1 RPM + packages to migrate to Oracle-provided MySQL-*-5.5 + packages. MySQL-shared-compat replaces the Red Hat + mysql-libs package by replacing libmysqlclient.so files + of the latter package, thus satisfying dependencies of + other packages on mysql-libs. This change affects only + users of Red Hat (or Red Hat-compatible) RPM packages. + Nothing is different for users of Oracle RPM packages. * MySQL-embedded-VERSION.glibc23.i386.rpm The embedded MySQL server library. @@ -4411,210 +4907,226 @@ * MySQL-VERSION.src.rpm This contains the source code for all of the previous - packages. It can also be used to rebuild the RPMs on other - architectures (for example, Alpha or SPARC). + packages. It can also be used to rebuild the RPMs on + other architectures (for example, Alpha or SPARC). - The suffix of RPM package names (following the VERSION value) has - the following syntax: + The suffix of RPM package names (following the VERSION value) + has the following syntax: .PLATFORM.CPU.rpm - The PLATFORM and CPU values indicate the type of system for which - the package is built. PLATFORM indicates the platform and CPU - indicates the processor type or family. + The PLATFORM and CPU values indicate the type of system for + which the package is built. PLATFORM indicates the platform + and CPU indicates the processor type or family. All packages are dynamically linked against glibc 2.3. The PLATFORM value indicates whether the package is platform - independent or intended for a specific platform, as shown in the - following table. + independent or intended for a specific platform, as shown in + the following table. - Table 2.13. MySQL Linux Installation Packages + Table 2.10 MySQL Linux Installation Packages PLATFORM Value Intended Use - glibc23 Platform independent, should run on any Linux distribution - that supports glibc 2.3 + glibc23 Platform independent, should run on any Linux + distribution that supports glibc 2.3 rhel4, rhel5 Red Hat Enterprise Linux 4 or 5 el6 Enterprise Linux 6 sles10, sles11 SuSE Linux Enterprise Server 10 or 11 In MySQL 5.5, only glibc23 packages are available currently. - The CPU value indicates the processor type or family for which the - package is built. + The CPU value indicates the processor type or family for + which the package is built. - Table 2.14. MySQL Installation Packages for Linux CPU Identifiers + Table 2.11 MySQL Installation Packages for Linux CPU + Identifiers CPU Value Intended Processor Type or Family i386, i586, i686 Pentium processor or better, 32 bit x86_64 64-bit x86 processor ia64 Itanium (IA-64) processor - To see all files in an RPM package (for example, a MySQL-server - RPM), run a command like this: + To see all files in an RPM package (for example, a + MySQL-server RPM), run a command like this: shell> rpm -qpl MySQL-server-VERSION.glibc23.i386.rpm - To perform a standard minimal installation, install the server and - client RPMs: + To perform a standard minimal installation, install the + server and client RPMs: shell> rpm -i MySQL-server-VERSION.glibc23.i386.rpm shell> rpm -i MySQL-client-VERSION.glibc23.i386.rpm - To install only the client programs, install just the client RPM: + To install only the client programs, install just the client + RPM: shell> rpm -i MySQL-client-VERSION.glibc23.i386.rpm - RPM provides a feature to verify the integrity and authenticity of - packages before installing them. To learn more about this feature, - see Section 2.1.4, "Verifying Package Integrity Using MD5 - Checksums or GnuPG." - - The server RPM places data under the /var/lib/mysql directory. The - RPM also creates a login account for a user named mysql (if one - does not exist) to use for running the MySQL server, and creates - the appropriate entries in /etc/init.d/ to start the server - automatically at boot time. (This means that if you have performed - a previous installation and have made changes to its startup - script, you may want to make a copy of the script so that you do - not lose it when you install a newer RPM.) See Section 2.11.1.2, - "Starting and Stopping MySQL Automatically," for more information - on how MySQL can be started automatically on system startup. - - In MySQL 5.5.5 and later, during a new installation, the server - boot scripts are installed, but the MySQL server is not started at - the end of the installation, since the status of the server during - an unattended installation is not known. - - In MySQL 5.5.5 and later, during an upgrade installation using the - RPM packages, if the MySQL server is running when the upgrade - occurs, the MySQL server is stopped, the upgrade occurs, and the - MySQL server is restarted. If the MySQL server is not already - running when the RPM upgrade occurs, the MySQL server is not - started at the end of the installation. + RPM provides a feature to verify the integrity and + authenticity of packages before installing them. To learn + more about this feature, see Section 2.1.3, "Verifying + Package Integrity Using MD5 Checksums or GnuPG." + + The server RPM places data under the /var/lib/mysql + directory. The RPM also creates a login account for a user + named mysql (if one does not exist) to use for running the + MySQL server, and creates the appropriate entries in + /etc/init.d/ to start the server automatically at boot time. + (This means that if you have performed a previous + installation and have made changes to its startup script, you + may want to make a copy of the script so that you do not lose + it when you install a newer RPM.) See Section 2.10.3, + "Starting and Stopping MySQL Automatically," for more + information on how MySQL can be started automatically on + system startup. + + In MySQL 5.5.5 and later, during a new installation, the + server boot scripts are installed, but the MySQL server is + not started at the end of the installation, since the status + of the server during an unattended installation is not known. + + In MySQL 5.5.5 and later, during an upgrade installation + using the RPM packages, if the MySQL server is running when + the upgrade occurs, the MySQL server is stopped, the upgrade + occurs, and the MySQL server is restarted. If the MySQL + server is not already running when the RPM upgrade occurs, + the MySQL server is not started at the end of the + installation. If something goes wrong, you can find more information in the - binary installation section. See Section 2.2, "Installing MySQL on - Unix/Linux Using Generic Binaries." + binary installation section. See Section 2.2, "Installing + MySQL on Unix/Linux Using Generic Binaries." Note - The accounts that are listed in the MySQL grant tables initially - have no passwords. After starting the server, you should set up - passwords for them using the instructions in Section 2.11, - "Postinstallation Setup and Testing." + The accounts that are listed in the MySQL grant tables + initially have no passwords. After starting the server, you + should set up passwords for them using the instructions in + Section 2.10, "Postinstallation Setup and Testing." During RPM installation, a user named mysql and a group named - mysql are created on the system. This is done using the useradd, - groupadd, and usermod commands. Those commands require appropriate - administrative privileges, which is required for locally managed - users and groups (as listed in the /etc/passwd and /etc/group - files) by the RPM installation process being run by root. - - If you log in as the mysql user, you may find that MySQL displays - "Invalid (old?) table or database name" errors that mention - .mysqlgui, lost+found, .mysqlgui, .bash_history, .fonts.cache-1, - .lesshst, .mysql_history, .profile, .viminfo, and similar files - created by MySQL or operating system utilities. You can safely - ignore these error messages or remove the files or directories - that cause them if you do not need them. + mysql are created on the system. This is done using the + useradd, groupadd, and usermod commands. Those commands + require appropriate administrative privileges, which is + required for locally managed users and groups (as listed in + the /etc/passwd and /etc/group files) by the RPM installation + process being run by root. + + If you log in as the mysql user, you may find that MySQL + displays "Invalid (old?) table or database name" errors that + mention .mysqlgui, lost+found, .mysqlgui, .bash_history, + .fonts.cache-1, .lesshst, .mysql_history, .profile, .viminfo, + and similar files created by MySQL or operating system + utilities. You can safely ignore these error messages or + remove the files or directories that cause them if you do not + need them. For nonlocal user management (LDAP, NIS, and so forth), the - administrative tools may require additional authentication (such - as a password), and will fail if the installing user does not - provide this authentication. Even if they fail, the RPM - installation will not abort but succeed, and this is intentional. - If they failed, some of the intended transfer of ownership may be - missing, and it is recommended that the system administrator then - manually ensures some appropriate user and group exists and - manually transfers ownership following the actions in the RPM spec - file. + administrative tools may require additional authentication + (such as a password), and will fail if the installing user + does not provide this authentication. Even if they fail, the + RPM installation will not abort but succeed, and this is + intentional. If they failed, some of the intended transfer of + ownership may be missing, and it is recommended that the + system administrator then manually ensures some appropriate + user and group exists and manually transfers ownership + following the actions in the RPM spec file. - In MySQL 5.5.31, the RPM spec file has been updated, which has the - following consequences: + In MySQL 5.5.31, the RPM spec file has been updated, which + has the following consequences: * For a non-upgrade installation (no existing MySQL version installed), it possible to install MySQL using yum. - * For upgrades, it is necessary to clean up any earlier MySQL - installations. In effect, the update is performed by removing - the old installations and installing the new one. + * For upgrades, it is necessary to clean up any earlier + MySQL installations. In effect, the update is performed + by removing the old installations and installing the new + one. Additional details follow. - For a non-upgrade installation of MySQL 5.5.31, it is possible to - install using yum: + For a non-upgrade installation of MySQL 5.5.31, it is + possible to install using yum: shell> yum install MySQL-server-NEWVERSION.glibc23.i386.rpm - For upgrades to MySQL 5.5.31, the upgrade is performed by removing - the old installation and installing the new one. To do this, use - the following procedure: + For upgrades to MySQL 5.5.31, the upgrade is performed by + removing the old installation and installing the new one. To + do this, use the following procedure: 1. Remove the existing 5.5.X installation. OLDVERSION is the version to remove. shell> rpm -e MySQL-server-OLDVERSION.glibc23.i386.rpm + Repeat this step for all installed MySQL RPMs. - 2. Install the new version. NEWVERSION is the version to install. + 2. Install the new version. NEWVERSION is the version to + install. shell> rpm -ivh MySQL-server-NEWVERSION.glibc23.i386.rpm - Alternatively, the removal and installation can be done using yum: + Alternatively, the removal and installation can be done using + yum: shell> yum remove MySQL-server-OLDVERSION.glibc23.i386.rpm shell> yum install MySQL-server-NEWVERSION.glibc23.i386.rpm -2.5.2. Installing MySQL on Linux Using Debian Packages +2.5.2 Installing MySQL on Linux Using Debian Packages Oracle provides Debian packages for installation on Debian or - Debian-like Linux systems. To obtain a package, see Section 2.1.3, - "How to Get MySQL." + Debian-like Linux systems. To obtain a package, see Section + 2.1.2, "How to Get MySQL." Note - Debian distributions of MySQL are also provided by other vendors. - Be aware that they may differ from those built by us in features, - capabilities, and conventions (including communication setup), and - that the instructions in this manual do not necessarily apply to - installing them. The vendor's instructions should be consulted - instead. - - Debian package files have names in mysql-MVER-DVER-CPU.deb format. - MVER is the MySQL version and DVER is the Debian version. The CPU - value indicates the processor type or family for which the package - is built, as shown in the following table. + Debian distributions of MySQL are also provided by other + vendors. Be aware that they may differ from those built by us + in features, capabilities, and conventions (including + communication setup), and that the instructions in this + manual do not necessarily apply to installing them. The + vendor's instructions should be consulted instead. + + Debian package files have names in mysql-MVER-DVER-CPU.deb + format. MVER is the MySQL version and DVER is the Debian + version. The CPU value indicates the processor type or family + for which the package is built, as shown in the following + table. - Table 2.15. MySQL Installation Packages for Linux CPU Identifiers + Table 2.12 MySQL Installation Packages for Linux CPU + Identifiers CPU Value Intended Processor Type or Family i686 Pentium processor or better, 32 bit x86_64 64-bit x86 processor - After downloading a Debian package, use the following command to - install it; + After downloading a Debian package, use the following command + to install it; shell> dpkg -i mysql-MVER-DVER-CPU.deb - The Debian package installs files in the /opt/mysql/server-5.5 - directory. + The Debian package installs files in the + /opt/mysql/server-5.5 directory. You may also need to install the libaio library if it is not already present on your system: -shell> apt-get install libaio1 +shell> sudo apt-get install libaio1 -2.5.3. Installing MySQL on Linux Using Native Package Managers +2.5.3 Installing MySQL on Linux Using Native Package Managers - Many Linux distributions include a version of the MySQL server, - client tools, and development components into the standard package - management system built into distributions such as Fedora, Debian, - Ubuntu, and Gentoo. This section provides basic instructions for - installing MySQL using these systems. + Many Linux distributions include a version of the MySQL + server, client tools, and development components into the + standard package management system built into distributions + such as Fedora, Debian, Ubuntu, and Gentoo. This section + provides basic instructions for installing MySQL using these + systems. Important - Native package installations can take care of the download and - dependencies required to run MySQL, but the MySQL version will - often be some way behind the currently available release. You will - also normally be unable to install development releases, as these - are not usually made available in the native repository. + Native package installations can take care of the download + and dependencies required to run MySQL, but the MySQL version + will often be some way behind the currently available + release. You will also normally be unable to install + development releases, as these are not usually made available + in the native repository. Distribution specific instructions are shown below: * Red Hat Linux, Fedora, CentOS - For Red Hat and similar distributions, the MySQL distribution - is divided into a number of separate packages, mysql for the - client tools, mysql-server for the server and associated - tools, and mysql-libs for the libraries. The libraries are - required if you want to provide connectivity from different - languages and environments such as Perl, Python and others. - To install, use the yum command to specify the packages that - you want to install. For example: + For Red Hat and similar distributions, the MySQL + distribution is divided into a number of separate + packages, mysql for the client tools, mysql-server for + the server and associated tools, and mysql-libs for the + libraries. The libraries are required if you want to + provide connectivity from different languages and + environments such as Perl, Python and others. + To install, use the yum command to specify the packages + that you want to install. For example: root-shell> yum install mysql mysql-server mysql-libs mysql-server Loaded plugins: presto, refresh-packagekit Setting up Install Process @@ -4623,34 +5135,34 @@ ---> Package mysql.x86_64 0:5.1.48-2.fc13 set to be updated ---> Package mysql-libs.x86_64 0:5.1.48-2.fc13 set to be updated ---> Package mysql-server.x86_64 0:5.1.48-2.fc13 set to be updated ---> Processing Dependency: perl-DBD-MySQL for package: mysql-server-5 -.1.48-2.fc13.x86_64 +--> Processing Dependency: perl-DBD-MySQL for package: mysql-server-5. +1.48-2.fc13.x86_64 --> Running transaction check ---> Package perl-DBD-MySQL.x86_64 0:4.017-1.fc13 set to be updated --> Finished Dependency Resolution Dependencies Resolved -===================================================================== -=========== +====================================================================== +========== Package Arch Version Repository - Size -===================================================================== -=========== + Size +====================================================================== +========== Installing: mysql x86_64 5.1.48-2.fc13 updates - 889 k + 889 k mysql-libs x86_64 5.1.48-2.fc13 updates - 1.2 M + 1.2 M mysql-server x86_64 5.1.48-2.fc13 updates - 8.1 M + 8.1 M Installing for dependencies: perl-DBD-MySQL x86_64 4.017-1.fc13 updates - 136 k + 136 k Transaction Summary -===================================================================== -=========== +====================================================================== +========== Install 4 Package(s) Upgrade 0 Package(s) @@ -4662,33 +5174,33 @@ Processing delta metadata Package(s) data still to download: 10 M (1/4): mysql-5.1.48-2.fc13.x86_64.rpm | 889 kB - 00:04 +00:04 (2/4): mysql-libs-5.1.48-2.fc13.x86_64.rpm | 1.2 MB - 00:06 +00:06 (3/4): mysql-server-5.1.48-2.fc13.x86_64.rpm | 8.1 MB - 00:40 +00:40 (4/4): perl-DBD-MySQL-4.017-1.fc13.x86_64.rpm | 136 kB - 00:00 ---------------------------------------------------------------------- ------------ +00:00 +---------------------------------------------------------------------- +---------- Total 201 kB/s | 10 MB - 00:52 +00:52 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Installing : mysql-libs-5.1.48-2.fc13.x86_64 - 1/4 + 1/4 Installing : mysql-5.1.48-2.fc13.x86_64 - 2/4 + 2/4 Installing : perl-DBD-MySQL-4.017-1.fc13.x86_64 - 3/4 + 3/4 Installing : mysql-server-5.1.48-2.fc13.x86_64 - 4/4 + 4/4 Installed: - mysql.x86_64 0:5.1.48-2.fc13 mysql-libs.x86_64 0:5.1.48- -2.fc13 + mysql.x86_64 0:5.1.48-2.fc13 mysql-libs.x86_64 0:5.1.48-2 +.fc13 mysql-server.x86_64 0:5.1.48-2.fc13 Dependency Installed: @@ -4696,73 +5208,76 @@ Complete! - MySQL and the MySQL server should now be installed. A sample - configuration file is installed into /etc/my.cnf. An init - script, to start and stop the server, will have been installed - into /etc/init.d/mysqld. To start the MySQL server use - service: + + MySQL and the MySQL server should now be installed. A + sample configuration file is installed into /etc/my.cnf. + An init script, to start and stop the server, will have + been installed into /etc/init.d/mysqld. To start the + MySQL server use service: root-shell> service mysqld start - To enable the server to be started and stopped automatically - during boot, use chkconfig: + + To enable the server to be started and stopped + automatically during boot, use chkconfig: root-shell> chkconfig --levels 235 mysqld on - Which enables the MySQL server to be started (and stopped) - automatically at the specified the run levels. - The database tables will have been automatically created for - you, if they do not already exist. You should, however, run - mysql_secure_installation to set the root passwords on your - server. + + Which enables the MySQL server to be started (and + stopped) automatically at the specified the run levels. + The database tables will have been automatically created + for you, if they do not already exist. You should, + however, run mysql_secure_installation to set the root + passwords on your server. * Debian, Ubuntu, Kubuntu - On Debian and related distributions, there are two packages, - mysql-client and mysql-server, for the client and server - components respectively. You should specify an explicit - version, for example mysql-client-5.1, to ensure that you - install the version of MySQL that you want. - To download and install, including any dependencies, use the - apt-get command, specifying the packages that you want to - install. + On Debian and related distributions, there are two + packages, mysql-client and mysql-server, for the client + and server components respectively. You should specify an + explicit version, for example mysql-client-5.1, to ensure + that you install the version of MySQL that you want. + To download and install, including any dependencies, use + the apt-get command, specifying the packages that you + want to install. Note Before installing, make sure that you update your apt-get - index files to ensure you are downloading the latest available - version. - A sample installation of the MySQL packages might look like - this (some sections trimmed for clarity): + index files to ensure you are downloading the latest + available version. + A sample installation of the MySQL packages might look + like this (some sections trimmed for clarity): root-shell> apt-get install mysql-client-5.1 mysql-server-5.1 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer - required: +required: linux-headers-2.6.28-11 linux-headers-2.6.28-11-generic Use 'apt-get autoremove' to remove them. The following extra packages will be installed: bsd-mailx libdbd-mysql-perl libdbi-perl libhtml-template-perl - libmysqlclient15off libmysqlclient16 libnet-daemon-perl libplrpc-pe -rl mailx + libmysqlclient15off libmysqlclient16 libnet-daemon-perl libplrpc-per +l mailx mysql-common postfix Suggested packages: - dbishell libipc-sharedcache-perl tinyca procmail postfix-mysql post -fix-pgsql + dbishell libipc-sharedcache-perl tinyca procmail postfix-mysql postf +ix-pgsql postfix-ldap postfix-pcre sasl2-bin resolvconf postfix-cdb The following NEW packages will be installed bsd-mailx libdbd-mysql-perl libdbi-perl libhtml-template-perl - libmysqlclient15off libmysqlclient16 libnet-daemon-perl libplrpc-pe -rl mailx + libmysqlclient15off libmysqlclient16 libnet-daemon-perl libplrpc-per +l mailx mysql-client-5.1 mysql-common mysql-server-5.1 postfix 0 upgraded, 13 newly installed, 0 to remove and 182 not upgraded. Need to get 1907kB/25.3MB of archives. After this operation, 59.5MB of additional disk space will be used. Do you want to continue [Y/n]? Y -Get: 1 http://gb.archive.ubuntu.com jaunty-updates/main mysql-common -5.1.30really5.0.75-0ubuntu10.5 [63.6kB] -Get: 2 http://gb.archive.ubuntu.com jaunty-updates/main libmysqlclien -t15off 5.1.30really5.0.75-0ubuntu10.5 [1843kB] +Get: 1 http://gb.archive.ubuntu.com jaunty-updates/main mysql-common 5 +.1.30really5.0.75-0ubuntu10.5 [63.6kB] +Get: 2 http://gb.archive.ubuntu.com jaunty-updates/main libmysqlclient +15off 5.1.30really5.0.75-0ubuntu10.5 [1843kB] Fetched 1907kB in 9s (205kB/s) Preconfiguring packages ... Selecting previously deselected package mysql-common. -(Reading database ... 121260 files and directories currently installe -d.) +(Reading database ... 121260 files and directories currently installed +.) ... Processing 1 added doc-base file(s)... Registering documents with scrollkeeper... @@ -4782,48 +5297,50 @@ ...done. 100825 11:46:15 InnoDB: Started; log sequence number 0 46409 100825 11:46:15 InnoDB: Starting shutdown... -100825 11:46:17 InnoDB: Shutdown completed; log sequence number 0 46 -409 +100825 11:46:17 InnoDB: Shutdown completed; log sequence number 0 464 +09 100825 11:46:17 [Warning] Forcing shutdown of 1 plugins * Starting MySQL database server mysqld ...done. - * Checking for corrupt, not cleanly closed and upgrade needing table -s. + * Checking for corrupt, not cleanly closed and upgrade needing tables +. ... Processing triggers for libc6 ... ldconfig deferred processing now taking place + Note The apt-get command will install a number of packages, - including the MySQL server, in order to provide the typical - tools and application environment. This can mean that you - install a large number of packages in addition to the main - MySQL package. - During installation, the initial database will be created, and - you will be prompted for the MySQL root password (and - confirmation). A configuration file will have been created in - /etc/mysql/my.cnf. An init script will have been created in - /etc/init.d/mysql. - The server will already be started. You can manually start and - stop the server using: + including the MySQL server, in order to provide the + typical tools and application environment. This can mean + that you install a large number of packages in addition + to the main MySQL package. + During installation, the initial database will be + created, and you will be prompted for the MySQL root + password (and confirmation). A configuration file will + have been created in /etc/mysql/my.cnf. An init script + will have been created in /etc/init.d/mysql. + The server will already be started. You can manually + start and stop the server using: root-shell> service mysql [start|stop] - The service will automatically be added to the 2, 3 and 4 run - levels, with stop scripts in the single, shutdown and restart - levels. + + The service will automatically be added to the 2, 3 and 4 + run levels, with stop scripts in the single, shutdown and + restart levels. * Gentoo Linux - As a source-based distribution, installing MySQL on Gentoo - involves downloading the source, patching the Gentoo - specifics, and then compiling the MySQL server and installing - it. This process is handled automatically by the emerge - command. Depending on the version of MySQL that you want to - install, you may need to unmask the specific version that you - want for your chosen platform. - The MySQL server and client tools are provided within a single - package, dev-db/mysql. You can obtain a list of the versions - available to install by looking at the portage directory for - the package: + As a source-based distribution, installing MySQL on + Gentoo involves downloading the source, patching the + Gentoo specifics, and then compiling the MySQL server and + installing it. This process is handled automatically by + the emerge command. Depending on the version of MySQL + that you want to install, you may need to unmask the + specific version that you want for your chosen platform. + The MySQL server and client tools are provided within a + single package, dev-db/mysql. You can obtain a list of + the versions available to install by looking at the + portage directory for the package: root-shell> ls /usr/portage/dev-db/mysql/mysql-5.1* mysql-5.1.39-r1.ebuild mysql-5.1.44-r1.ebuild @@ -4833,356 +5350,294 @@ mysql-5.1.45-r1.ebuild mysql-5.1.45.ebuild mysql-5.1.46.ebuild + To install a specific MySQL version, you must specify the entire atom. For example: root-shell> emerge =dev-db/mysql-5.1.46 - A simpler alternative is to use the virtual/mysql-5.1 package, - which will install the latest version: + + A simpler alternative is to use the virtual/mysql-5.1 + package, which will install the latest version: root-shell> emerge =virtual/mysql-5.1 + If the package is masked (because it is not tested or - certified for the current platform), use the ACCEPT_KEYWORDS - environment variable. For example: + certified for the current platform), use the + ACCEPT_KEYWORDS environment variable. For example: root-shell> ACCEPT_KEYWORDS="~x86" emerge =virtual/mysql-5.1 - After installation, you should create a new database using - mysql_install_db, and set the password for the root user on - MySQL. You can use the configuration interface to set the - password and create the initial database: + + After installation, you should create a new database + using mysql_install_db, and set the password for the root + user on MySQL. You can use the configuration interface to + set the password and create the initial database: root-shell> emerge --config =dev-db/mysql-5.1.46 - A sample configuration file will have been created for you in - /etc/mysql/my.cnf, and an init script will have been created - in /etc/init.d/mysql. - To enable MySQL to start automatically at the normal (default) - run levels, you can use: + + A sample configuration file will have been created for + you in /etc/mysql/my.cnf, and an init script will have + been created in /etc/init.d/mysql. + To enable MySQL to start automatically at the normal + (default) run levels, you can use: root-shell> rc-update add mysql default -2.6. Installing MySQL Using Unbreakable Linux Network (ULN) +2.6 Installing MySQL Using Unbreakable Linux Network (ULN) Linux supports a number of different solutions for installing - MySQL, covered in Section 2.5, "Installing MySQL on Linux." One of - the methods, covered in this section, is installing from Oracles's - Unbreakable Linux Network (ULN). You can find information about - Oracle Linux and ULN under http://linux.oracle.com/. + MySQL, covered in Section 2.5, "Installing MySQL on Linux." + One of the methods, covered in this section, is installing + from Oracle's Unbreakable Linux Network (ULN). You can find + information about Oracle Linux and ULN under + http://linux.oracle.com/. To use ULN, you need to obtain a ULN login and register the machine used for installation with ULN. This is described in - detail in the ULN FAQ (https://linux.oracle.com/uln_faq.html). The - page also describes how to install and update packages.The MySQL - packages are in the "MySQL for Oracle Linux 6" channel for your - system architecture on ULN. + detail in the ULN FAQ + (https://linux.oracle.com/uln_faq.html). The page also + describes how to install and update packages.The MySQL + packages are in the "MySQL for Oracle Linux 6" channel for + your system architecture on ULN. Note - At the time of writing this (September 2012), ULN provides MySQL - 5.5 for Oracle Linux 6. - - Once MySQL has been installed using ULN, you can find information - on starting and stopping the server, and more, in this section, - particularly under Section 2.5.1, "Installing MySQL on Linux Using - RPM Packages." + At the time of this writing, ULN provides MySQL 5.5 for + Oracle Linux 6. + + Once MySQL has been installed using ULN, you can find + information on starting and stopping the server, and more, in + this section, particularly under Section 2.5.1, "Installing + MySQL on Linux Using RPM Packages." If you're updating an existing MySQL installation to an - installation using ULN, the recommended procedure is to export - your data using mysqldump, remove the existing installation, - install MySQL from ULN, and load the exported data into your - freshly installed MySQL. - - If the existing MySQL installation you're upgrading from is from a - previous release series (prior to MySQL 5.5), make sure to read - the section on upgrading MySQL, Section 2.12.1, "Upgrading MySQL." + installation using ULN, the recommended procedure is to + export your data using mysqldump, remove the existing + installation, install MySQL from ULN, and load the exported + data into your freshly installed MySQL. + + If the existing MySQL installation you're upgrading from is + from a previous release series (prior to MySQL 5.5), make + sure to read the section on upgrading MySQL, Section 2.11.1, + "Upgrading MySQL." -2.7. Installing MySQL on Solaris and OpenSolaris +2.7 Installing MySQL on Solaris and OpenSolaris MySQL on Solaris and OpenSolaris is available in a number of different formats. - * For information on installing using the native Solaris PKG - format, see Section 2.7.1, "Installing MySQL on Solaris Using - a Solaris PKG." + * For information on installing using the native Solaris + PKG format, see Section 2.7.1, "Installing MySQL on + Solaris Using a Solaris PKG." * On OpenSolaris, the standard package repositories include - MySQL packages specially built for OpenSolaris that include - entries for the Service Management Framework (SMF) to enable - control of the installation using the SMF administration - commands. For more information, see Section 2.7.2, "Installing - MySQL on OpenSolaris Using IPS." + MySQL packages specially built for OpenSolaris that + include entries for the Service Management Framework + (SMF) to enable control of the installation using the SMF + administration commands. For more information, see + Section 2.7.2, "Installing MySQL on OpenSolaris Using + IPS." * To use a standard tar binary installation, use the notes - provided in Section 2.2, "Installing MySQL on Unix/Linux Using - Generic Binaries." Check the notes and hints at the end of - this section for Solaris specific notes that you may need - before or after installation. + provided in Section 2.2, "Installing MySQL on Unix/Linux + Using Generic Binaries." Check the notes and hints at the + end of this section for Solaris specific notes that you + may need before or after installation. - To obtain a binary MySQL distribution for Solaris in tarball or - PKG format, http://dev.mysql.com/downloads/mysql/5.5.html. + To obtain a binary MySQL distribution for Solaris in tarball + or PKG format, http://dev.mysql.com/downloads/mysql/5.5.html. - Additional notes to be aware of when installing and using MySQL on - Solaris: + Additional notes to be aware of when installing and using + MySQL on Solaris: - * If you want to use MySQL with the mysql user and group, use - the groupadd and useradd commands: + * If you want to use MySQL with the mysql user and group, + use the groupadd and useradd commands: groupadd mysql useradd -g mysql mysql - * If you install MySQL using a binary tarball distribution on - Solaris, you may run into trouble even before you get the - MySQL distribution unpacked, as the Solaris tar cannot handle - long file names. This means that you may see errors when you - try to unpack MySQL. - If this occurs, you must use GNU tar (gtar) to unpack the - distribution. In Solaris 10 and OpenSolaris gtar is normally - located in /usr/sfw/bin/gtar, but may not be included in the - default path definition. - - * When using Solaris 10 for x86_64, you should mount any file - systems on which you intend to store InnoDB files with the - forcedirectio option. (By default mounting is done without - this option.) Failing to do so will cause a significant drop - in performance when using the InnoDB storage engine on this - platform. - * If you would like MySQL to start automatically, you can copy - support-files/mysql.server to /etc/init.d and create a - symbolic link to it named /etc/rc3.d/S99mysql.server. + * If you install MySQL using a binary tarball distribution + on Solaris, you may run into trouble even before you get + the MySQL distribution unpacked, as the Solaris tar + cannot handle long file names. This means that you may + see errors when you try to unpack MySQL. + If this occurs, you must use GNU tar (gtar) to unpack the + distribution. In Solaris 10 and OpenSolaris gtar is + normally located in /usr/sfw/bin/gtar, but may not be + included in the default path definition. + + * When using Solaris 10 for x86_64, you should mount any + file systems on which you intend to store InnoDB files + with the forcedirectio option. (By default mounting is + done without this option.) Failing to do so will cause a + significant drop in performance when using the InnoDB + storage engine on this platform. + + * If you would like MySQL to start automatically, you can + copy support-files/mysql.server to /etc/init.d and create + a symbolic link to it named /etc/rc3.d/S99mysql.server. - * If too many processes try to connect very rapidly to mysqld, - you should see this error in the MySQL log: + * If too many processes try to connect very rapidly to + mysqld, you should see this error in the MySQL log: Error in accept: Protocol error + You might try starting the server with the --back_log=50 option as a workaround for this. * To configure the generation of core files on Solaris you should use the coreadm command. Because of the security - implications of generating a core on a setuid() application, - by default, Solaris does not support core files on setuid() - programs. However, you can modify this behavior using coreadm. - If you enable setuid() core files for the current user, they - will be generated using the mode 600 and owned by the - superuser. - -2.7.1. Installing MySQL on Solaris Using a Solaris PKG - - You can install MySQL on Solaris and OpenSolaris using a binary - package using the native Solaris PKG format instead of the binary - tarball distribution. + implications of generating a core on a setuid() + application, by default, Solaris does not support core + files on setuid() programs. However, you can modify this + behavior using coreadm. If you enable setuid() core files + for the current user, they will be generated using the + mode 600 and owned by the superuser. + +2.7.1 Installing MySQL on Solaris Using a Solaris PKG + + You can install MySQL on Solaris and OpenSolaris using a + binary package using the native Solaris PKG format instead of + the binary tarball distribution. To use this package, download the corresponding - mysql-VERSION-solaris10-PLATFORM.pkg.gz file, then uncompress it. - For example: -shell> gunzip mysql-5.5.36-solaris10-x86_64.pkg.gz + mysql-VERSION-solaris10-PLATFORM.pkg.gz file, then uncompress + it. For example: +shell> gunzip mysql-5.5.44-solaris10-x86_64.pkg.gz To install a new package, use pkgadd and follow the onscreen - prompts. You must have root privileges to perform this operation: -shell> pkgadd -d mysql-5.5.36-solaris10-x86_64.pkg + prompts. You must have root privileges to perform this + operation: +shell> pkgadd -d mysql-5.5.44-solaris10-x86_64.pkg The following packages are available: 1 mysql MySQL Community Server (GPL) - (i86pc) 5.5.36 + (i86pc) 5.5.44 Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]: - The PKG installer installs all of the files and tools needed, and - then initializes your database if one does not exist. To complete - the installation, you should set the root password for MySQL as - provided in the instructions at the end of the installation. - Alternatively, you can run the mysql_secure_installation script - that comes with the installation. - - By default, the PKG package installs MySQL under the root path - /opt/mysql. You can change only the installation root path when - using pkgadd, which can be used to install MySQL in a different - Solaris zone. If you need to install in a specific directory, use - a binary tar file distribution. - - The pkg installer copies a suitable startup script for MySQL into - /etc/init.d/mysql. To enable MySQL to startup and shutdown - automatically, you should create a link between this file and the - init script directories. For example, to ensure safe startup and - shutdown of MySQL you could use the following commands to add the - right links: + The PKG installer installs all of the files and tools needed, + and then initializes your database if one does not exist. To + complete the installation, you should set the root password + for MySQL as provided in the instructions at the end of the + installation. Alternatively, you can run the + mysql_secure_installation script that comes with the + installation. + + By default, the PKG package installs MySQL under the root + path /opt/mysql. You can change only the installation root + path when using pkgadd, which can be used to install MySQL in + a different Solaris zone. If you need to install in a + specific directory, use a binary tar file distribution. + + The pkg installer copies a suitable startup script for MySQL + into /etc/init.d/mysql. To enable MySQL to startup and + shutdown automatically, you should create a link between this + file and the init script directories. For example, to ensure + safe startup and shutdown of MySQL you could use the + following commands to add the right links: shell> ln /etc/init.d/mysql /etc/rc3.d/S91mysql shell> ln /etc/init.d/mysql /etc/rc0.d/K02mysql - To remove MySQL, the installed package name is mysql. You can use - this in combination with the pkgrm command to remove the + To remove MySQL, the installed package name is mysql. You can + use this in combination with the pkgrm command to remove the installation. - To upgrade when using the Solaris package file format, you must - remove the existing installation before installing the updated - package. Removal of the package does not delete the existing - database information, only the server, binaries and support files. - The typical upgrade sequence is therefore: + To upgrade when using the Solaris package file format, you + must remove the existing installation before installing the + updated package. Removal of the package does not delete the + existing database information, only the server, binaries and + support files. The typical upgrade sequence is therefore: shell> mysqladmin shutdown shell> pkgrm mysql -shell> pkgadd -d mysql-5.5.36-solaris10-x86_64.pkg +shell> pkgadd -d mysql-5.5.44-solaris10-x86_64.pkg shell> mysqld_safe & shell> mysql_upgrade - You should check the notes in Section 2.12, "Upgrading or + You should check the notes in Section 2.11, "Upgrading or Downgrading MySQL" before performing any upgrade. -2.7.2. Installing MySQL on OpenSolaris Using IPS +2.7.2 Installing MySQL on OpenSolaris Using IPS OpenSolaris includes standard packages for MySQL in the core - repository. The MySQL packages are based on a specific release of - MySQL and updated periodically. For the latest release you must - use either the native Solaris PKG, tar, or source installations. - The native OpenSolaris packages include SMF files so that you can - easily control your MySQL installation, including automatic - startup and recovery, using the native service management tools. - - To install MySQL on OpenSolaris, use the pkg command. You will - need to be logged in as root, or use the pfexec tool, as shown in - the example below: + repository. The MySQL packages are based on a specific + release of MySQL and updated periodically. For the latest + release you must use either the native Solaris PKG, tar, or + source installations. The native OpenSolaris packages include + SMF files so that you can easily control your MySQL + installation, including automatic startup and recovery, using + the native service management tools. + + To install MySQL on OpenSolaris, use the pkg command. You + will need to be logged in as root, or use the pfexec tool, as + shown in the example below: shell> pfexec pkg install SUNWmysql55 The package set installs three individual packages, SUNWmysql55lib, which contains the MySQL client libraries; - SUNWmysql55r which contains the root components, including SMF and - configuration files; and SUNWmysql55u which contains the scripts, - binary tools and other files. You can install these packages - individually if you only need the corresponding components. - - The MySQL files are installed into /usr/mysql which symbolic links - for the sub directories (bin, lib, etc.) to a version specific - directory. For MySQL 5.5, the full installation is located in - /usr/mysql/5.5. The default data directory is /var/mysql/5.5/data. - The configuration file is installed in /etc/mysql/5.5/my.cnf. This - layout permits multiple versions of MySQL to be installed, without - overwriting the data and binaries from other versions. - - Once installed, you must run mysql_install_db to initialize the - database, and use the mysql_secure_installation to secure your - installation. + SUNWmysql55r which contains the root components, including + SMF and configuration files; and SUNWmysql55u which contains + the scripts, binary tools and other files. You can install + these packages individually if you only need the + corresponding components. + + The MySQL files are installed into /usr/mysql which symbolic + links for the sub directories (bin, lib, etc.) to a version + specific directory. For MySQL 5.5, the full installation is + located in /usr/mysql/5.5. The default data directory is + /var/mysql/5.5/data. The configuration file is installed in + /etc/mysql/5.5/my.cnf. This layout permits multiple versions + of MySQL to be installed, without overwriting the data and + binaries from other versions. + + Once installed, you must run mysql_install_db to initialize + the database, and use the mysql_secure_installation to secure + your installation. Using SMF to manage your MySQL installation - Once installed, you can start and stop your MySQL server using the - installed SMF configuration. The service name is mysql, or if you - have multiple versions installed, you should use the full version - name, for example mysql:version_55. To start and enable MySQL to - be started at boot time: + Once installed, you can start and stop your MySQL server + using the installed SMF configuration. The service name is + mysql, or if you have multiple versions installed, you should + use the full version name, for example mysql:version_55. To + start and enable MySQL to be started at boot time: shell> svcadm enable mysql To disable MySQL from starting during boot time, and shut the MySQL server down if it is running, use: shell> svcadm disable mysql - To restart MySQL, for example after a configuration file changes, - use the restart option: + To restart MySQL, for example after a configuration file + changes, use the restart option: shell> svcadm restart mysql - You can also use SMF to configure the data directory and enable - full 64-bit mode. For example, to set the data directory used by - MySQL: -shell> svccfg -svc:> select mysql:version_55 -svc:/application/database/mysql:version_55> setprop mysql/data=/data0 -/mysql - + You can also use SMF to configure the data directory and + enable full 64-bit mode. For example, to set the data + directory used by MySQL: +shell> svccfg +svc:> select mysql:version_55 +svc:/application/database/mysql:version_55> setprop mysql/data=/data0/ +mysql - By default, the 32-bit binaries are used. To enable the 64-bit - server on 64-bit platforms, set the enable_64bit parameter. For - example: -svc:/application/database/mysql:version_55> setprop mysql/enable_64bi -t=1 + By default, the 32-bit binaries are used. To enable the + 64-bit server on 64-bit platforms, set the enable_64bit + parameter. For example: +svc:/application/database/mysql:version_55> setprop mysql/enable_64bit +=1 You need to refresh the SMF after settings these options: shell> svcadm refresh mysql -2.8. Installing MySQL on HP-UX - - MySQL for HP-UX is available in a number of different forms: - - * Using a DEPOT distribution provided at - http://dev.mysql.com/downloads/. Please read the general notes - on HP-UX installation before continuing. For more information - on DEPOT installations, see Section 2.8.2, "Installing MySQL - on HP-UX Using DEPOT Packages." - - * Using a binary tarball distribution provided at - http://dev.mysql.com/downloads/. Please read the general notes - on HP-UX installation before continuing. For more information - on binary installations, see Section 2.2, "Installing MySQL on - Unix/Linux Using Generic Binaries." - -2.8.1. General Notes on Installing MySQL on HP-UX - - Some additional notes on installing and using MySQL on HP-UX: - - * If you install MySQL using a binary tarball distribution on - HP-UX, you may run into trouble even before you get the MySQL - distribution unpacked, as the HP-UX tar cannot handle long - file names. This means that you may see errors when you try to - unpack MySQL. - If this occurs, you must use GNU tar (gtar) to unpack the - distribution. - - * Because of some critical bugs in the standard HP-UX libraries, - you should install the following patches before trying to run - MySQL on HP-UX 11.0: -PHKL_22840 Streams cumulative -PHNE_22397 ARPA cumulative - This solves the problem of getting EWOULDBLOCK from recv() and - EBADF from accept() in threaded applications. - -2.8.2. Installing MySQL on HP-UX Using DEPOT Packages - - The HP-UX DEPOT format packages can be installed using the - swinstall command. You should install the ncurses and zlib - libraries before installing the MySQL DEPOT package. You can use - the free software depothelper tool to install these packages and - any dependencies for you automatically. - - To install using the MySQL DEPOT packages, follow this guide: - - 1. Download the MySQL DEPOT package from - http://dev.mysql.com/downloads/. You must uncompress the - package before installation: -root-shell> gunzip mysql-5.1.48-hpux11.31-ia64-64bit.depot.gz - - 2. Install the DEPOT package using swinstall: -root-shell> swinstall -s mysql-5.1.49-hpux11.31-ia64-64bit.depot - MySQL will be installed into a directory matching the depot - package name, within /usr/local. For convenience, you may want - to create a symbolic link to the installed directory, for - example: -root-shell> ln -s mysql-5.1.49-hpux11.31-ia64-64bit mysql - - 3. Your package is now installed. You should complete the - configuration of MySQL by creating a user and group: -root-shell> /usr/sbin/groupadd mysql -root-shell> /usr/sbin/useradd -g mysql -d /var/lib/mysql/ -s /bin/fal -se mysql - - 4. Create the standard database using the new user/group you have - created, and set the permissions: -root-shell> cd /usr/local/ -root-shell> scripts/mysql_install_db --user=mysql -root-shell> chown -R root . -root-shell> chown -R mysql data - - 5. Finally, secure your new installation by setting the root - passwords, and then start your MySQL server using the mysql - user: -root-shell> mysql_secure_installation -root-shell> mysqld_safe --user=mysql & - -2.9. Installing MySQL on FreeBSD +2.8 Installing MySQL on FreeBSD This section provides information about installing MySQL on variants of FreeBSD Unix. - You can install MySQL on FreeBSD by using the binary distribution - provided by Oracle. For more information, see Section 2.2, - "Installing MySQL on Unix/Linux Using Generic Binaries." - - The easiest (and preferred) way to install MySQL is to use the - mysql-server and mysql-client ports available at - http://www.freebsd.org/. Using these ports gives you the following - benefits: + You can install MySQL on FreeBSD by using the binary + distribution provided by Oracle. For more information, see + Section 2.2, "Installing MySQL on Unix/Linux Using Generic + Binaries." + + The easiest (and preferred) way to install MySQL is to use + the mysql-server and mysql-client ports available at + http://www.freebsd.org/. Using these ports gives you the + following benefits: - * A working MySQL with all optimizations enabled that are known - to work on your version of FreeBSD. + * A working MySQL with all optimizations enabled that are + known to work on your version of FreeBSD. * Automatic configuration and build. @@ -5191,12 +5646,12 @@ * The ability to use pkg_info -L to see which files are installed. - * The ability to use pkg_delete to remove MySQL if you no longer - want it on your machine. + * The ability to use pkg_delete to remove MySQL if you no + longer want it on your machine. - The MySQL build process requires GNU make (gmake) to work. If GNU - make is not available, you must install it first before compiling - MySQL. + The MySQL build process requires GNU make (gmake) to work. If + GNU make is not available, you must install it first before + compiling MySQL. To install using the ports system: # cd /usr/ports/databases/mysql51-server @@ -5207,12 +5662,13 @@ ... The standard port installation places the server into - /usr/local/libexec/mysqld, with the startup script for the MySQL - server placed in /usr/local/etc/rc.d/mysql-server. + /usr/local/libexec/mysqld, with the startup script for the + MySQL server placed in /usr/local/etc/rc.d/mysql-server. Some additional notes on the BSD implementation: - * To remove MySQL after installation using the ports system: + * To remove MySQL after installation using the ports + system: # cd /usr/ports/databases/mysql51-server # make deinstall ... @@ -5220,205 +5676,230 @@ # make deinstall ... - * If you get problems with the current date in MySQL, setting - the TZ variable should help. See Section 2.13, "Environment - Variables." -2.10. Installing MySQL from Source + * If you get problems with the current date in MySQL, + setting the TZ variable should help. See Section 2.12, + "Environment Variables." + +2.9 Installing MySQL from Source + + Building MySQL from the source code enables you to customize + build parameters, compiler optimizations, and installation + location. For a list of systems on which MySQL is known to + run, see + http://www.mysql.com/support/supportedplatforms/database.html + . + + Before you proceed with an installation from source, check + whether Oracle produces a precompiled binary distribution for + your platform and whether it works for you. We put a great + deal of effort into ensuring that our binaries are built with + the best possible options for optimal performance. + Instructions for installing binary distributions are + available in Section 2.2, "Installing MySQL on Unix/Linux + Using Generic Binaries." + Note - Building MySQL from the source code enables you to customize build - parameters, compiler optimizations, and installation location. For - a list of systems on which MySQL is known to run, see Section - 2.1.1, "Operating Systems Supported by MySQL Community Server." - - Before you proceed with an installation from source, check whether - Oracle produces a precompiled binary distribution for your - platform and whether it works for you. We put a great deal of - effort into ensuring that our binaries are built with the best - possible options for optimal performance. Instructions for - installing binary distributions are available in Section 2.2, - "Installing MySQL on Unix/Linux Using Generic Binaries." - Note - - This section describes how to build MySQL from source using CMake. - Before MySQL 5.5, source builds used the GNU autotools on - Unix-like systems. Source builds on Windows used CMake, but the - process was different from that described here. For + This section describes how to build MySQL from source using + CMake. Before MySQL 5.5, source builds used the GNU autotools + on Unix-like systems. Source builds on Windows used CMake, + but the process was different from that described here. For source-building instructions for older versions of MySQL, see Installing MySQL from Source - (http://dev.mysql.com/doc/refman/5.1/en/source-installation.html), - in the MySQL 5.1 Reference Manual. If you are familiar with - autotools but not CMake, you might find these transition + (http://dev.mysql.com/doc/refman/5.1/en/source-installation.h + tml), in the MySQL 5.1 Reference Manual. If you are familiar + with autotools but not CMake, you might find these transition instructions helpful: Autotools to CMake Transition Guide - (http://dev.mysql.com/doc/internals/en/autotools-to-cmake.html) + (http://dev.mysql.com/doc/internals/en/autotools-to-cmake.htm + l) Source Installation Methods There are two methods for installing MySQL from source: - * Use a standard MySQL source distribution. To obtain a standard - distribution, see Section 2.1.3, "How to Get MySQL." For - instructions on building from a standard distribution, see - Section 2.10.2, "Installing MySQL Using a Standard Source - Distribution." - Standard distributions are available as compressed tar files, - Zip archives, or RPM packages. Distribution files have names - of the form mysql-VERSION.tar.gz, mysql-VERSION.zip, or - mysql-VERSION.rpm, where VERSION is a number like 5.5.36. File - names for source distributions can be distinguished from those - for precompiled binary distributions in that source - distribution names are generic and include no platform name, - whereas binary distribution names include a platform name - indicating the type of system for which the distribution is - intended (for example, pc-linux-i686 or winx64). - - * Use a MySQL development tree. Development trees have not - necessarily received the same level of testing as standard - release distributions, so this installation method is usually - required only if you need the most recent code changes. For - information on building from one of the development trees, see - Section 2.10.3, "Installing MySQL Using a Development Source - Tree." + * Use a standard MySQL source distribution. To obtain a + standard distribution, see Section 2.1.2, "How to Get + MySQL." For instructions on building from a standard + distribution, see Section 2.9.2, "Installing MySQL Using + a Standard Source Distribution." + Standard distributions are available as compressed tar + files, Zip archives, or RPM packages. Distribution files + have names of the form mysql-VERSION.tar.gz, + mysql-VERSION.zip, or mysql-VERSION.rpm, where VERSION is + a number like 5.5.44. File names for source distributions + can be distinguished from those for precompiled binary + distributions in that source distribution names are + generic and include no platform name, whereas binary + distribution names include a platform name indicating the + type of system for which the distribution is intended + (for example, pc-linux-i686 or winx64). + + * Use a MySQL development tree. For information on building + from one of the development trees, see Section 2.9.3, + "Installing MySQL Using a Development Source Tree." Source Installation System Requirements - Installation of MySQL from source requires several development - tools. Some of these tools are needed no matter whether you use a - standard source distribution or a development source tree. Other - tool requirements depend on which installation method you use. - - To install MySQL from source, your system must have the following - tools, regardless of installation method: - - * CMake, which is used as the build framework on all platforms. - CMake can be downloaded from http://www.cmake.org. - - * A good make program. Although some platforms come with their - own make implementations, it is highly recommended that you - use GNU make 3.75 or newer. It may already be available on - your system as gmake. GNU make is available from - http://www.gnu.org/software/make/. - - * A working ANSI C++ compiler. GCC 4.2.1 or later, Sun Studio 10 - or later, Visual Studio 2008 or later, and many current - vendor-supplied compilers are known to work. + Installation of MySQL from source requires several + development tools. Some of these tools are needed no matter + whether you use a standard source distribution or a + development source tree. Other tool requirements depend on + which installation method you use. + + To install MySQL from source, your system must have the + following tools, regardless of installation method: + + * CMake, which is used as the build framework on all + platforms. CMake can be downloaded from + http://www.cmake.org. + + * A good make program. Although some platforms come with + their own make implementations, it is highly recommended + that you use GNU make 3.75 or newer. It may already be + available on your system as gmake. GNU make is available + from http://www.gnu.org/software/make/. + + * A working ANSI C++ compiler. GCC 4.2.1 or later, Sun + Studio 12 or later, Visual Studio 2008 or later, and many + current vendor-supplied compilers are known to work. * Perl is needed if you intend to run test scripts. Most Unix-like systems include Perl. On Windows, you can use a version such as ActiveState Perl. - To install MySQL from a standard source distribution, one of the - following tools is required to unpack the distribution file: + To install MySQL from a standard source distribution, one of + the following tools is required to unpack the distribution + file: + + * For a .tar.gz compressed tar file: GNU gunzip to + uncompress the distribution and a reasonable tar to + unpack it. If your tar program supports the z option, it + can both uncompress and unpack the file. + GNU tar is known to work. The standard tar provided with + some operating systems is not able to unpack the long + file names in the MySQL distribution. You should download + and install GNU tar, or if available, use a preinstalled + version of GNU tar. Usually this is available as gnutar, + gtar, or as tar within a GNU or Free Software directory, + such as /usr/sfw/bin or /usr/local/bin. GNU tar is + available from http://www.gnu.org/software/tar/. + + * For a .zip Zip archive: WinZip or another tool that can + read .zip files. + + * For an .rpm RPM package: The rpmbuild program used to + build the distribution unpacks it. - * For a .tar.gz compressed tar file: GNU gunzip to uncompress - the distribution and a reasonable tar to unpack it. If your - tar program supports the z option, it can both uncompress and - unpack the file. - GNU tar is known to work. The standard tar provided with some - operating systems is not able to unpack the long file names in - the MySQL distribution. You should download and install GNU - tar, or if available, use a preinstalled version of GNU tar. - Usually this is available as gnutar, gtar, or as tar within a - GNU or Free Software directory, such as /usr/sfw/bin or - /usr/local/bin. GNU tar is available from - http://www.gnu.org/software/tar/. - - * For a .zip Zip archive: WinZip or another tool that can read - .zip files. - - * For an .rpm RPM package: The rpmbuild program used to build - the distribution unpacks it. - - To install MySQL from a development source tree, the following - additional tools are required: - - * To obtain the source tree, you must have Bazaar installed. The - Bazaar VCS Web site (http://bazaar-vcs.org) has instructions - for downloading and installing Bazaar on different platforms. - Bazaar is supported on any platform that supports Python, and - is therefore compatible with any Linux, Unix, Windows, or Mac - OS X host. - - * bison is needed to generate sql_yacc.cc from sql_yacc.yy You - should use the latest version of bison where possible. - Versions 1.75 and 2.1 are known to work. There have been - reported problems with bison 1.875. If you experience - problems, upgrade to a later, rather than earlier, version. - bison is available from http://www.gnu.org/software/bison/. - bison for Windows can be downloaded from - http://gnuwin32.sourceforge.net/packages/bison.htm. Download - the package labeled "Complete package, excluding sources". On - Windows, the default location for bison is the C:\Program - Files\GnuWin32 directory. Some utilities may fail to find - bison because of the space in the directory name. Also, Visual - Studio may simply hang if there are spaces in the path. You - can resolve these problems by installing into a directory that - does not contain a space; for example C:\GnuWin32. + To install MySQL from a development source tree, the + following additional tools are required: - * On OpenSolaris and Solaris Express, m4 must be installed in - addition to bison. m4 is available from + * One of the following revision control systems is required + to obtain the development source code: + + + Git: The GitHub Help (https://help.github.com/) + provides instructions for downloading and installing + Git on different platforms. MySQL officially joined + GitHub in September, 2014. For more information + about MySQL's move to GitHub, refer to the + announcement on the MySQL Release Engineering blog: + MySQL on GitHub + (http://mysqlrelease.com/2014/09/mysql-on-github/) + + + Bazaar: The Bazaar VCS Web site + (http://bazaar-vcs.org) provides instructions for + downloading and installing Bazaar on different + platforms. Bazaar is supported on any platform that + supports Python, and is therefore compatible with + any Linux, Unix, Windows, or OS X host. + + * bison 2.1 or newer, available from + http://www.gnu.org/software/bison/. (Version 1 is no + longer supported.) Use the latest version of bison where + possible; if you experience problems, upgrade to a later + version, rather than revert to an earlier one. + bison is available from + http://www.gnu.org/software/bison/. bison for Windows can + be downloaded from + http://gnuwin32.sourceforge.net/packages/bison.htm. + Download the package labeled "Complete package, excluding + sources". On Windows, the default location for bison is + the C:\Program Files\GnuWin32 directory. Some utilities + may fail to find bison because of the space in the + directory name. Also, Visual Studio may simply hang if + there are spaces in the path. You can resolve these + problems by installing into a directory that does not + contain a space; for example C:\GnuWin32. + + * On OpenSolaris and Solaris Express, m4 must be installed + in addition to bison. m4 is available from http://www.gnu.org/software/m4/. Note - If you have to install any programs, modify your PATH environment - variable to include any directories in which the programs are - located. See Section 4.2.4, "Setting Environment Variables." - - If you run into problems and need to file a bug report, please use - the instructions in Section 1.7, "How to Report Bugs or Problems." - -2.10.1. MySQL Layout for Source Installation - - By default, when you install MySQL after compiling it from source, - the installation step installs files under /usr/local/mysql. The - component locations under the installation directory are the same - as for binary distributions. See Section 2.2, "MySQL Installation - Layout for Generic Unix/Linux Binary Package," and Section 2.3.1, - "MySQL Installation Layout on Microsoft Windows." To configure - installation locations different from the defaults, use the - options described at Section 2.10.4, "MySQL Source-Configuration - Options." + If you have to install any programs, modify your PATH + environment variable to include any directories in which the + programs are located. See Section 4.2.10, "Setting + Environment Variables." + + If you run into problems and need to file a bug report, + please use the instructions in Section 1.7, "How to Report + Bugs or Problems." + +2.9.1 MySQL Layout for Source Installation + + By default, when you install MySQL after compiling it from + source, the installation step installs files under + /usr/local/mysql. The component locations under the + installation directory are the same as for binary + distributions. See Section 2.2, "MySQL Installation Layout + for Generic Unix/Linux Binary Package," and Section 2.3.1, + "MySQL Installation Layout on Microsoft Windows." To + configure installation locations different from the defaults, + use the options described at Section 2.9.4, "MySQL + Source-Configuration Options." -2.10.2. Installing MySQL Using a Standard Source Distribution +2.9.2 Installing MySQL Using a Standard Source Distribution To install MySQL from a standard source distribution: - 1. Verify that your system satisfies the tool requirements listed - at Section 2.10, "Installing MySQL from Source." + 1. Verify that your system satisfies the tool requirements + listed at Section 2.9, "Installing MySQL from Source." - 2. Obtain a distribution file using the instructions in Section - 2.1.3, "How to Get MySQL." + 2. Obtain a distribution file using the instructions in + Section 2.1.2, "How to Get MySQL." 3. Configure, build, and install the distribution using the instructions in this section. - 4. Perform postinstallation procedures using the instructions in - Section 2.11, "Postinstallation Setup and Testing." + 4. Perform postinstallation procedures using the + instructions in Section 2.10, "Postinstallation Setup and + Testing." In MySQL 5.5, CMake is used as the build framework on all platforms. The instructions given here should enable you to produce a working installation. For additional information on - using CMake to build MySQL, see How to Build MySQL Server with - CMake (http://dev.mysql.com/doc/internals/en/cmake.html). - - If you start from a source RPM, use the following command to make - a binary RPM that you can install. If you do not have rpmbuild, - use rpm instead. + using CMake to build MySQL, see How to Build MySQL Server + with CMake + (http://dev.mysql.com/doc/internals/en/cmake.html). + + If you start from a source RPM, use the following command to + make a binary RPM that you can install. If you do not have + rpmbuild, use rpm instead. shell> rpmbuild --rebuild --clean MySQL-VERSION.src.rpm - The result is one or more binary RPM packages that you install as - indicated in Section 2.5.1, "Installing MySQL on Linux Using RPM - Packages." - - The sequence for installation from a compressed tar file or Zip - archive source distribution is similar to the process for - installing from a generic binary distribution (see Section 2.2, - "Installing MySQL on Unix/Linux Using Generic Binaries"), except - that it is used on all platforms and includes steps to configure - and compile the distribution. For example, with a compressed tar - file source distribution on Unix, the basic installation command - sequence looks like this: + The result is one or more binary RPM packages that you + install as indicated in Section 2.5.1, "Installing MySQL on + Linux Using RPM Packages." + + The sequence for installation from a compressed tar file or + Zip archive source distribution is similar to the process for + installing from a generic binary distribution (see Section + 2.2, "Installing MySQL on Unix/Linux Using Generic + Binaries"), except that it is used on all platforms and + includes steps to configure and compile the distribution. For + example, with a compressed tar file source distribution on + Unix, the basic installation command sequence looks like + this: # Preconfiguration setup shell> groupadd mysql shell> useradd -r -g mysql mysql @@ -5442,45 +5923,49 @@ # Next command is optional shell> cp support-files/mysql.server /etc/init.d/mysql.server - A more detailed version of the source-build specific instructions - is shown following. + A more detailed version of the source-build specific + instructions is shown following. Note - The procedure shown here does not set up any passwords for MySQL - accounts. After following the procedure, proceed to Section 2.11, - "Postinstallation Setup and Testing," for postinstallation setup - and testing. + The procedure shown here does not set up any passwords for + MySQL accounts. After following the procedure, proceed to + Section 2.10, "Postinstallation Setup and Testing," for + postinstallation setup and testing. Perform Preconfiguration Setup - On Unix, set up the mysql user and group that will be used to run - and execute the MySQL server and own the database directory. For - details, see Creating a mysql System User and Group, in Section - 2.2, "Installing MySQL on Unix/Linux Using Generic Binaries." Then - perform the following steps as the mysql user, except as noted. + On Unix, set up the mysql user and group that will be used to + run and execute the MySQL server and own the database + directory. For details, see Creating a mysql System User and + Group, in Section 2.2, "Installing MySQL on Unix/Linux Using + Generic Binaries." Then perform the following steps as the + mysql user, except as noted. Obtain and Unpack the Distribution - Pick the directory under which you want to unpack the distribution - and change location into it. + Pick the directory under which you want to unpack the + distribution and change location into it. Obtain a distribution file using the instructions in Section - 2.1.3, "How to Get MySQL." + 2.1.2, "How to Get MySQL." Unpack the distribution into the current directory: - * To unpack a compressed tar file, tar can uncompress and unpack - the distribution if it has z option support: + * To unpack a compressed tar file, tar can uncompress and + unpack the distribution if it has z option support: shell> tar zxvf mysql-VERSION.tar.gz + If your tar does not have z option support, use gunzip to unpack the distribution and tar to unpack it: shell> gunzip < mysql-VERSION.tar.gz | tar xvf - + Alternatively, CMake can uncompress and unpack the distribution: shell> cmake -E tar zxvf mysql-VERSION.tar.gz - * To unpack a Zip archive, use WinZip or another tool that can - read .zip files. + + * To unpack a Zip archive, use WinZip or another tool that + can read .zip files. Unpacking the distribution file creates a directory named mysql-VERSION. @@ -5491,36 +5976,40 @@ distribution: shell> cd mysql-VERSION - Configure the source directory. The minimum configuration command - includes no options to override configuration defaults: + Configure the source directory. The minimum configuration + command includes no options to override configuration + defaults: shell> cmake . - On Windows, specify the development environment. For example, the - following commands configure MySQL for 32-bit or 64-bit builds, - respectively: + On Windows, specify the development environment. For example, + the following commands configure MySQL for 32-bit or 64-bit + builds, respectively: shell> cmake . -G "Visual Studio 9 2008" shell> cmake . -G "Visual Studio 9 2008 Win64" - On Mac OS X, to use the Xcode IDE: + On OS X, to use the Xcode IDE: shell> cmake . -G Xcode - When you run cmake, you might want to add options to the command - line. Here are some examples: + When you run cmake, you might want to add options to the + command line. Here are some examples: - * -DBUILD_CONFIG=mysql_release: Configure the source with the - same build options used by Oracle to produce binary + * -DBUILD_CONFIG=mysql_release: Configure the source with + the same build options used by Oracle to produce binary distributions for official MySQL releases. - * -DCMAKE_INSTALL_PREFIX=dir_name: Configure the distribution - for installation under a particular location. + * -DCMAKE_INSTALL_PREFIX=dir_name: Configure the + distribution for installation under a particular + location. - * -DCPACK_MONOLITHIC_INSTALL=1: Cause make package to generate a - single installation file rather than multiple files. + * -DCPACK_MONOLITHIC_INSTALL=1: Cause make package to + generate a single installation file rather than multiple + files. - * -DWITH_DEBUG=1: Build the distribution with debugging support. + * -DWITH_DEBUG=1: Build the distribution with debugging + support. - For a more extensive list of options, see Section 2.10.4, "MySQL - Source-Configuration Options." + For a more extensive list of options, see Section 2.9.4, + "MySQL Source-Configuration Options." To list the configuration options, use one of the following commands: @@ -5529,24 +6018,26 @@ shell> cmake . -LAH # all params with help text shell> ccmake . # interactive display - If CMake fails, you might need to reconfigure by running it again - with different options. If you do reconfigure, take note of the - following: - - * If CMake is run after it has previously been run, it may use - information that was gathered during its previous invocation. - This information is stored in CMakeCache.txt. When CMake - starts up, it looks for that file and reads its contents if it - exists, on the assumption that the information is still - correct. That assumption is invalid when you reconfigure. - - * Each time you run CMake, you must run make again to recompile. - However, you may want to remove old object files from previous - builds first because they were compiled using different - configuration options. + If CMake fails, you might need to reconfigure by running it + again with different options. If you do reconfigure, take + note of the following: + + * If CMake is run after it has previously been run, it may + use information that was gathered during its previous + invocation. This information is stored in CMakeCache.txt. + When CMake starts up, it looks for that file and reads + its contents if it exists, on the assumption that the + information is still correct. That assumption is invalid + when you reconfigure. + + * Each time you run CMake, you must run make again to + recompile. However, you may want to remove old object + files from previous builds first because they were + compiled using different configuration options. To prevent old object files or configuration information from - being used, run these commands on Unix before re-running CMake: + being used, run these commands on Unix before re-running + CMake: shell> make clean shell> rm CMakeCache.txt @@ -5556,14 +6047,14 @@ If you build out of the source tree (as described later), the CMakeCache.txt file and all built files are in the build - directory, so you can remove that directory to object files and - cached configuration information. + directory, so you can remove that directory to object files + and cached configuration information. - If you are going to send mail to a MySQL mailing list to ask for - configuration assistance, first check the files in the CMakeFiles - directory for useful information about the failure. To file a bug - report, please use the instructions in Section 1.7, "How to Report - Bugs or Problems." + If you are going to send mail to a MySQL mailing list to ask + for configuration assistance, first check the files in the + CMakeFiles directory for useful information about the + failure. To file a bug report, please use the instructions in + Section 1.7, "How to Report Bugs or Problems." Build the Distribution @@ -5574,31 +6065,49 @@ The second command sets VERBOSE to show the commands for each compiled source. - Use gmake instead on systems where you are using GNU make and it - has been installed as gmake. + Use gmake instead on systems where you are using GNU make and + it has been installed as gmake. On Windows: shell> devenv MySQL.sln /build RelWithDebInfo - It is possible to build out of the source tree to keep the tree - clean. If the top-level source directory is named mysql-src under - your current working directory, you can build in a directory named - build at the same level like this: -shell> mkdir build -shell> cd build + It is possible to build out of the source tree to keep the + tree clean. If the top-level source directory is named + mysql-src under your current working directory, you can build + in a directory named bld at the same level like this: +shell> mkdir bld +shell> cd bld shell> cmake ../mysql-src - If you have gotten to the compilation stage, but the distribution - does not build, see Section 2.10.5, "Dealing with Problems - Compiling MySQL," for help. If that does not solve the problem, - please enter it into our bugs database using the instructions - given in Section 1.7, "How to Report Bugs or Problems." If you - have installed the latest versions of the required tools, and they - crash trying to process our configuration files, please report - that also. However, if you get a command not found error or a - similar problem for required tools, do not report it. Instead, - make sure that all the required tools are installed and that your - PATH variable is set correctly so that your shell can find them. + The build directory need not actually be outside the source + tree. For example, to build in a directory, you can build in + a directory named bld under the top-level source tree, do + this, starting with mysql-src as your current working + directory: +shell> mkdir bld +shell> cd bld +shell> cmake .. + + If you have multiple source trees at the same level (for + example, to build multiple versions of MySQL), the second + strategy can be advantageous. The first strategy places all + build directories at the same level, which requires that you + choose a unique name for each. With the second strategy, you + can use the same name for the build directory within each + source tree. + + If you have gotten to the compilation stage, but the + distribution does not build, see Section 2.9.5, "Dealing with + Problems Compiling MySQL," for help. If that does not solve + the problem, please enter it into our bugs database using the + instructions given in Section 1.7, "How to Report Bugs or + Problems." If you have installed the latest versions of the + required tools, and they crash trying to process our + configuration files, please report that also. However, if you + get a command not found error or a similar problem for + required tools, do not report it. Instead, make sure that all + the required tools are installed and that your PATH variable + is set correctly so that your shell can find them. Install the Distribution @@ -5606,193 +6115,339 @@ shell> make install This installs the files under the configured installation - directory (by default, /usr/local/mysql). You might need to run - the command as root. + directory (by default, /usr/local/mysql). You might need to + run the command as root. - To install in a specific directory, add a DESTDIR parameter to the - command line: + To install in a specific directory, add a DESTDIR parameter + to the command line: shell> make install DESTDIR="/opt/mysql" - Alternatively, generate installation package files that you can - install where you like: + Alternatively, generate installation package files that you + can install where you like: shell> make package This operation produces one or more .tar.gz files that can be - installed like generic binary distribution packages. See Section - 2.2, "Installing MySQL on Unix/Linux Using Generic Binaries." If - you run CMake with -DCPACK_MONOLITHIC_INSTALL=1, the operation - produces a single file. Otherwise, it produces multiple files. + installed like generic binary distribution packages. See + Section 2.2, "Installing MySQL on Unix/Linux Using Generic + Binaries." If you run CMake with + -DCPACK_MONOLITHIC_INSTALL=1, the operation produces a single + file. Otherwise, it produces multiple files. On Windows, generate the data directory, then create a .zip archive installation package: -shell> devenv MySQL.sln /build RelWithDebInfo /project initial_databa -se +shell> devenv MySQL.sln /build RelWithDebInfo /project initial_databas +e shell> devenv MySQL.sln /build RelWithDebInfo /project package - You can install the resulting .zip archive where you like. See - Section 2.3.7, "Installing MySQL on Microsoft Windows Using a - noinstall Zip Archive." + You can install the resulting .zip archive where you like. + See Section 2.3.7, "Installing MySQL on Microsoft Windows + Using a noinstall Zip Archive." Perform Postinstallation Setup - The remainder of the installation process involves setting up the - configuration file, creating the core databases, and starting the - MySQL server. For instructions, see Section 2.11, - "Postinstallation Setup and Testing." - Note - - The accounts that are listed in the MySQL grant tables initially - have no passwords. After starting the server, you should set up - passwords for them using the instructions in Section 2.11, - "Postinstallation Setup and Testing." - -2.10.3. Installing MySQL Using a Development Source Tree - - This section discusses how to install MySQL from the latest - development source code. Development trees have not necessarily - received the same level of testing as standard release - distributions, so this installation method is usually required - only if you need the most recent code changes. Do not use a - development tree for production systems. If your goal is simply to - get MySQL up and running on your system, you should use a standard - release distribution (either a binary or source distribution). See - Section 2.1.3, "How to Get MySQL." - - MySQL development projects are hosted on Launchpad - (http://launchpad.net/). MySQL projects, including MySQL Server, - MySQL Workbench, and others are available from the Oracle/MySQL - Engineering (http://launchpad.net/~mysql) page. For the - repositories related only to MySQL Server, see the MySQL Server - (http://launchpad.net/mysql-server) page. - - To install MySQL from a development source tree, your system must - satisfy the tool requirements listed at Section 2.10, "Installing - MySQL from Source," including the requirements for Bazaar and - bison. + The remainder of the installation process involves setting up + the configuration file, creating the core databases, and + starting the MySQL server. For instructions, see Section + 2.10, "Postinstallation Setup and Testing." + Note + + The accounts that are listed in the MySQL grant tables + initially have no passwords. After starting the server, you + should set up passwords for them using the instructions in + Section 2.10, "Postinstallation Setup and Testing." + +2.9.3 Installing MySQL Using a Development Source Tree + + This section describes how to install MySQL from the latest + development source code, which is currently hosted on both + GitHub (https://github.com/) and Launchpad + (http://launchpad.net/). To obtain the MySQL Server source + code from one of these repository hosting services, you can + set up a local MySQL Git repository or a local MySQL Bazaar + branch. + + * On GitHub (https://github.com/), MySQL Server and other + MySQL projects are found on the MySQL + (https://github.com/mysql) page. The MySQL Server project + is a single repository that contains branches for MySQL + 5.5, 5.6, and 5.7. + MySQL officially joined GitHub in September, 2014. For + more information about MySQL's move to GitHub, refer to + the announcement on the MySQL Release Engineering blog: + MySQL on GitHub + (http://mysqlrelease.com/2014/09/mysql-on-github/) + + * On Launchpad (http://launchpad.net/), MySQL projects, + including MySQL Server, MySQL Workbench, and others are + found on the Oracle/MySQL Engineering + (http://launchpad.net/~mysql) page. For the repositories + related only to MySQL Server, see the MySQL Server + (http://launchpad.net/mysql-server) page. - To create a local branch of the MySQL development tree on your - machine, use this procedure: +Prerequisites for Installing from Development Source - 1. To obtain a copy of the MySQL source code, you must create a - new Bazaar branch. If you do not already have a Bazaar + To install MySQL from a development source tree, your system + must satisfy the tool requirements outlined in Section 2.9, + "Installing MySQL from Source." + +Setting Up a MySQL Git Repository + + To set up a MySQL Git repository on your machine, use this + procedure: + + 1. Clone the MySQL Git repository to your machine. The + following command clones the MySQL Git repository to a + directory named mysql-server. The download size is + approximately 437 MB. The initial download will take some + time to complete, depending on the speed of your + connection. +~$ git clone https://github.com/mysql/mysql-server.git +Cloning into 'mysql-server'... +remote: Counting objects: 1035465, done. +remote: Total 1035465 (delta 0), reused 0 (delta 0) +Receiving objects: 100% (1035465/1035465), 437.48 MiB | 5.10 MiB/s, do +ne. +Resolving deltas: 100% (855607/855607), done. +Checking connectivity... done. +Checking out files: 100% (21902/21902), done. + + 2. When the clone operation completes, the contents of your + local MySQL Git repository appear similar to the + following: +~$ cd mysql-server + +~/mysql-server$ ls +BUILD COPYING libmysqld regex tests +BUILD-CMAKE dbug libservices scripts unitt +est +client Docs man sql VERSI +ON +cmake extra mysql-test sql-bench vio +CMakeLists.txt include mysys sql-common win +cmd-line-utils INSTALL-SOURCE packaging storage zlib +config.h.cmake INSTALL-WIN-SOURCE plugin strings +configure.cmake libmysql README support-files + + 3. Use the git branch -r command to view the remote tracking + branches for the MySQL repository. +~/mysql-server$ git branch -r + origin/5.5 + origin/5.6 + origin/5.7 + origin/HEAD -> origin/5.7 + + 4. To view the branches that are checked out in your local + repository, issue the git branch command. When you cloned + the MySQL Git repository, the MySQL 5.7 branch was + checked out automatically. The asterisk identifies the + 5.7 branch as the active branch. +~/mysql-server$ git branch +* 5.7 + + 5. To check out a different MySQL branch, run the git + checkout command, specifying the branch name. For + example, to checkout the MySQL 5.5 branch: +~/mysql-server$ git checkout 5.5 +Branch 5.5 set up to track remote branch 5.5 from origin. +Switched to a new branch '5.5' + + 6. Run git branch again to verify that the MySQL 5.5 branch + is present. MySQL 5.5, which is the last branch you + checked out, is marked by an asterisk indicating that it + is the active branch. +~/mysql-server$ git branch +* 5.5 + 5.7 + The git checkout command is also used to switch branches. + For example, to make MySQL 5.7 the active branch again, + you would run git checkout 5.7. + + 7. To obtain changes made after your initial setup of the + MySQL Git repository, switch to the branch you want to + update and issue the git pull command: +~/mysql-server$ git checkout 5.5 +~/mysql-server$ git pull + + To examine the commit history, use the git log option: +~/mysql-server$ git log + + You can also browse commit history and source code on the + GitHub MySQL (https://github.com/mysql) site. + If you see changes or code that you have a question + about, send an email to the MySQL internals mailing list. + See Section 1.6.1, "MySQL Mailing Lists." For information + about contributing a patch, see Contributing to MySQL + Server + (http://mysqlserverteam.com/contributing-to-mysql-server/ + ). + + 8. After you have cloned the MySQL Git repository and have + checked out the branch you want to build, you can build + MySQL Server from the source code. Instructions are + provided in Section 2.9.2, "Installing MySQL Using a + Standard Source Distribution," except that you skip the + part about obtaining and unpacking the distribution. + Be careful about installing a build from a distribution + source tree on a production machine. The installation + command may overwrite your live release installation. If + you already have MySQL installed and do not want to + overwrite it, run CMake with values for the + CMAKE_INSTALL_PREFIX, MYSQL_TCP_PORT, and MYSQL_UNIX_ADDR + options different from those used by your production + server. For additional information about preventing + multiple servers from interfering with each other, see + Section 5.3, "Running Multiple MySQL Instances on One + Machine." + Play hard with your new installation. For example, try to + make new features crash. Start by running make test. See + Section 24.1.2, "The MySQL Test Suite." + +Setting Up a MySQL Bazaar Branch + + To setup a MySQL Bazaar branch on your machine, use this + procedure: + + 1. To obtain a copy of the MySQL development source code + hosted on Launchpad (http://launchpad.net/), create a new + Bazaar branch. If you do not already have a Bazaar repository directory set up, you must initialize a new directory: shell> mkdir mysql-server shell> bzr init-repo --trees mysql-server + This is a one-time operation. - 2. Assuming that you have an initialized repository directory, - you can branch from the public MySQL server repositories to - create a local source tree. To create a branch of a specific - version: + 2. Assuming that you have an initialized repository + directory, you can branch from the public MySQL server + repositories to create a local source tree. To create a + branch of a specific version: shell> cd mysql-server shell> bzr branch lp:mysql-server/5.5 mysql-5.5 - This is a one-time operation per source tree. You can branch - the source trees for several versions of MySQL under the - mysql-server directory. - - 3. The initial download will take some time to complete, - depending on the speed of your connection. Please be patient. - Once you have downloaded the first tree, additional trees - should take significantly less time to download. - - 4. When building from the Bazaar branch, you may want to create a - copy of your active branch so that you can make configuration - and other changes without affecting the original branch - contents. You can achieve this by branching from the original - branch: + + This is a one-time operation per source tree. You can + branch the source trees for several versions of MySQL + under the mysql-server directory. + The initial download will take some time to complete, + depending on the speed of your connection. Once you have + downloaded the first tree, additional trees should take + significantly less time to download. + + 3. When building from the Bazaar branch, you may want to + create a copy of your active branch so that you can make + configuration and other changes without affecting the + original branch contents. You can achieve this by + branching from the original branch: shell> bzr branch mysql-5.5 mysql-5.5-build - 5. To obtain changes made after you have set up the branch - initially, update it using the pull option periodically. Use - this command in the top-level directory of the local copy: + + 4. To obtain changes made after you have set up the branch + initially, update it using the pull option periodically. + Use this command in the top-level directory of the local + copy: shell> bzr pull - To examine the changeset comments for the tree, use the log - option to bzr: + + To examine the changeset comments for the tree, use the + log option to bzr: shell> bzr log + You can also browse changesets, comments, and source code online at the Launchpad MySQL Server (http://launchpad.net/mysql-server) page. - If you see diffs (changes) or code that you have a question - about, do not hesitate to send email to the MySQL internals - mailing list. See Section 1.6.1, "MySQL Mailing Lists." If you - think you have a better idea on how to do something, send an - email message to the list with a patch. - - After you have the local branch, you can build MySQL server from - the source code. For information, see Section 2.10.2, "Installing - MySQL Using a Standard Source Distribution," except that you skip - the part about obtaining and unpacking the distribution. - - Be careful about installing a build from a distribution source - tree on a production machine. The installation command may - overwrite your live release installation. If you already have - MySQL installed and do not want to overwrite it, run CMake with - values for the CMAKE_INSTALL_PREFIX, MYSQL_TCP_PORT, and - MYSQL_UNIX_ADDR options different from those used by your - production server. For additional information about preventing - multiple servers from interfering with each other, see Section - 5.3, "Running Multiple MySQL Instances on One Machine." - - Play hard with your new installation. For example, try to make new - features crash. Start by running make test. See Section 23.1.2, - "The MySQL Test Suite." - -2.10.4. MySQL Source-Configuration Options - - The CMake program provides a great deal of control over how you - configure a MySQL source distribution. Typically, you do this - using options on the CMake command line. For information about - options supported by CMake, run either of these commands in the - top-level source directory: + If you see diffs (changes) or code that you have a + question about, do not hesitate to send email to the + MySQL internals mailing list. See Section 1.6.1, "MySQL + Mailing Lists." For information about contributing at + patch, see Contributing to MySQL Server + (http://mysqlserverteam.com/contributing-to-mysql-server/ + ). + + 5. After you have the local branch, you can build MySQL + server from the source code. Instructions are provided in + Section 2.9.2, "Installing MySQL Using a Standard Source + Distribution," except that you skip the part about + obtaining and unpacking the distribution. + Be careful about installing a build from a distribution + source tree on a production machine. The installation + command may overwrite your live release installation. If + you already have MySQL installed and do not want to + overwrite it, run CMake with values for the + CMAKE_INSTALL_PREFIX, MYSQL_TCP_PORT, and MYSQL_UNIX_ADDR + options different from those used by your production + server. For additional information about preventing + multiple servers from interfering with each other, see + Section 5.3, "Running Multiple MySQL Instances on One + Machine." + Play hard with your new installation. For example, try to + make new features crash. Start by running make test. See + Section 24.1.2, "The MySQL Test Suite." + +2.9.4 MySQL Source-Configuration Options + + The CMake program provides a great deal of control over how + you configure a MySQL source distribution. Typically, you do + this using options on the CMake command line. For information + about options supported by CMake, run either of these + commands in the top-level source directory: shell> cmake . -LH shell> ccmake . - You can also affect CMake using certain environment variables. See - Section 2.13, "Environment Variables." + You can also affect CMake using certain environment + variables. See Section 2.12, "Environment Variables." The following table shows the available CMake options. In the Default column, PREFIX stands for the value of the - CMAKE_INSTALL_PREFIX option, which specifies the installation base - directory. This value is used as the parent location for several - of the installation subdirectories. + CMAKE_INSTALL_PREFIX option, which specifies the installation + base directory. This value is used as the parent location for + several of the installation subdirectories. - Table 2.16. MySQL Source-Configuration Option Reference (CMake) + Table 2.13 MySQL Source-Configuration Option Reference + (CMake) Formats Description Default Introduced Removed - BUILD_CONFIG Use same build options as official releases 5.5.7 - CMAKE_BUILD_TYPE Type of build to produce RelWithDebInfo 5.5.7 - CMAKE_INSTALL_PREFIX Installation base directory /usr/local/mysql - 5.5.8 - COMPILATION_COMMENT Comment about compilation environment 5.5.7 - CPACK_MONOLITHIC_INSTALL Whether package build produces single - file OFF 5.5.7 + BUILD_CONFIG Use same build options as official releases + 5.5.7 + CMAKE_BUILD_TYPE Type of build to produce RelWithDebInfo + 5.5.7 + CMAKE_C_FLAGS Flags for C Compiler + CMAKE_CXX_FLAGS Flags for C++ Compiler + CMAKE_INSTALL_PREFIX Installation base directory + /usr/local/mysql 5.5.8 + COMPILATION_COMMENT Comment about compilation environment + 5.5.7 + CPACK_MONOLITHIC_INSTALL Whether package build produces + single file OFF 5.5.7 DEFAULT_CHARSET The default server character set latin1 5.5.7 - DEFAULT_COLLATION The default server collation latin1_swedish_ci + + DEFAULT_COLLATION The default server collation + latin1_swedish_ci 5.5.7 + ENABLE_DEBUG_SYNC Whether to enable Debug Sync support ON 5.5.7 - ENABLE_DEBUG_SYNC Whether to enable Debug Sync support ON 5.5.7 ENABLE_DOWNLOADS Whether to download optional files OFF 5.5.7 + ENABLE_DTRACE Whether to include DTrace support 5.5.7 ENABLE_GCOV Whether to include gcov support 5.5.14 - ENABLED_LOCAL_INFILE Whether to enable LOCAL for LOAD DATA INFILE - OFF 5.5.7 - ENABLED_PROFILING Whether to enable query profiling code ON 5.5.7 - - IGNORE_AIO_CHECK With -DBUILD_CONFIG=mysql_release, ignore libaio - check OFF 5.5.9 + ENABLED_LOCAL_INFILE Whether to enable LOCAL for LOAD DATA + INFILE OFF 5.5.7 + ENABLED_PROFILING Whether to enable query profiling code ON + 5.5.7 + IGNORE_AIO_CHECK With -DBUILD_CONFIG=mysql_release, ignore + libaio check OFF 5.5.9 INSTALL_BINDIR User executables directory PREFIX/bin 5.5.7 INSTALL_DOCDIR Documentation directory PREFIX/docs 5.5.7 INSTALL_DOCREADMEDIR README file directory PREFIX 5.5.7 INSTALL_INCLUDEDIR Header file directory PREFIX/include 5.5.7 + INSTALL_INFODIR Info file directory PREFIX/docs 5.5.7 - INSTALL_LAYOUT Select predefined installation layout STANDALONE - 5.5.7 + INSTALL_LAYOUT Select predefined installation layout + STANDALONE 5.5.7 INSTALL_LIBDIR Library file directory PREFIX/lib 5.5.7 INSTALL_MANDIR Manual page directory PREFIX/man 5.5.7 - INSTALL_MYSQLSHAREDIR Shared data directory PREFIX/share 5.5.7 - INSTALL_MYSQLTESTDIR mysql-test directory PREFIX/mysql-test 5.5.7 - + INSTALL_MYSQLSHAREDIR Shared data directory PREFIX/share + 5.5.7 + INSTALL_MYSQLTESTDIR mysql-test directory PREFIX/mysql-test + 5.5.7 INSTALL_PLUGINDIR Plugin directory PREFIX/lib/plugin 5.5.7 INSTALL_SBINDIR Server executable directory PREFIX/bin 5.5.7 + INSTALL_SCRIPTDIR Scripts directory PREFIX/scripts 5.5.7 INSTALL_SHAREDIR aclocal/mysql.m4 installation directory PREFIX/share 5.5.7 @@ -5801,15 +6456,16 @@ PREFIX/support-files 5.5.7 MEMCACHED_HOME Path to memcached [none] 5.5.16-ndb-7.2.2 MYSQL_DATADIR Data directory 5.5.7 - MYSQL_MAINTAINER_MODE Whether to enable MySQL maintainer-specific - development environment OFF 5.5.7 - MYSQL_PROJECT_NAME Windows/Mac OS X project name 3306 5.5.21 + MYSQL_MAINTAINER_MODE Whether to enable MySQL + maintainer-specific development environment OFF 5.5.7 + MYSQL_PROJECT_NAME Windows/OS X project name 3306 5.5.21 MYSQL_TCP_PORT TCP/IP port number 3306 5.5.7 MYSQL_UNIX_ADDR Unix socket file /tmp/mysql.sock 5.5.7 ODBC_INCLUDES ODBC includes directory ODBC_LIB_DIR ODBC library directory SYSCONFDIR Option file directory 5.5.7 - WITH_ASAN Enable address sanitizer OFF 5.5.35 + TMPDIR tmpdir default value 5.5.36 + WITH_ASAN Enable AddressSanitizer OFF 5.5.35 WITH_BUNDLED_LIBEVENT Use bundled libevent when building ndbmemcache ON 5.5.16-ndb-7.2.2 WITH_BUNDLED_MEMCACHED Use bundled memcached when building @@ -5817,102 +6473,112 @@ WITH_CLASSPATH Classpath to use when building MySQL Cluster Connector for Java. Default is an empty string. WITH_DEBUG Whether to include debugging support OFF 5.5.7 - WITH_EMBEDDED_SERVER Whether to build embedded server OFF 5.5.7 - WITH_xxx_STORAGE_ENGINE Compile storage engine xxx statically into - server 5.5.7 + WITH_EMBEDDED_SERVER Whether to build embedded server OFF + 5.5.7 + WITH_EMBEDDED_SHARED_LIBRARY Whether to build a shared + embedded server library OFF 5.5.37 + WITH_xxx_STORAGE_ENGINE Compile storage engine xxx statically + into server 5.5.7 WITH_ERROR_INSERT Enable error injection in the NDB storage engine. Should not be used for building binaries intended for production. OFF WITH_EXTRA_CHARSETS Which extra character sets to include all 5.5.7 WITH_LIBEDIT Use bundled libedit library ON 5.5.7 - WITH_LIBWRAP Whether to include libwrap (TCP wrappers) support OFF - 5.5.7 - WITH_NDB_BINLOG Enable binary logging by default by mysqld. ON + WITH_LIBWRAP Whether to include libwrap (TCP wrappers) + support OFF 5.5.7 + WITH_NDB_BINLOG Enable binary logging by default by mysqld. + ON WITH_NDB_DEBUG Produce a debug build for testing or troubleshooting. OFF WITH_NDB_JAVA Enable building of Java and ClusterJ support. Enabled by default. Supported in MySQL Cluster only. ON 5.5.27-ndb-7.2.9 - WITH_NDB_PORT Default port used by a management server built with - this option. If this option was not used to build it, the - management server's default port is 1186. [none] + WITH_NDB_PORT Default port used by a management server built + with this option. If this option was not used to build it, + the management server's default port is 1186. [none] WITH_NDB_TEST Include NDB API test programs. OFF - WITH_NDBCLUSTER_STORAGE_ENGINE Build the NDB storage engine ON + WITH_NDBCLUSTER_STORAGE_ENGINE Build the NDB storage engine + ON WITH_NDBMTD Build multi-threaded data node. ON WITH_READLINE Use bundled readline library OFF 5.5.7 WITH_SSL Type of SSL support no 5.5.7 WITH_UNIXODBC Enable unixODBC support OFF + WITH_VALGRIND Whether to compile in Valgrind header files OFF + 5.5.6 WITH_ZLIB Type of zlib support system 5.5.7 - WITHOUT_xxx_STORAGE_ENGINE Exclude storage engine xxx from build - 5.5.7 + WITHOUT_xxx_STORAGE_ENGINE Exclude storage engine xxx from + build 5.5.7 WITHOUT_SERVER Do not build the server OFF The following sections provide more information about CMake options. - * General Options + * Section 2.9.4, "" - * Installation Layout Options + * Section 2.9.4, "" - * Feature Options + * Section 2.9.4, "" - * Options for Compiling MySQL Cluster + * Section 2.9.4, "" - * Compiler Flags + * Section 2.9.4, "" For boolean options, the value may be specified as 1 or ON to enable the option, or as 0 or OFF to disable the option. Many options configure compile-time defaults that can be overridden at server startup. For example, the - CMAKE_INSTALL_PREFIX, MYSQL_TCP_PORT, and MYSQL_UNIX_ADDR options - that configure the default installation base directory location, - TCP/IP port number, and Unix socket file can be changed at server - startup with the --basedir, --port, and --socket options for - mysqld. Where applicable, configuration option descriptions - indicate the corresponding mysqld startup option. + CMAKE_INSTALL_PREFIX, MYSQL_TCP_PORT, and MYSQL_UNIX_ADDR + options that configure the default installation base + directory location, TCP/IP port number, and Unix socket file + can be changed at server startup with the --basedir, --port, + and --socket options for mysqld. Where applicable, + configuration option descriptions indicate the corresponding + mysqld startup option. General Options * -DBUILD_CONFIG=mysql_release - This option configures a source distribution with the same - build options used by Oracle to produce binary distributions - for official MySQL releases. + This option configures a source distribution with the + same build options used by Oracle to produce binary + distributions for official MySQL releases. * -DCMAKE_BUILD_TYPE=type The type of build to produce: + RelWithDebInfo: Enable optimizations and generate - debugging information. This is the default MySQL build - type. + debugging information. This is the default MySQL + build type. + Debug: Disable optimizations and generate debugging information. This build type is also used if the - WITH_DEBUG option is enabled. That is, -DWITH_DEBUG=1 has - the same effect as -DCMAKE_BUILD_TYPE=Debug. + WITH_DEBUG option is enabled. That is, + -DWITH_DEBUG=1 has the same effect as + -DCMAKE_BUILD_TYPE=Debug. * -DCPACK_MONOLITHIC_INSTALL=bool This option affects whether the make package operation - produces multiple installation package files or a single file. - If disabled, the operation produces multiple installation - package files, which may be useful if you want to install only - a subset of a full MySQL installation. If enabled, it produces - a single file for installing everything. + produces multiple installation package files or a single + file. If disabled, the operation produces multiple + installation package files, which may be useful if you + want to install only a subset of a full MySQL + installation. If enabled, it produces a single file for + installing everything. Installation Layout Options - The CMAKE_INSTALL_PREFIX option indicates the base installation - directory. Other options with names of the form INSTALL_xxx that - indicate component locations are interpreted relative to the - prefix and their values are relative pathnames. Their values - should not include the prefix. + The CMAKE_INSTALL_PREFIX option indicates the base + installation directory. Other options with names of the form + INSTALL_xxx that indicate component locations are interpreted + relative to the prefix and their values are relative + pathnames. Their values should not include the prefix. * -DCMAKE_INSTALL_PREFIX=dir_name The installation base directory. - This value can be set at server startup with the --basedir - option. + This value can be set at server startup with the + --basedir option. * -DINSTALL_BINDIR=dir_name Where to install user programs. @@ -5941,10 +6607,11 @@ + DEB: DEB package layout (experimental). You can select a predefined layout but modify individual - component installation locations by specifying other options. - For example: + component installation locations by specifying other + options. For example: shell> cmake . -DINSTALL_LAYOUT=SVR4 -DMYSQL_DATADIR=/var/mysql/data + * -DINSTALL_LIBDIR=dir_name Where to install library files. @@ -5955,14 +6622,15 @@ Where to install shared data files. * -DINSTALL_MYSQLTESTDIR=dir_name - Where to install the mysql-test directory. As of MySQL 5.5.32, - to suppress installation of this directory, explicitly set the - option to the empty value (-DINSTALL_MYSQLTESTDIR=). + Where to install the mysql-test directory. As of MySQL + 5.5.32, to suppress installation of this directory, + explicitly set the option to the empty value + (-DINSTALL_MYSQLTESTDIR=). * -DINSTALL_PLUGINDIR=dir_name The location of the plugin directory. - This value can be set at server startup with the --plugin_dir - option. + This value can be set at server startup with the + --plugin_dir option. * -DINSTALL_SBINDIR=dir_name Where to install the mysqld server. @@ -5975,52 +6643,55 @@ * -DINSTALL_SQLBENCHDIR=dir_name Where to install the sql-bench directory. To suppress - installation of this directory, explicitly set the option to - the empty value (-DINSTALL_SQLBENCHDIR=). + installation of this directory, explicitly set the option + to the empty value (-DINSTALL_SQLBENCHDIR=). * -DINSTALL_SUPPORTFILESDIR=dir_name Where to install extra support files. * -DMYSQL_DATADIR=dir_name The location of the MySQL data directory. - This value can be set at server startup with the --datadir - option. + This value can be set at server startup with the + --datadir option. * -DODBC_INCLUDES=dir_name - The location of the ODBC includes directory, and may be used - while configuring Connector/ODBC. + The location of the ODBC includes directory, and may be + used while configuring Connector/ODBC. * -DODBC_LIB_DIR=dir_name - The location of the ODBC library directory, and may be used - while configuring Connector/ODBC. + The location of the ODBC library directory, and may be + used while configuring Connector/ODBC. * -DSYSCONFDIR=dir_name The default my.cnf option file directory. - This location cannot be set at server startup, but you can - start the server with a given option file using the - --defaults-file=file_name option, where file_name is the full - path name to the file. - - * -DWITH_UNIXODBC=1 - Enables unixODBC support, for Connector/ODBC. + This location cannot be set at server startup, but you + can start the server with a given option file using the + --defaults-file=file_name option, where file_name is the + full path name to the file. + + * -DTMPDIR=dir_name + The default location to use for the tmpdir system + variable. If unspecified, the value defaults to P_tmpdir + in . This option was added in MySQL 5.6.16. Storage Engine Options - Storage engines are built as plugins. You can build a plugin as a - static module (compiled into the server) or a dynamic module - (built as a dynamic library that must be installed into the server - using the INSTALL PLUGIN statement or the --plugin-load option - before it can be used). Some plugins might not support static or - dynamic building. - - The MyISAM, MERGE, MEMORY, and CSV engines are mandatory (always - compiled into the server) and need not be installed explicitly. + Storage engines are built as plugins. You can build a plugin + as a static module (compiled into the server) or a dynamic + module (built as a dynamic library that must be installed + into the server using the INSTALL PLUGIN statement or the + --plugin-load option before it can be used). Some plugins + might not support static or dynamic building. + + The MyISAM, MERGE, MEMORY, and CSV engines are mandatory + (always compiled into the server) and need not be installed + explicitly. To compile a storage engine statically into the server, use - -DWITH_engine_STORAGE_ENGINE=1. Some permissible engine values are - ARCHIVE, BLACKHOLE, EXAMPLE, FEDERATED, INNOBASE (InnoDB), - NDBCLUSTER (NDB), PARTITION (partitioning support), and PERFSCHEMA - (Performance Schema). Examples: + -DWITH_engine_STORAGE_ENGINE=1. Some permissible engine + values are ARCHIVE, BLACKHOLE, EXAMPLE, FEDERATED, INNOBASE + (InnoDB), NDBCLUSTER (NDB), PARTITION (partitioning support), + and PERFSCHEMA (Performance Schema). Examples: -DWITH_INNOBASE_STORAGE_ENGINE=1 -DWITH_ARCHIVE_STORAGE_ENGINE=1 -DWITH_BLACKHOLE_STORAGE_ENGINE=1 @@ -6028,14 +6699,14 @@ Note - WITH_NDBCLUSTER_STORAGE_ENGINE is supported only when building - MySQL Cluster using the MySQL Cluster sources. It cannot be used - to enable clustering support in other MySQL source trees or - distributions. In MySQL Cluster NDB 7.2 source distributions, it - is enabled by default. See Section 17.2.1.3, "Building MySQL - Cluster from Source on Linux," and Section 17.2.2.2, "Compiling - and Installing MySQL Cluster from Source on Windows," for more - information. + WITH_NDBCLUSTER_STORAGE_ENGINE is supported only when + building MySQL Cluster using the MySQL Cluster sources. It + cannot be used to enable clustering support in other MySQL + source trees or distributions. In MySQL Cluster NDB 7.2 + source distributions, it is enabled by default. See Section + 18.2.1.3, "Building MySQL Cluster from Source on Linux," and + Section 18.2.2.2, "Compiling and Installing MySQL Cluster + from Source on Windows," for more information. To exclude a storage engine from the build, use -DWITHOUT_engine_STORAGE_ENGINE=1. Examples: @@ -6044,9 +6715,9 @@ -DWITHOUT_PARTITION_STORAGE_ENGINE=1 If neither -DWITH_engine_STORAGE_ENGINE nor - -DWITHOUT_engine_STORAGE_ENGINE are specified for a given storage - engine, the engine is built as a shared module, or excluded if it - cannot be built as a shared module. + -DWITHOUT_engine_STORAGE_ENGINE are specified for a given + storage engine, the engine is built as a shared module, or + excluded if it cannot be built as a shared module. Feature Options @@ -6055,15 +6726,16 @@ A descriptive comment about the compilation environment. * -DDEFAULT_CHARSET=charset_name - The server character set. By default, MySQL uses the latin1 - (cp1252 West European) character set. + The server character set. By default, MySQL uses the + latin1 (cp1252 West European) character set. charset_name may be one of binary, armscii8, ascii, big5, - cp1250, cp1251, cp1256, cp1257, cp850, cp852, cp866, cp932, - dec8, eucjpms, euckr, gb2312, gbk, geostd8, greek, hebrew, - hp8, keybcs2, koi8r, koi8u, latin1, latin2, latin5, latin7, - macce, macroman, sjis, swe7, tis620, ucs2, ujis, utf8, - utf8mb4, utf16, utf32. The permissible character sets are - listed in the cmake/character_sets.cmake file as the value of + cp1250, cp1251, cp1256, cp1257, cp850, cp852, cp866, + cp932, dec8, eucjpms, euckr, gb2312, gbk, geostd8, greek, + hebrew, hp8, keybcs2, koi8r, koi8u, latin1, latin2, + latin5, latin7, macce, macroman, sjis, swe7, tis620, + ucs2, ujis, utf8, utf8mb4, utf16, utf32. The permissible + character sets are listed in the + cmake/character_sets.cmake file as the value of CHARSETS_AVAILABLE. This value can be set at server startup with the --character_set_server option. @@ -6071,99 +6743,108 @@ * -DDEFAULT_COLLATION=collation_name The server collation. By default, MySQL uses latin1_swedish_ci. Use the SHOW COLLATION statement to - determine which collations are available for each character - set. + determine which collations are available for each + character set. This value can be set at server startup with the --collation_server option. * -DENABLE_DEBUG_SYNC=bool - Whether to compile the Debug Sync facility into the server. - This facility is used for testing and debugging. This option - is enabled by default, but has no effect unless MySQL is - configured with debugging enabled. If debugging is enabled and - you want to disable Debug Sync, use -DENABLE_DEBUG_SYNC=0. + Whether to compile the Debug Sync facility into the + server. This facility is used for testing and debugging. + This option is enabled by default, but has no effect + unless MySQL is configured with debugging enabled. If + debugging is enabled and you want to disable Debug Sync, + use -DENABLE_DEBUG_SYNC=0. When compiled in, Debug Sync is disabled by default at runtime. To enable it, start mysqld with the --debug-sync-timeout=N option, where N is a timeout value - greater than 0. (The default value is 0, which disables Debug - Sync.) N becomes the default timeout for individual + greater than 0. (The default value is 0, which disables + Debug Sync.) N becomes the default timeout for individual synchronization points. - For a description of the Debug Sync facility and how to use - synchronization points, see MySQL Internals: Test + For a description of the Debug Sync facility and how to + use synchronization points, see MySQL Internals: Test Synchronization - (http://dev.mysql.com/doc/internals/en/test-synchronization.ht - ml). + (http://dev.mysql.com/doc/internals/en/test-synchronizati + on.html). * -DENABLE_DOWNLOADS=bool - Whether to download optional files. For example, with this - option enabled, CMake downloads the Google Test distribution - that is used by the test suite to run unit tests. + Whether to download optional files. For example, with + this option enabled, CMake downloads the Google Test + distribution that is used by the test suite to run unit + tests. * -DENABLE_DTRACE=bool - Whether to include support for DTrace probes. For information - about DTrace, wee Section 5.4, "Tracing mysqld Using DTrace" + Whether to include support for DTrace probes. For + information about DTrace, wee Section 5.4, "Tracing + mysqld Using DTrace" * -DENABLE_GCOV=bool Whether to include gcov support (Linux only). * -DENABLED_LOCAL_INFILE=bool - Whether to enable LOCAL capability in the client library for - LOAD DATA INFILE. - This option controls client-side LOCAL capability, but the - capability can be set on the server side at server startup - with the --local-infile option. See Section 6.1.6, "Security - Issues with LOAD DATA LOCAL." + Whether to enable LOCAL capability in the client library + for LOAD DATA INFILE. + This option controls client-side LOCAL capability, but + the capability can be set on the server side at server + startup with the --local-infile option. See Section + 6.1.6, "Security Issues with LOAD DATA LOCAL." * -DENABLED_PROFILING=bool - Whether to enable query profiling code (for the SHOW PROFILE - and SHOW PROFILES statements). + Whether to enable query profiling code (for the SHOW + PROFILE and SHOW PROFILES statements). * -DIGNORE_AIO_CHECK=bool - If the -DBUILD_CONFIG=mysql_release option is given on Linux, - the libaio library must be linked in by default. If you do not - have libaio or do not want to install it, you can suppress the - check for it by specifying -DIGNORE_AIO_CHECK=1. This option - was added in MySQL 5.5.9. + If the -DBUILD_CONFIG=mysql_release option is given on + Linux, the libaio library must be linked in by default. + If you do not have libaio or do not want to install it, + you can suppress the check for it by specifying + -DIGNORE_AIO_CHECK=1. This option was added in MySQL + 5.5.9. * -DMYSQL_MAINTAINER_MODE=bool Whether to enable a MySQL maintainer-specific development - environment. If enabled, this option causes compiler warnings - to become errors. + environment. If enabled, this option causes compiler + warnings to become errors. * -DMYSQL_PROJECT_NAME=name - For Windows or Mac OS X, the project name to incorporate into - the project file name. This option was added in MySQL 5.5.21. + For Windows or OS X, the project name to incorporate into + the project file name. This option was added in MySQL + 5.5.21. * -DMYSQL_TCP_PORT=port_num - The port number on on which the server listens for TCP/IP + The port number on which the server listens for TCP/IP connections. The default is 3306. This value can be set at server startup with the --port option. * -DMYSQL_UNIX_ADDR=file_name The Unix socket file path on which the server listens for - socket connections. This must be an absolute path name. The - default is /tmp/mysql.sock. + socket connections. This must be an absolute path name. + The default is /tmp/mysql.sock. This value can be set at server startup with the --socket option. * -DWITH_ASAN=bool - Whether to enable address sanitization, for compilers that - support it. The default is off. This option was added in MySQL - 5.5.35. + Whether to enable AddressSanitizer, for compilers that + support it. The default is off. This option was added in + MySQL 5.5.35. * -DWITH_DEBUG=bool Whether to include debugging support. - Configuring MySQL with debugging support enables you to use - the --debug="d,parser_debug" option when you start the server. - This causes the Bison parser that is used to process SQL - statements to dump a parser trace to the server's standard - error output. Typically, this output is written to the error - log. + Configuring MySQL with debugging support enables you to + use the --debug="d,parser_debug" option when you start + the server. This causes the Bison parser that is used to + process SQL statements to dump a parser trace to the + server's standard error output. Typically, this output is + written to the error log. * -DWITH_EMBEDDED_SERVER=bool Whether to build the libmysqld embedded server library. + * -DWITH_EMBEDDED_SHARED_LIBRARY=bool + Whether to build a shared libmysqld embedded server + library. This option was added in MySQL 5.5.37. + * -DWITH_EXTRA_CHARSETS=name Which extra character sets to include: @@ -6196,462 +6877,535 @@ distribution. + system: Use the system SSL library. - For information about using SSL support, see Section 6.3.8, - "Using SSL for Secure Connections." + For information about using SSL support, see Section + 6.3.9, "Using SSL for Secure Connections." + + * -DWITH_UNIXODBC=1 + Enables unixODBC support, for Connector/ODBC. + + * -DWITH_VALGRIND=bool + Whether to compile in the Valgrind header files, which + exposes the Valgrind API to MySQL code. The default is + OFF. + To generate a Valgrind-aware debug build, + -DWITH_VALGRIND=1 normally is combined with + -DWITH_DEBUG=1. See Building Debug Configurations + (http://dev.mysql.com/doc/internals/en/debug-configuratio + ns.html). * -DWITH_ZLIB=zlib_type Some features require that the server be built with compression library support, such as the COMPRESS() and - UNCOMPRESS() functions, and compression of the client/server - protocol. The WITH_ZLIB indicates the source of zlib support: + UNCOMPRESS() functions, and compression of the + client/server protocol. The WITH_ZLIB indicates the + source of zlib support: + bundled: Use the zlib library bundled with the distribution. - + system: Use the system zlib library. This is the default. + + system: Use the system zlib library. This is the + default. * -DWITHOUT_SERVER=bool - Whether to build without the MySQL server. The default is OFF, - which does build the server. + Whether to build without the MySQL server. The default is + OFF, which does build the server. Compiler Flags - To specify compiler flags, set the CFLAGS and CXXFLAGS environment - variables before running CMake. Example: -shell> CFLAGS=-DHAVE_EMBEDDED_PRIVILEGE_CONTROL -shell> CXXFLAGS=-DHAVE_EMBEDDED_PRIVILEGE_CONTROL -shell> export CFLAGS CXXFLAGS -shell> cmake [options] - - The following flags control configuration features: - - * HAVE_EMBEDDED_PRIVILEGE_CONTROL - By default, authentication for connections to the embedded - server is disabled. To enable connection authentication, - define this flag. + + * -DCMAKE_C_FLAGS="flags" + Flags for the C Compiler. + + * -DCMAKE_CXX_FLAGS="flags" + Flags for the C++ Compiler. + + To specify your own C and C++ compiler flags, for flags that + do not affect optimization, use the CMAKE_C_FLAGS and + CMAKE_CXX_FLAGS CMake options. + + When providing your own compiler flags, you might want to + specify CMAKE_BUILD_TYPE as well. + + For example, to create a 32-bit release build on a 64-bit + Linux machine, do this: +shell> mkdir bld +shell> cd bld +shell> cmake .. -DCMAKE_C_FLAGS=-m32 \ + -DCMAKE_CXX_FLAGS=-m32 \ + -DCMAKE_BUILD_TYPE=RelWithDebInfo + + If you set flags that affect optimization (-Onumber), you + must set the CMAKE_C_FLAGS_build_type and/or + CMAKE_CXX_FLAGS_build_type options, where build_type + corresponds to the CMAKE_BUILD_TYPE value. To specify a + different optimization for the default build type + (RelWithDebInfo) set the CMAKE_C_FLAGS_RELWITHDEBINFO and + CMAKE_CXX_FLAGS_RELWITHDEBINFO options. For example, to + compile on Linux with -O3 and with debug symbols, do this: +shell> cmake .. -DCMAKE_C_FLAGS_RELWITHDEBINFO="-O3 -g" \ + -DCMAKE_CXX_FLAGS_RELWITHDEBINFO="-O3 -g" CMake Options for Compiling MySQL Cluster - The following options are for use when building MySQL Cluster NDB - 7.2 or later. These options are supported only with the MySQL - Cluster NDB 7.2 and later MySQL Cluster sources; they are not - supported when using sources from the MySQL 5.5 Server tree. + The following options are for use when building MySQL Cluster + NDB 7.2 or later. These options are supported only with the + MySQL Cluster NDB 7.2 and later MySQL Cluster sources; they + are not supported when using sources from the MySQL 5.5 + Server tree. * -DMEMCACHED_HOME=path - Perform the build using the memcached (version 1.6 or later) - installed in the system directory indicated by path. Files - from this installation that are used in the build include the - memcached binary, header files, and libraries, as well as the - memcached_utilities library and the header file - engine_testapp.h. - You must leave this option unset when building ndbmemcache - using the bundled memcached sources (WITH_BUNDLED_MEMCACHED - option); in other words, the bundled sources are used by - default). + Perform the build using the memcached (version 1.6 or + later) installed in the system directory indicated by + path. Files from this installation that are used in the + build include the memcached binary, header files, and + libraries, as well as the memcached_utilities library and + the header file engine_testapp.h. + You must leave this option unset when building + ndbmemcache using the bundled memcached sources + (WITH_BUNDLED_MEMCACHED option); in other words, the + bundled sources are used by default). This option was added in MySQL Cluster NDB 7.2.2. While additional CMake options---such as for SASL - authorization and for providing dtrace support---are available - for use when compiling memcached from external sources, these - options are currently not enabled for the memcached sources - bundled with MySQL Cluster. + authorization and for providing dtrace support---are + available for use when compiling memcached from external + sources, these options are currently not enabled for the + memcached sources bundled with MySQL Cluster. * -DWITH_BUNDLED_LIBEVENT={ON|OFF} - Use the libevent included in the MySQL Cluster sources when - building MySQL Cluster with ndbmemcached support (MySQL - Cluster NDB 7.2.2 and later). Enabled by default. OFF causes - the system's libevent to be used instead. + Use the libevent included in the MySQL Cluster sources + when building MySQL Cluster with ndbmemcached support + (MySQL Cluster NDB 7.2.2 and later). Enabled by default. + OFF causes the system's libevent to be used instead. * -DWITH_BUNDLED_MEMCACHED={ON|OFF} Build the memcached sources included in the MySQL Cluster - source tree (MySQL Cluster NDB 7.2.3 and later), then use the - resulting memcached server when building the ndbmemcache - engine. In this case, make install places the memcached binary - in the installation bin directory, and the ndbmemcache engine - shared object file ndb_engine.so in the installation lib - directory. + source tree (MySQL Cluster NDB 7.2.3 and later), then use + the resulting memcached server when building the + ndbmemcache engine. In this case, make install places the + memcached binary in the installation bin directory, and + the ndbmemcache engine shared object file ndb_engine.so + in the installation lib directory. This option is ON by default. * -DWITH_CLASSPATH=path - Sets the classpath for building MySQL Cluster Connector for - Java. Default is empty. In MySQL Cluster NDB 7.2.9 and later, - this option is ignored if -DWITH_NDB_JAVA=OFF is used. + Sets the classpath for building MySQL Cluster Connector + for Java. The default is empty. In MySQL Cluster NDB + 7.2.9 and later, this option is ignored if + -DWITH_NDB_JAVA=OFF is used. * -DWITH_ERROR_INSERT={ON|OFF} - Enables error injection in the NDB kernel. For testing only; - not intended for use in building production binaries. Default - is OFF. + Enables error injection in the NDB kernel. For testing + only; not intended for use in building production + binaries. The default is OFF. * -DWITH_NDBCLUSTER_STORAGE_ENGINE={ON|OFF} - Build and link in support for the NDB (NDBCLUSTER) storage - engine in mysqld. Default is ON. + Build and link in support for the NDB (NDBCLUSTER) + storage engine in mysqld. The default is ON. * -DWITH_NDBCLUSTER={ON|OFF} This is an alias for WITH_NDBCLUSTER_STORAGE_ENGINE. * -DWITH_NDBMTD={ON|OFF} - Build the multi-threaded data node executable ndbmtd. Default - is ON. + Build the multi-threaded data node executable ndbmtd. The + default is ON. * -DWITH_NDB_BINLOG={ON|OFF} - Enable binary logging by default in the mysqld built using - this option. ON by default. + Enable binary logging by default in the mysqld built + using this option. ON by default. * -DWITH_NDB_DEBUG={ON|OFF} Enable building the debug versions of the MySQL Cluster binaries. OFF by default. * -DWITH_NDB_JAVA={ON|OFF} - Enable building MySQL Cluster with Java support, including - ClusterJ. - This option was added in MySQL Cluster NDB 7.2.9, and is ON by - default. If you do not wish to compile MySQL Cluster with Java - support, you must disable it explicitly by specifying - -DWITH_NDB_JAVA=OFF when running CMake. Otherwise, if Java - cannot be found, configuration of the build fails. + Enable building MySQL Cluster with Java support, + including ClusterJ. + This option was added in MySQL Cluster NDB 7.2.9, and is + ON by default. If you do not wish to compile MySQL + Cluster with Java support, you must disable it explicitly + by specifying -DWITH_NDB_JAVA=OFF when running CMake. + Otherwise, if Java cannot be found, configuration of the + build fails. * -DWITH_NDB_PORT=port - Causes the MySQL Cluster management server (ndb_mgmd) that is - built to use this port by default. If this option is unset, - the resulting management server tries to use port 1186 by - default. + Causes the MySQL Cluster management server (ndb_mgmd) + that is built to use this port by default. If this option + is unset, the resulting management server tries to use + port 1186 by default. * -DWITH_NDB_TEST={ON|OFF} If enabled, include a set of NDB API test programs. The default is OFF. -2.10.5. Dealing with Problems Compiling MySQL +2.9.5 Dealing with Problems Compiling MySQL - The solution to many problems involves reconfiguring. If you do - reconfigure, take note of the following: + The solution to many problems involves reconfiguring. If you + do reconfigure, take note of the following: - * If CMake is run after it has previously been run, it may use - information that was gathered during its previous invocation. - This information is stored in CMakeCache.txt. When CMake - starts up, it looks for that file and reads its contents if it - exists, on the assumption that the information is still - correct. That assumption is invalid when you reconfigure. - - * Each time you run CMake, you must run make again to recompile. - However, you may want to remove old object files from previous - builds first because they were compiled using different - configuration options. + * If CMake is run after it has previously been run, it may + use information that was gathered during its previous + invocation. This information is stored in CMakeCache.txt. + When CMake starts up, it looks for that file and reads + its contents if it exists, on the assumption that the + information is still correct. That assumption is invalid + when you reconfigure. + + * Each time you run CMake, you must run make again to + recompile. However, you may want to remove old object + files from previous builds first because they were + compiled using different configuration options. To prevent old object files or configuration information from - being used, run these commands on Unix before re-running CMake: + being used, run the following commands before re-running + CMake: + + On Unix: shell> make clean shell> rm CMakeCache.txt - Or, on Windows: + On Windows: shell> devenv MySQL.sln /clean shell> del CMakeCache.txt - If you build out of the source tree, remove and recreate your - build directory before re-running CMake. For instructions on - building outside of the source tree, see How to Build MySQL Server - with CMake (http://dev.mysql.com/doc/internals/en/cmake.html). - - On some systems, warnings may occur due to differences in system - include files. The following list describes other problems that - have been found to occur most often when compiling MySQL: - - * To define flags to be used by your C or C++ compilers, specify - them using the CFLAGS and CXXFLAGS environment variables. You - can also specify the compiler names this way using CC and CXX. - For example: + If you build outside of the source tree, remove and recreate + your build directory before re-running CMake. For + instructions on building outside of the source tree, see How + to Build MySQL Server with CMake + (http://dev.mysql.com/doc/internals/en/cmake.html). + + On some systems, warnings may occur due to differences in + system include files. The following list describes other + problems that have been found to occur most often when + compiling MySQL: + + * To define which C and C++ compilers to use, you can + define the CC and CXX environment variables. For example: shell> CC=gcc -shell> CFLAGS=-O3 -shell> CXX=gcc -shell> CXXFLAGS=-O3 -shell> export CC CFLAGS CXX CXXFLAGS +shell> CXX=g++ +shell> export CC CXX + + To specify your own C and C++ compiler flags, use the + CMAKE_C_FLAGS and CMAKE_CXX_FLAGS CMake options. See + Section 2.9.4, "." To see what flags you might need to specify, invoke mysql_config with the --cflags option. - * If compilation fails, check whether the MYSQL_MAINTAINER_MODE - option is enabled. This mode causes compiler warnings to - become errors, so disabling it may enable compilation to - proceed. + * To see what commands are executed during the compile + stage, after using CMake to configure MySQL, run make + VERBOSE=1 rather than just make. + + * If compilation fails, check whether the + MYSQL_MAINTAINER_MODE option is enabled. This mode causes + compiler warnings to become errors, so disabling it may + enable compilation to proceed. * If your compile fails with errors such as any of the - following, you must upgrade your version of make to GNU make: + following, you must upgrade your version of make to GNU + make: make: Fatal error in reader: Makefile, line 18: Badly formed macro assignment + Or: make: file `Makefile' line 18: Must be a separator (: + Or: pthread.h: No such file or directory + Solaris and FreeBSD are known to have troublesome make programs. GNU make 3.75 is known to work. - * The sql_yacc.cc file is generated from sql_yacc.yy. Normally, - the build process does not need to create sql_yacc.cc because - MySQL comes with a pregenerated copy. However, if you do need - to re-create it, you might encounter this error: + * The sql_yacc.cc file is generated from sql_yacc.yy. + Normally, the build process does not need to create + sql_yacc.cc because MySQL comes with a pregenerated copy. + However, if you do need to re-create it, you might + encounter this error: "sql_yacc.yy", line xxx fatal: default action causes potential... - This is a sign that your version of yacc is deficient. You - probably need to install bison (the GNU version of yacc) and - use that instead. + + This is a sign that your version of yacc is deficient. + You probably need to install a recent version of bison + (the GNU version of yacc) and use that instead. Versions of bison older than 1.75 may report this error: sql_yacc.yy:#####: fatal error: maximum table size (32767) exceeded - The maximum table size is not actually exceeded; the error is - caused by bugs in older versions of bison. - - For information about acquiring or updating tools, see the system - requirements in Section 2.10, "Installing MySQL from Source." -2.10.6. MySQL Configuration and Third-Party Tools + The maximum table size is not actually exceeded; the + error is caused by bugs in older versions of bison. - Third-party tools that need to determine the MySQL version from - the MySQL source can read the VERSION file in the top-level source - directory. The file lists the pieces of the version separately. - For example, if the version is 5.5.8, the file looks like this: + For information about acquiring or updating tools, see the + system requirements in Section 2.9, "Installing MySQL from + Source." + +2.9.6 MySQL Configuration and Third-Party Tools + + Third-party tools that need to determine the MySQL version + from the MySQL source can read the VERSION file in the + top-level source directory. The file lists the pieces of the + version separately. For example, if the version is MySQL + 5.7.4-m14, the file looks like this: MYSQL_VERSION_MAJOR=5 -MYSQL_VERSION_MINOR=5 -MYSQL_VERSION_PATCH=8 -MYSQL_VERSION_EXTRA= - - If the source is not for a General Availability (GA) release, the - MYSQL_VERSION_EXTRA value will be nonempty. For example, the value - for a Release Candidate release would look like this: -MYSQL_VERSION_EXTRA=rc - - To construct a five-digit number from the version components, use - this formula: -MYSQL_VERSION_MAJOR*10000 + MYSQL_VERSION_MINOR*100 + MYSQL_VERSION_P -ATCH - -2.11. Postinstallation Setup and Testing - - This section discusses post-installation items for Unix-like - systems. If you are using Windows, see Section 2.3.10, "Windows - Postinstallation Procedures." - - After installing MySQL, there are some items that you should - address. For example: - - * You should initialize the data directory and create the MySQL - grant tables, as describe in Section 2.11.1, "Postinstallation - Procedures for Unix-like Systems." - - * An important security concern is that the initial accounts in - the grant tables have no passwords. You should assign - passwords to prevent unauthorized access to the MySQL server. - For instructions, see Section 2.11.2, "Securing the Initial +MYSQL_VERSION_MINOR=7 +MYSQL_VERSION_PATCH=4 +MYSQL_VERSION_EXTRA=-m14 + + If the source is not for a General Availablility (GA) + release, the MYSQL_VERSION_EXTRA value will be nonempty. For + the example, the value corresponds to Milestone 14. + + To construct a five-digit number from the version components, + use this formula: +MYSQL_VERSION_MAJOR*10000 + MYSQL_VERSION_MINOR*100 + MYSQL_VERSION_PA +TCH + +2.10 Postinstallation Setup and Testing + + This section discusses postinstallation tasks for Unix-like + systems. + + After installing MySQL, there are some tasks that you should + perform: + + * You should initialize the data directory and create the + MySQL grant tables. If you are using Windows, see Section + 2.3.10, "Windows Postinstallation Procedures." For Unix + systems, see Section 2.10.1, "Postinstallation Procedures + for Unix-like Systems." + + * After you complete the procedure and have the server + running, any initial accounts in the grant tables should + be assigned passwords, if that was not already done + during data directory initialization. Passwords prevent + unauthorized access to the MySQL server. You may also + wish to restrict access to test databases. For + instructions, see Section 2.10.2, "Securing the Initial MySQL Accounts." - * Optionally, you can create time zone tables to enable - recognition of named time zones. For instructions, see Section - 4.4.6, "mysql_tzinfo_to_sql --- Load the Time Zone Tables." - - * If you have trouble getting the server to start, see Section - 2.11.1.3, "Starting and Troubleshooting the MySQL Server." - - * When you are ready to create additional user accounts, you can - find information on the MySQL access control system and - account management in Section 6.2, "The MySQL Access Privilege - System," and Section 6.3, "MySQL User Account Management." - -2.11.1. Postinstallation Procedures for Unix-like Systems - - After installing MySQL on a Unix-like system, you must initialize - the grant tables, start the server, and make sure that the server - works satisfactorily. You may also wish to arrange for the server - to be started and stopped automatically when your system starts - and stops. You should also assign passwords to the accounts in the - grant tables. - - On a Unix-like system, the grant tables are set up by the - mysql_install_db program. For some installation methods, this - program is run for you automatically if an existing database - cannot be found. - - * If you install MySQL on Linux using RPM distributions, the - server RPM runs mysql_install_db. - - * Using the native packaging system on many platforms, including - Debian Linux, Ubuntu Linux, Gentoo Linux and others, the - mysql_install_db command is run for you. - - * If you install MySQL on Mac OS X using a DMG distribution, the - installer runs mysql_install_db. - - For other platforms and installation types, including generic - binary and source installs, you will need to run mysql_install_db - yourself. - - The following procedure describes how to initialize the grant - tables (if that has not previously been done) and start the - server. It also suggests some commands that you can use to test - whether the server is accessible and working properly. For - information about starting and stopping the server automatically, - see Section 2.11.1.2, "Starting and Stopping MySQL Automatically." - - After you complete the procedure and have the server running, you - should assign passwords to the accounts created by - mysql_install_db and perhaps restrict access to test databases. - For instructions, see Section 2.11.2, "Securing the Initial MySQL - Accounts." + * You may wish to arrange for the server to start and stop + automatically when your system starts and stops. For + instructions, see Section 2.10.3, "Starting and Stopping + MySQL Automatically." - In the examples shown here, the server runs under the user ID of - the mysql login account. This assumes that such an account exists. - Either create the account if it does not exist, or substitute the - name of a different existing login account that you plan to use - for running the server. For information about creating the - account, see Creating a mysql System User and Group, in Section - 2.2, "Installing MySQL on Unix/Linux Using Generic Binaries." + * Optionally, you can create time zone tables to enable + recognition of named time zones. For instructions, see + Section 4.4.6, "mysql_tzinfo_to_sql --- Load the Time + Zone Tables." + + If you have trouble starting the server, see Section 2.10.4, + "Troubleshooting Problems Starting the MySQL Server." + + When you are ready to create additional user accounts, you + can find information on the MySQL access control system and + account management in Section 6.2, "The MySQL Access + Privilege System," and Section 6.3, "MySQL User Account + Management." + +2.10.1 Postinstallation Procedures for Unix-like Systems + + After installing MySQL on a Unix-like system, you must + initialize the data directory (including the tables in the + mysql system database), start the server, and make sure that + the server works satisfactorily. You should also assign + passwords to any accounts listed in the mysql.user grant + table + + On a Unix-like system, the grant tables in the mysql database + are set up by the mysql_install_db program. For some + installation methods, this program is run for you + automatically if an existing mysql database cannot be found: + + * If you install MySQL on Linux using server RPM + distributions. + + * Using the native packaging system on many platforms, + including Debian Linux, Ubuntu Linux, Gentoo Linux, and + others. + + * If you install MySQL on OS X using a DMG distribution. + + For other platforms and installation types, including + installation from generic binary and source distributions, + you must initialize the data directory yourself. + + The following procedure describes how to initialize the data + directory (if that has not previously been done) and start + the server. It also suggests some commands that you can use + to test whether the server is accessible and working + properly. + + In the examples shown here, the server runs under the user ID + of the mysql login account. This assumes that such an account + exists. Either create the account if it does not exist, or + substitute the name of a different existing login account + that you plan to use for running the server. For information + about creating the account, see Creating a mysql System User + and Group, in Section 2.2, "Installing MySQL on Unix/Linux + Using Generic Binaries." - 1. Change location into the top-level directory of your MySQL - installation, represented here by BASEDIR: + 1. Change location into the top-level directory of your + MySQL installation, represented here by BASEDIR: shell> cd BASEDIR - BASEDIR is the installation directory for your MySQL instance. - It is likely to be something like /usr/local/mysql or - /usr/local. The following steps assume that you have changed - location to this directory. - You will find several files and subdirectories in the BASEDIR - directory. The most important for installation purposes are - the bin and scripts subdirectories: + + BASEDIR is the installation directory for your MySQL + instance. It is likely to be something like + /usr/local/mysql or /usr/local. The following steps + assume that you have changed location to this directory. + You will find several files and subdirectories in the + BASEDIR directory. The most important for installation + purposes are the bin and scripts subdirectories: + The bin directory contains client programs and the - server. You should add the full path name of this - directory to your PATH environment variable so that your - shell finds the MySQL programs properly. See Section - 2.13, "Environment Variables." + server. To make it more convenient to invoke + programs installed in the bin directory under the + installation directory, you can add that directory + to your PATH environment variable setting. That + enables your shell to find MySQL programs properly, + so that you can run a program by typing only its + name, not its entire path name. See Section 4.2.10, + "Setting Environment Variables." + The scripts directory contains the mysql_install_db - script used to initialize the mysql database containing - the grant tables that store the server access - permissions. + program used to initialize the mysql database + containing the grant tables that store the server + access permissions. 2. If necessary, ensure that the distribution contents are accessible to mysql. If you installed the distribution as - mysql, no further action is required. If you installed the - distribution as root, its contents will be owned by root. - Change its ownership to mysql by executing the following - commands as root in the installation directory. The first - command changes the owner attribute of the files to the mysql - user. The second changes the group attribute to the mysql - group. -shell> chown -R mysql . + mysql, no further action is required. If you installed + the distribution as root, its contents will be owned by + root. This is suitable for most of the installation, with + the exception that the data directory must be owned by + mysql. To accomplish this, run the following commands as + root in the installation directory. For some distribution + types, the data directory might be named var rather than + data; adjust the second command accordingly. +shell> chown -R root . +shell> chown -R mysql data shell> chgrp -R mysql . - 3. If necessary, run the mysql_install_db program to set up the - initial MySQL grant tables containing the privileges that - determine how users are permitted to connect to the server. - You will need to do this if you used a distribution type for - which the installation procedure does not run the program for - you. + + 3. If necessary, run the mysql_install_db program to set up + the initial MySQL grant tables containing the privileges + that determine how users are permitted to connect to the + server. You must do this if you used a distribution type + for which the installation procedure does not run the + program for you. shell> scripts/mysql_install_db --user=mysql - Typically, mysql_install_db needs to be run only the first - time you install MySQL, so you can skip this step if you are - upgrading an existing installation, However, mysql_install_db - does not overwrite any existing privilege tables, so it should - be safe to run in any circumstances. + + Typically, mysql_install_db needs to be run only the + first time you install MySQL, so you can skip this step + if you are upgrading an existing installation, However, + mysql_install_db does not overwrite any existing + privilege tables, so it should be safe to run in any + circumstances. It might be necessary to specify other options such as - --basedir or --datadir if mysql_install_db does not identify - the correct locations for the installation directory or data - directory. For example: + --basedir or --datadir if mysql_install_db does not + identify the correct locations for the installation + directory or data directory. For example: shell> scripts/mysql_install_db --user=mysql \ --basedir=/opt/mysql/mysql \ --datadir=/opt/mysql/mysql/data - The mysql_install_db script creates the server's data - directory with mysql as the owner. Under the data directory, - it creates directories for the mysql database that holds the - grant tables and the test database that you can use to test - MySQL. The script also creates privilege table entries for - root and anonymous-user accounts. The accounts have no - passwords initially. Section 2.11.2, "Securing the Initial - MySQL Accounts," describes the initial privileges. Briefly, - these privileges permit the MySQL root user to do anything, - and permit anybody to create or use databases with a name of + + The mysql_install_db program creates the server's data + directory with mysql as the owner. Under the data + directory, it creates directories for the mysql database + that holds the grant tables and the test database that + you can use to test MySQL. The script also creates + privilege table entries for root and anonymous-user + accounts. The accounts have no passwords initially. + Section 2.10.2, "Securing the Initial MySQL Accounts," + describes the initial privileges. Briefly, these + privileges permit the MySQL root user to do anything, and + permit anybody to create or use databases with a name of test or starting with test_. See Section 6.2, "The MySQL Access Privilege System," for a complete listing and description of the grant tables. - It is important to make sure that the database directories and - files are owned by the mysql login account so that the server - has read and write access to them when you run it later. To - ensure this if you run mysql_install_db as root, include the - --user option as shown. Otherwise, you should execute the - script while logged in as mysql, in which case you can omit - the --user option from the command. - If you do not want to have the test database, you can remove - it after starting the server, using the instructions in - Section 2.11.2, "Securing the Initial MySQL Accounts." - If you have trouble with mysql_install_db at this point, see - Section 2.11.1.1, "Problems Running mysql_install_db." - - 4. Most of the MySQL installation can be owned by root if you - like. The exception is that the data directory must be owned - by mysql. To accomplish this, run the following commands as - root in the installation directory: -shell> chown -R root . -shell> chown -R mysql data - - 5. If the plugin directory (the directory named by the plugin_dir - system variable) is writable by the server, it may be possible - for a user to write executable code to a file in the directory - using SELECT ... INTO DUMPFILE. This can be prevented by - making plugin_dir read only to the server or by setting - --secure-file-priv to a directory where SELECT writes can be - made safely. - - 6. If you installed MySQL using a source distribution, you may - want to optionally copy one of the provided configuration - files from the support-files directory into your /etc - directory. There are different sample configuration files for - different use cases, server types, and CPU and RAM - configurations. If you want to use one of these standard - files, you should copy it to /etc/my.cnf, or /etc/mysql/my.cnf - and edit and check the configuration before starting your - MySQL server for the first time. - If you do not copy one of the standard configuration files, - the MySQL server will be started with the default settings. - If you want MySQL to start automatically when you boot your - machine, you can copy support-files/mysql.server to the - location where your system has its startup files. More - information can be found in the mysql.server script itself, - and in Section 2.11.1.2, "Starting and Stopping MySQL - Automatically." + It is important to make sure that the database + directories and files are owned by the mysql login + account so that the server has read and write access to + them when you run it later. To ensure this if you run + mysql_install_db as root, include the --user option as + shown. Otherwise, you should execute the program while + logged in as mysql, in which case you can omit the --user + option from the command. + If you do not want to have the test database, you can + remove it after starting the server, using the + instructions in Section 2.10.2, "Securing the Initial + MySQL Accounts." + If you have trouble with mysql_install_db at this point, + see Section 2.10.1.1, "Problems Running + mysql_install_db." + + 4. If the plugin directory (the directory named by the + plugin_dir system variable) is writable by the server, it + may be possible for a user to write executable code to a + file in the directory using SELECT ... INTO DUMPFILE. + This can be prevented by making plugin_dir read only to + the server or by setting --secure-file-priv to a + directory where SELECT writes can be made safely. + + 5. If you installed MySQL using a source distribution, you + may want to optionally copy one of the provided + configuration files from the support-files directory into + your /etc directory. There are different sample + configuration files for different use cases, server + types, and CPU and RAM configurations. If you want to use + one of these standard files, you should copy it to + /etc/my.cnf, or /etc/mysql/my.cnf and edit and check the + configuration before starting your MySQL server for the + first time. + If you do not copy one of the standard configuration + files, the MySQL server will be started with the default + settings. + If you want MySQL to start automatically when you boot + your machine, you can copy support-files/mysql.server to + the location where your system has its startup files. + More information can be found in the mysql.server script + itself, and in Section 2.10.3, "Starting and Stopping + MySQL Automatically." - 7. Start the MySQL server: + 6. Start the MySQL server: shell> bin/mysqld_safe --user=mysql & + It is important that the MySQL server be run using an - unprivileged (non-root) login account. To ensure this if you - run mysqld_safe as root, include the --user option as shown. - Otherwise, you should execute the script while logged in as - mysql, in which case you can omit the --user option from the - command. - For further instructions for running MySQL as an unprivileged - user, see Section 6.1.5, "How to Run MySQL as a Normal User." - If the command fails immediately and prints mysqld ended, look - for information in the error log (which by default is the - host_name.err file in the data directory). - If you neglected to create the grant tables by running - mysql_install_db before proceeding to this step, the following - message appears in the error log file when you start the - server: -mysqld: Can't find file: 'host.frm' - This error also occurs if you run mysql_install_db as root - without the --user option. Remove the data directory and run - mysql_install_db with the --user option as described - previously. - If you have other problems starting the server, see Section - 2.11.1.3, "Starting and Troubleshooting the MySQL Server." For - more information about mysqld_safe, see Section 4.3.2, - "mysqld_safe --- MySQL Server Startup Script." - - 8. Use mysqladmin to verify that the server is running. The - following commands provide simple tests to check whether the - server is up and responding to connections: + unprivileged (non-root) login account. To ensure this if + you run mysqld_safe as root, include the --user option as + shown. Otherwise, you should execute the program while + logged in as mysql, in which case you can omit the --user + option from the command. + For further instructions for running MySQL as an + unprivileged user, see Section 6.1.5, "How to Run MySQL + as a Normal User." + If the command fails immediately and prints mysqld ended, + look for information in the error log (which by default + is the host_name.err file in the data directory). + If the server is unable to access the data directory it + starts or read the grant tables in the mysql database, it + writes a message to its error log. Such problems can + occur if you neglected to create the grant tables by + initializing the data directory before proceeding to this + step, or if you ran the command that initializes the data + directory without the --user option. Remove the data + directory and run the command with the --user option as + described previously. + If you have other problems starting the server, see + Section 2.10.4, "Troubleshooting Problems Starting the + MySQL Server." For more information about mysqld_safe, + see Section 4.3.2, "mysqld_safe --- MySQL Server Startup + Script." + + 7. Use mysqladmin to verify that the server is running. The + following commands provide simple tests to check whether + the server is up and responding to connections: shell> bin/mysqladmin version shell> bin/mysqladmin variables - The output from mysqladmin version varies slightly depending - on your platform and version of MySQL, but should be similar - to that shown here: + + The output from mysqladmin version varies slightly + depending on your platform and version of MySQL, but + should be similar to that shown here: shell> bin/mysqladmin version -mysqladmin Ver 14.12 Distrib 5.5.36, for pc-linux-gnu on i686 +mysqladmin Ver 14.12 Distrib 5.5.44, for pc-linux-gnu on i686 ... -Server version 5.5.36 +Server version 5.5.44 Protocol version 10 Connection Localhost via UNIX socket UNIX socket /var/lib/mysql/mysql.sock @@ -6660,19 +7414,24 @@ Threads: 1 Questions: 366 Slow queries: 0 Opens: 0 Flush tables: 1 Open tables: 19 Queries per second avg: 0.000 - To see what else you can do with mysqladmin, invoke it with - the --help option. - 9. Verify that you can shut down the server: + To see what else you can do with mysqladmin, invoke it + with the --help option. + + 8. Verify that you can shut down the server: shell> bin/mysqladmin -u root shutdown - 10. Verify that you can start the server again. Do this by using - mysqld_safe or by invoking mysqld directly. For example: + + + 9. Verify that you can start the server again. Do this by + using mysqld_safe or by invoking mysqld directly. For + example: shell> bin/mysqld_safe --user=mysql & - If mysqld_safe fails, see Section 2.11.1.3, "Starting and - Troubleshooting the MySQL Server." - 11. Run some simple tests to verify that you can retrieve - information from the server. The output should be similar to - what is shown here: + + If mysqld_safe fails, see Section 2.10.4, + "Troubleshooting Problems Starting the MySQL Server." + 10. Run some simple tests to verify that you can retrieve + information from the server. The output should be similar + to what is shown here: shell> bin/mysqlshow +--------------------+ | Databases | @@ -6716,287 +7475,525 @@ | % | test | | | % | test_% | | +------+--------+------+ - 12. There is a benchmark suite in the sql-bench directory (under - the MySQL installation directory) that you can use to compare - how MySQL performs on different platforms. The benchmark suite - is written in Perl. It requires the Perl DBI module that - provides a database-independent interface to the various - databases, and some other additional Perl modules: -DBI -DBD::mysql -Data::Dumper -Data::ShowTable - These modules can be obtained from CPAN - (http://www.cpan.org/). See also Section 2.14.1, "Installing - Perl on Unix." - The sql-bench/Results directory contains the results from many - runs against different databases and platforms. To run all - tests, execute these commands: -shell> cd sql-bench -shell> perl run-all-tests - If you do not have the sql-bench directory, you probably - installed MySQL using RPM files other than the source RPM. - (The source RPM includes the sql-bench benchmark directory.) - In this case, you must first install the benchmark suite - before you can use it. There are separate benchmark RPM files - named mysql-bench-VERSION.i386.rpm that contain benchmark code - and data. - If you have a source distribution, there are also tests in its - tests subdirectory that you can run. For example, to run - auto_increment.tst, execute this command from the top-level - directory of your source distribution: -shell> mysql -vvf test < ./tests/auto_increment.tst - The expected result of the test can be found in the - ./tests/auto_increment.res file. - 13. At this point, you should have the server running. However, - none of the initial MySQL accounts have a password, and the - server permits permissive access to test databases. To tighten - security, follow the instructions in Section 2.11.2, "Securing - the Initial MySQL Accounts." - - The MySQL 5.5 installation procedure creates time zone tables in - the mysql database but does not populate them. To do so, use the - instructions in Section 10.6, "MySQL Server Time Zone Support." - - To make it more convenient to invoke programs installed in the bin - directory under the installation directory, you can add that - directory to your PATH environment variable setting. That enables - you to run a program by typing only its name, not its entire path - name. See Section 4.2.4, "Setting Environment Variables." + + 11. At this point, you should have the server running. + However, none of the initial MySQL accounts have a + password, and the server permits permissive access to + test databases. To tighten security, follow the + instructions in Section 2.10.2, "Securing the Initial + MySQL Accounts." + + The MySQL 5.5 installation procedure creates time zone tables + in the mysql database but does not populate them. To do so, + use the instructions in Section 10.6, "MySQL Server Time Zone + Support." You can set up new accounts using the bin/mysql_setpermission - script if you install the DBI and DBD::mysql Perl modules. See - Section 4.6.13, "mysql_setpermission --- Interactively Set - Permissions in Grant Tables." For Perl module installation - instructions, see Section 2.14, "Perl Installation Notes." + script if you install the DBI and DBD::mysql Perl modules. + See Section 4.6.13, "mysql_setpermission --- Interactively + Set Permissions in Grant Tables." For Perl module + installation instructions, see Section 2.13, "Perl + Installation Notes." If you would like to use mysqlaccess and have the MySQL - distribution in some nonstandard location, you must change the - location where mysqlaccess expects to find the mysql client. Edit - the bin/mysqlaccess script at approximately line 18. Search for a - line that looks like this: + distribution in some nonstandard location, you must change + the location where mysqlaccess expects to find the mysql + client. Edit the bin/mysqlaccess script at approximately line + 18. Search for a line that looks like this: $MYSQL = '/usr/local/bin/mysql'; # path to mysql executable - Change the path to reflect the location where mysql actually is - stored on your system. If you do not do this, a Broken pipe error - will occur when you run mysqlaccess. - -2.11.1.1. Problems Running mysql_install_db - - The purpose of the mysql_install_db script is to generate new - MySQL privilege tables. It does not overwrite existing MySQL - privilege tables, and it does not affect any other data. - - If you want to re-create your privilege tables, first stop the - mysqld server if it is running. Then rename the mysql directory - under the data directory to save it, and then run - mysql_install_db. Suppose that your current directory is the MySQL - installation directory and that mysql_install_db is located in the - bin directory and the data directory is named data. To rename the - mysql database and re-run mysql_install_db, use these commands. + Change the path to reflect the location where mysql actually + is stored on your system. If you do not do this, a Broken + pipe error will occur when you run mysqlaccess. + +2.10.1.1 Problems Running mysql_install_db + + The purpose of the mysql_install_db program is to initialize + the data directory, including the tables in the mysql system + database. It does not overwrite existing MySQL privilege + tables, and it does not affect any other data. + + To re-create your privilege tables, first stop the mysqld + server if it is running. Then rename the mysql directory + under the data directory to save it, and run + mysql_install_db. Suppose that your current directory is the + MySQL installation directory and that mysql_install_db is + located in the bin directory and the data directory is named + data. To rename the mysql database and re-run + mysql_install_db, use these commands. shell> mv data/mysql data/mysql.old shell> scripts/mysql_install_db --user=mysql - When you run mysql_install_db, you might encounter the following - problems: + When you run mysql_install_db, you might encounter the + following problems: * mysql_install_db fails to install the grant tables - You may find that mysql_install_db fails to install the grant - tables and terminates after displaying the following messages: + You may find that mysql_install_db fails to install the + grant tables and terminates after displaying the + following messages: Starting mysqld daemon with databases from XXXXXX mysqld ended + In this case, you should examine the error log file very - carefully. The log should be located in the directory XXXXXX - named by the error message and should indicate why mysqld did - not start. If you do not understand what happened, include the - log when you post a bug report. See Section 1.7, "How to - Report Bugs or Problems." + carefully. The log should be located in the directory + XXXXXX named by the error message and should indicate why + mysqld did not start. If you do not understand what + happened, include the log when you post a bug report. See + Section 1.7, "How to Report Bugs or Problems." * There is a mysqld process running - This indicates that the server is running, in which case the - grant tables have probably been created already. If so, there - is no need to run mysql_install_db at all because it needs to - be run only once (when you install MySQL the first time). + This indicates that the server is running, in which case + the grant tables have probably been created already. If + so, there is no need to run mysql_install_db at all + because it needs to be run only once, when you first + install MySQL. * Installing a second mysqld server does not work when one server is running - This can happen when you have an existing MySQL installation, - but want to put a new installation in a different location. - For example, you might have a production installation, but you - want to create a second installation for testing purposes. - Generally the problem that occurs when you try to run a second - server is that it tries to use a network interface that is in - use by the first server. In this case, you should see one of - the following error messages: + This can happen when you have an existing MySQL + installation, but want to put a new installation in a + different location. For example, you might have a + production installation, but you want to create a second + installation for testing purposes. Generally the problem + that occurs when you try to run a second server is that + it tries to use a network interface that is in use by the + first server. In this case, you should see one of the + following error messages: Can't start server: Bind on TCP/IP port: Address already in use Can't start server: Bind on unix socket... - For instructions on setting up multiple servers, see Section - 5.3, "Running Multiple MySQL Instances on One Machine." + + For instructions on setting up multiple servers, see + Section 5.3, "Running Multiple MySQL Instances on One + Machine." * You do not have write access to the /tmp directory - If you do not have write access to create temporary files or a - Unix socket file in the default location (the /tmp directory) - or the TMP_DIR environment variable, if it has been set, an - error occurs when you run mysql_install_db or the mysqld - server. + If you do not have write access to create temporary files + or a Unix socket file in the default location (the /tmp + directory) or the TMPDIR environment variable, if it has + been set, an error occurs when you run mysql_install_db + or the mysqld server. You can specify different locations for the temporary - directory and Unix socket file by executing these commands - prior to starting mysql_install_db or mysqld, where - some_tmp_dir is the full path name to some directory for which - you have write permission: + directory and Unix socket file by executing these + commands prior to starting mysql_install_db or mysqld, + where some_tmp_dir is the full path name to some + directory for which you have write permission: shell> TMPDIR=/some_tmp_dir/ shell> MYSQL_UNIX_PORT=/some_tmp_dir/mysql.sock shell> export TMPDIR MYSQL_UNIX_PORT - Then you should be able to run mysql_install_db and start the - server with these commands: + + Then you should be able to run mysql_install_db and start + the server with these commands: shell> scripts/mysql_install_db --user=mysql shell> bin/mysqld_safe --user=mysql & + If mysql_install_db is located in the scripts directory, modify the first command to scripts/mysql_install_db. - See Section C.5.4.5, "How to Protect or Change the MySQL Unix - Socket File," and Section 2.13, "Environment Variables." + See Section B.5.4.5, "How to Protect or Change the MySQL + Unix Socket File," and Section 2.12, "Environment + Variables." - There are some alternatives to running the mysql_install_db script - provided in the MySQL distribution: + There are some alternatives to running the mysql_install_db + program provided in the MySQL distribution: - * If you want the initial privileges to be different from the - standard defaults, you can modify mysql_install_db before you - run it. However, it is preferable to use GRANT and REVOKE to - change the privileges after the grant tables have been set up. - In other words, you can run mysql_install_db, and then use - mysql -u root mysql to connect to the server as the MySQL root - user so that you can issue the necessary GRANT and REVOKE - statements. - If you want to install MySQL on several machines with the same - privileges, you can put the GRANT and REVOKE statements in a - file and execute the file as a script using mysql after + * If you want the initial privileges to be different from + the standard defaults, use account-management statements + such as CREATE USER, GRANT, and REVOKE to change the + privileges after the grant tables have been set up. In + other words, run mysql_install_db, and then use mysql -u + root mysql to connect to the server as the MySQL root + user so that you can issue the necessary statements. (See + xref linkend="account-management-sql"/>.) + To install MySQL on several machines with the same + privileges, put the GRANT and REVOKE statements in a file + and execute the file as a script using mysql after running mysql_install_db. For example: shell> scripts/mysql_install_db --user=mysql shell> bin/mysql -u root < your_script_file - By doing this, you can avoid having to issue the statements - manually on each machine. - * It is possible to re-create the grant tables completely after - they have previously been created. You might want to do this - if you are just learning how to use GRANT and REVOKE and have - made so many modifications after running mysql_install_db that - you want to wipe out the tables and start over. - To re-create the grant tables, remove all the .frm, .MYI, and - .MYD files in the mysql database directory. Then run the - mysql_install_db script again. - - * You can start mysqld manually using the --skip-grant-tables - option and add the privilege information yourself using mysql: -shell> bin/mysqld_safe --user=mysql --skip-grant-tables & -shell> bin/mysql mysql - From mysql, manually execute the SQL commands contained in - mysql_install_db. Make sure that you run mysqladmin - flush-privileges or mysqladmin reload afterward to tell the - server to reload the grant tables. - Note that by not using mysql_install_db, you not only have to - populate the grant tables manually, you also have to create - them first. + This enables you to avoid issuing the statements manually + on each machine. -2.11.1.2. Starting and Stopping MySQL Automatically + * It is possible to re-create the grant tables completely + after they have previously been created. You might want + to do this if you are just learning how to use GRANT and + REVOKE and have made so many modifications after running + mysql_install_db that you want to wipe out the tables and + start over. + To re-create the grant tables, stop the server if it is + running and remove the mysql database directory. Then run + mysql_install_db again. + +2.10.2 Securing the Initial MySQL Accounts + + Part of the MySQL installation process is to set up, in the + data directory, the mysql database that contains the grant + tables: - Generally, you start the mysqld server in one of these ways: + * Windows distributions contain preinitialized grant + tables. - * Invoke mysqld directly. This works on any platform. + * On Unix, the mysql_install_db program populates the grant + tables. Some installation methods run this program for + you. Others require that you execute it manually. For + details, see Section 2.10.1, "Postinstallation Procedures + for Unix-like Systems." + + The mysql.user grant table defines the initial MySQL user + accounts and their access privileges: + + * Some accounts have the user name root. These are + superuser accounts that have all privileges and can do + anything. The initial root account passwords are empty, + so anyone can connect to the MySQL server as root without + a password and be granted all privileges. - * Invoke mysqld_safe, which tries to determine the proper - options for mysqld and then runs it with those options. This - script is used on Unix and Unix-like systems. See Section - 4.3.2, "mysqld_safe --- MySQL Server Startup Script." - - * Invoke mysql.server. This script is used primarily at system - startup and shutdown on systems that use System V-style run - directories (that is, /etc/init.d and run-level specific - directories), where it usually is installed under the name - mysql. The mysql.server script starts the server by invoking - mysqld_safe. See Section 4.3.3, "mysql.server --- MySQL Server - Startup Script." - - * On Mac OS X, install a separate MySQL Startup Item package to - enable the automatic startup of MySQL on system startup. The - Startup Item starts the server by invoking mysql.server. See - Section 2.4.3, "Installing the MySQL Startup Item," for - details. A MySQL Preference Pane also provides control for - starting and stopping MySQL through the System Preferences, - see Section 2.4.4, "Installing and Using the MySQL Preference - Pane." - - * Use the Solaris/OpenSolaris service management framework (SMF) - system to initiate and control MySQL startup. For more - information, see Section 2.7.2, "Installing MySQL on - OpenSolaris Using IPS." + + On Windows, root accounts are created that permit + connections from the local host only. Connections + can be made by specifying the host name localhost, + the IP address 127.0.0.1, or the IPv6 address ::1. + If the user selects the Enable root access from + remote machines option during installation, the + Windows installer creates another root account that + permits connections from any host. + + + On Unix, each root account permits connections from + the local host. Connections can be made by + specifying the host name localhost, the IP address + 127.0.0.1, the IPv6 address ::1, or the actual host + name or IP address. + An attempt to connect to the host 127.0.0.1 normally + resolves to the localhost account. However, this fails if + the server is run with the --skip-name-resolve option, so + the 127.0.0.1 account is useful in that case. The ::1 + account is used for IPv6 connections. + + * If accounts for anonymous users were created, these have + an empty user name. The anonymous accounts have no + password, so anyone can use them to connect to the MySQL + server. - The mysqld_safe and mysql.server scripts, Solaris/OpenSolaris SMF, - and the Mac OS X Startup Item (or MySQL Preference Pane) can be - used to start the server manually, or automatically at system - startup time. mysql.server and the Startup Item also can be used - to stop the server. + + On Windows, there is one anonymous account that + permits connections from the local host. Connections + can be made by specifying a host name of localhost. + + + On Unix, each anonymous account permits connections + from the local host. Connections can be made by + specifying a host name of localhost for one of the + accounts, or the actual host name or IP address for + the other. + + To display which accounts exist in the mysql.user table and + check whether their passwords are empty, use the following + statement: +mysql> SELECT User, Host, Password FROM mysql.user; ++------+--------------------+----------+ +| User | Host | Password | ++------+--------------------+----------+ +| root | localhost | | +| root | myhost.example.com | | +| root | 127.0.0.1 | | +| root | ::1 | | +| | localhost | | +| | myhost.example.com | | ++------+--------------------+----------+ - To start or stop the server manually using the mysql.server - script, invoke it with start or stop arguments: -shell> mysql.server start -shell> mysql.server stop + This output indicates that there are several root and + anonymous-user accounts, none of which have passwords. The + output might differ on your system, but the presence of + accounts with empty passwords means that your MySQL + installation is unprotected until you do something about it: + + * You should assign a password to each MySQL root account + that does not have one. + + * If you want to prevent clients from connecting as + anonymous users without a password, you should either + assign a password to each anonymous account or else + remove the accounts. - Before mysql.server starts the server, it changes location to the - MySQL installation directory, and then invokes mysqld_safe. If you - want the server to run as some specific user, add an appropriate - user option to the [mysqld] group of the /etc/my.cnf option file, - as shown later in this section. (It is possible that you will need - to edit mysql.server if you've installed a binary distribution of - MySQL in a nonstandard location. Modify it to change location into - the proper directory before it runs mysqld_safe. If you do this, - your modified version of mysql.server may be overwritten if you - upgrade MySQL in the future, so you should make a copy of your - edited version that you can reinstall.) + In addition, the mysql.db table contains rows that permit all + accounts to access the test database and other databases with + names that start with test_. This is true even for accounts + that otherwise have no special privileges such as the default + anonymous accounts. This is convenient for testing but + inadvisable on production servers. Administrators who want + database access restricted only to accounts that have + permissions granted explicitly for that purpose should remove + these mysql.db table rows. + + The following instructions describe how to set up passwords + for the initial MySQL accounts, first for the root accounts, + then for the anonymous accounts. The instructions also cover + how to remove the anonymous accounts, should you prefer not + to permit anonymous access at all, and describe how to remove + permissive access to test databases. Replace newpwd in the + examples with the password that you want to use. Replace + host_name with the name of the server host. You can determine + this name from the output of the preceding SELECT statement. + For the output shown, host_name is myhost.example.com. + Note + + For additional information about setting passwords, see + Section 6.3.5, "Assigning Account Passwords." If you forget + your root password after setting it, see Section B.5.4.1, + "How to Reset the Root Password." - mysql.server stop stops the server by sending a signal to it. You - can also stop the server manually by executing mysqladmin - shutdown. + You might want to defer setting the passwords until later, to + avoid the need to specify them while you perform additional + setup or testing. However, be sure to set them before using + your installation for production purposes. + + To set up additional accounts, see Section 6.3.2, "Adding + User Accounts." + Note - To start and stop MySQL automatically on your server, you need to - add start and stop commands to the appropriate places in your - /etc/rc* files. + On Windows, you can also perform the process described in + this section using the Configuration Wizard (see Section + 2.3.6.11, "The Security Options Dialog"). On all platforms, + the MySQL distribution includes mysql_secure_installation, a + command-line utility that automates much of the process of + securing a MySQL installation. - If you use the Linux server RPM package - (MySQL-server-VERSION.rpm), or a native Linux package - installation, the mysql.server script may be installed in the - /etc/init.d directory with the name mysql. See Section 2.5.1, - "Installing MySQL on Linux Using RPM Packages," for more - information on the Linux RPM packages. +Assigning root Account Passwords + + A root account password can be set several ways. The + following discussion demonstrates three methods: + + * Use the SET PASSWORD statement + + * Use the UPDATE statement + + * Use the mysqladmin command-line client program + + To assign passwords using SET PASSWORD, connect to the server + as root and issue a SET PASSWORD statement for each root + account listed in the mysql.user table. Be sure to encrypt + the password using the PASSWORD() function. + + For Windows, do this: +shell> mysql -u root +mysql> SET PASSWORD FOR 'root'@'localhost' = PASSWORD('newpwd'); +mysql> SET PASSWORD FOR 'root'@'127.0.0.1' = PASSWORD('newpwd'); +mysql> SET PASSWORD FOR 'root'@'::1' = PASSWORD('newpwd'); +mysql> SET PASSWORD FOR 'root'@'%' = PASSWORD('newpwd'); + + The last statement is unnecessary if the mysql.user table has + no root account with a host value of %. + + For Unix, do this: +shell> mysql -u root +mysql> SET PASSWORD FOR 'root'@'localhost' = PASSWORD('newpwd'); +mysql> SET PASSWORD FOR 'root'@'127.0.0.1' = PASSWORD('newpwd'); +mysql> SET PASSWORD FOR 'root'@'::1' = PASSWORD('newpwd'); +mysql> SET PASSWORD FOR 'root'@'host_name' = PASSWORD('newpwd'); + + You can also use a single statement that assigns a password + to all root accounts by using UPDATE to modify the mysql.user + table directly. This method works on any platform: +shell> mysql -u root +mysql> UPDATE mysql.user SET Password = PASSWORD('newpwd') + -> WHERE User = 'root'; +mysql> FLUSH PRIVILEGES; + + The FLUSH statement causes the server to reread the grant + tables. Without it, the password change remains unnoticed by + the server until you restart it. + + To assign passwords to the root accounts using mysqladmin, + execute the following commands: +shell> mysqladmin -u root password "newpwd" +shell> mysqladmin -u root -h host_name password "newpwd" + + Those commands apply both to Windows and to Unix. The double + quotation marks around the password are not always necessary, + but you should use them if the password contains spaces or + other characters that are special to your command + interpreter. + + The mysqladmin method of setting the root account passwords + does not work for the 'root'@'127.0.0.1' or 'root'@'::1' + account. Use the SET PASSWORD method shown earlier. + + After the root passwords have been set, you must supply the + appropriate password whenever you connect as root to the + server. For example, to shut down the server with mysqladmin, + use this command: +shell> mysqladmin -u root -p shutdown +Enter password: (enter root password here) + +Assigning Anonymous Account Passwords + + The mysql commands in the following instructions include a -p + option based on the assumption that you have set the root + account passwords using the preceding instructions and must + specify that password when connecting to the server. + + To assign passwords to the anonymous accounts, connect to the + server as root, then use either SET PASSWORD or UPDATE. Be + sure to encrypt the password using the PASSWORD() function. + + To use SET PASSWORD on Windows, do this: +shell> mysql -u root -p +Enter password: (enter root password here) +mysql> SET PASSWORD FOR ''@'localhost' = PASSWORD('newpwd'); + + To use SET PASSWORD on Unix, do this: +shell> mysql -u root -p +Enter password: (enter root password here) +mysql> SET PASSWORD FOR ''@'localhost' = PASSWORD('newpwd'); +mysql> SET PASSWORD FOR ''@'host_name' = PASSWORD('newpwd'); + + To set the anonymous-user account passwords with a single + UPDATE statement, do this (on any platform): +shell> mysql -u root -p +Enter password: (enter root password here) +mysql> UPDATE mysql.user SET Password = PASSWORD('newpwd') + -> WHERE User = ''; +mysql> FLUSH PRIVILEGES; + + The FLUSH statement causes the server to reread the grant + tables. Without it, the password change remains unnoticed by + the server until you restart it. + +Removing Anonymous Accounts + + If you prefer to remove any anonymous accounts rather than + assigning them passwords, do so as follows on Windows: +shell> mysql -u root -p +Enter password: (enter root password here) +mysql> DROP USER ''@'localhost'; + + On Unix, remove the anonymous accounts like this: +shell> mysql -u root -p +Enter password: (enter root password here) +mysql> DROP USER ''@'localhost'; +mysql> DROP USER ''@'host_name'; + +Securing Test Databases + + By default, the mysql.db table contains rows that permit + access by any user to the test database and other databases + with names that start with test_. (These rows have an empty + User column value, which for access-checking purposes matches + any user name.) This means that such databases can be used + even by accounts that otherwise possess no privileges. If you + want to remove any-user access to test databases, do so as + follows: +shell> mysql -u root -p +Enter password: (enter root password here) +mysql> DELETE FROM mysql.db WHERE Db LIKE 'test%'; +mysql> FLUSH PRIVILEGES; + + The FLUSH statement causes the server to reread the grant + tables. Without it, the privilege change remains unnoticed by + the server until you restart it. + + With the preceding change, only users who have global + database privileges or privileges granted explicitly for the + test database can use it. However, if you do not want the + database to exist at all, drop it: +mysql> DROP DATABASE test; + +2.10.3 Starting and Stopping MySQL Automatically + + Generally, you start the mysqld server in one of these ways: + + * Invoke mysqld directly. This works on any platform. + + * Invoke mysqld_safe, which tries to determine the proper + options for mysqld and then runs it with those options. + This script is used on Unix and Unix-like systems. See + Section 4.3.2, "mysqld_safe --- MySQL Server Startup + Script." + + * Invoke mysql.server. This script is used primarily at + system startup and shutdown on systems that use System + V-style run directories (that is, /etc/init.d and + run-level specific directories), where it usually is + installed under the name mysql. The mysql.server script + starts the server by invoking mysqld_safe. See Section + 4.3.3, "mysql.server --- MySQL Server Startup Script." + + * On OS X, install a separate MySQL Startup Item package to + enable the automatic startup of MySQL on system startup. + The Startup Item starts the server by invoking + mysql.server. See Section 2.4.4, "Installing the MySQL + Startup Item," for details. A MySQL Preference Pane also + provides control for starting and stopping MySQL through + the System Preferences, see Section 2.4.5, "Installing + and Using the MySQL Preference Pane." + + * Use the Solaris/OpenSolaris service management framework + (SMF) system to initiate and control MySQL startup. For + more information, see Section 2.7.2, "Installing MySQL on + OpenSolaris Using IPS." + + The mysqld_safe and mysql.server scripts, Solaris/OpenSolaris + SMF, and the OS X Startup Item (or MySQL Preference Pane) can + be used to start the server manually, or automatically at + system startup time. mysql.server and the Startup Item also + can be used to stop the server. + + To start or stop the server manually using the mysql.server + script, invoke it with start or stop arguments: +shell> mysql.server start +shell> mysql.server stop + + Before mysql.server starts the server, it changes location to + the MySQL installation directory, and then invokes + mysqld_safe. If you want the server to run as some specific + user, add an appropriate user option to the [mysqld] group of + the /etc/my.cnf option file, as shown later in this section. + (It is possible that you must edit mysql.server if you've + installed a binary distribution of MySQL in a nonstandard + location. Modify it to change location into the proper + directory before it runs mysqld_safe. If you do this, your + modified version of mysql.server may be overwritten if you + upgrade MySQL in the future, so you should make a copy of + your edited version that you can reinstall.) + + mysql.server stop stops the server by sending a signal to it. + You can also stop the server manually by executing mysqladmin + shutdown. + + To start and stop MySQL automatically on your server, you + must add start and stop commands to the appropriate places in + your /etc/rc* files. + + If you use the Linux server RPM package + (MySQL-server-VERSION.rpm), or a native Linux package + installation, the mysql.server script may be installed in the + /etc/init.d directory with the name mysql. See Section 2.5.1, + "Installing MySQL on Linux Using RPM Packages," for more + information on the Linux RPM packages. - Some vendors provide RPM packages that install a startup script - under a different name such as mysqld. + Some vendors provide RPM packages that install a startup + script under a different name such as mysqld. - If you install MySQL from a source distribution or using a binary - distribution format that does not install mysql.server + If you install MySQL from a source distribution or using a + binary distribution format that does not install mysql.server automatically, you can install it manually. The script can be - found in the support-files directory under the MySQL installation - directory or in a MySQL source tree. + found in the support-files directory under the MySQL + installation directory or in a MySQL source tree. To install mysql.server manually, copy it to the /etc/init.d - directory with the name mysql, and then make it executable. Do - this by changing location into the appropriate directory where - mysql.server is located and executing these commands: + directory with the name mysql, and then make it executable: shell> cp mysql.server /etc/init.d/mysql shell> chmod +x /etc/init.d/mysql Note - Older Red Hat systems use the /etc/rc.d/init.d directory rather - than /etc/init.d. Adjust the preceding commands accordingly. - Alternatively, first create /etc/init.d as a symbolic link that - points to /etc/rc.d/init.d: + Older Red Hat systems use the /etc/rc.d/init.d directory + rather than /etc/init.d. Adjust the preceding commands + accordingly. Alternatively, first create /etc/init.d as a + symbolic link that points to /etc/rc.d/init.d: shell> cd /etc shell> ln -s rc.d/init.d . - After installing the script, the commands needed to activate it to - run at system startup depend on your operating system. On Linux, - you can use chkconfig: + After installing the script, the commands needed to activate + it to run at system startup depend on your operating system. + On Linux, you can use chkconfig: shell> chkconfig --add mysql On some Linux systems, the following command also seems to be @@ -7004,25 +8001,26 @@ shell> chkconfig --level 345 mysql on On FreeBSD, startup scripts generally should go in - /usr/local/etc/rc.d/. The rc(8) manual page states that scripts in - this directory are executed only if their basename matches the - *.sh shell file name pattern. Any other files or directories - present within the directory are silently ignored. In other words, - on FreeBSD, you should install the mysql.server script as - /usr/local/etc/rc.d/mysql.server.sh to enable automatic startup. - - As an alternative to the preceding setup, some operating systems - also use /etc/rc.local or /etc/init.d/boot.local to start - additional services on startup. To start up MySQL using this - method, you could append a command like the one following to the + /usr/local/etc/rc.d/. The rc(8) manual page states that + scripts in this directory are executed only if their basename + matches the *.sh shell file name pattern. Any other files or + directories present within the directory are silently + ignored. In other words, on FreeBSD, you should install the + mysql.server script as /usr/local/etc/rc.d/mysql.server.sh to + enable automatic startup. + + As an alternative to the preceding setup, some operating + systems also use /etc/rc.local or /etc/init.d/boot.local to + start additional services on startup. To start up MySQL using + this method, append a command like the one following to the appropriate startup file: /bin/sh -c 'cd /usr/local/mysql; ./bin/mysqld_safe --user=mysql &' - For other systems, consult your operating system documentation to - see how to install startup scripts. + For other systems, consult your operating system + documentation to see how to install startup scripts. - You can add options for mysql.server in a global /etc/my.cnf file. - A typical /etc/my.cnf file might look like this: + You can add options for mysql.server in a global /etc/my.cnf + file. A typical /etc/my.cnf file might look like this: [mysqld] datadir=/usr/local/mysql/var socket=/var/tmp/mysql.sock @@ -7032,15 +8030,16 @@ [mysql.server] basedir=/usr/local/mysql - The mysql.server script supports the following options: basedir, - datadir, and pid-file. If specified, they must be placed in an - option file, not on the command line. mysql.server supports only - start and stop as command-line arguments. + The mysql.server script supports the following options: + basedir, datadir, and pid-file. If specified, they must be + placed in an option file, not on the command line. + mysql.server supports only start and stop as command-line + arguments. - The following table shows which option groups the server and each - startup script read from option files. + The following table shows which option groups the server and + each startup script read from option files. - Table 2.17. MySQL Startup scripts and supported server option + Table 2.14 MySQL Startup scripts and supported server option groups Script Option Groups mysqld [mysqld], [server], [mysqld-major_version] @@ -7048,95 +8047,98 @@ mysql.server [mysqld], [mysql.server], [server] [mysqld-major_version] means that groups with names like - [mysqld-5.1] and [mysqld-5.5] are read by servers having versions - 5.1.x, 5.5.x, and so forth. This feature can be used to specify - options that can be read only by servers within a given release - series. + [mysqld-5.1] and [mysqld-5.5] are read by servers having + versions 5.1.x, 5.5.x, and so forth. This feature can be used + to specify options that can be read only by servers within a + given release series. For backward compatibility, mysql.server also reads the - [mysql_server] group and mysqld_safe also reads the [safe_mysqld] - group. However, you should update your option files to use the - [mysql.server] and [mysqld_safe] groups instead when using MySQL - 5.5. + [mysql_server] group and mysqld_safe also reads the + [safe_mysqld] group. However, you should update your option + files to use the [mysql.server] and [mysqld_safe] groups + instead. For more information on MySQL configuration files and their - structure and contents, see Section 4.2.3.3, "Using Option Files." + structure and contents, see Section 4.2.6, "Using Option + Files." -2.11.1.3. Starting and Troubleshooting the MySQL Server +2.10.4 Troubleshooting Problems Starting the MySQL Server - This section provides troubleshooting suggestions for problems - starting the server on a Unix-like system. If you are using - Windows, see Section 2.3.8, "Troubleshooting a Microsoft Windows - MySQL Server Installation." + This section provides troubleshooting suggestions for + problems starting the server. For additional suggestions for + Windows systems, see Section 2.3.8, "Troubleshooting a + Microsoft Windows MySQL Server Installation." - If you have problems starting the server, here are some things to - try: + If you have problems starting the server, here are some + things to try: * Check the error log to see why the server does not start. - * Specify any special options needed by the storage engines you - are using. + * Specify any special options needed by the storage engines + you are using. * Make sure that the server knows where to find the data directory. - * Make sure that the server can access the data directory. The - ownership and permissions of the data directory and its - contents must be set such that the server can read and modify - them. - - * Verify that the network interfaces the server wants to use are - available. - - Some storage engines have options that control their behavior. You - can create a my.cnf file and specify startup options for the - engines that you plan to use. If you are going to use storage - engines that support transactional tables (InnoDB, NDB), be sure - that you have them configured the way you want before starting the - server: + * Make sure that the server can access the data directory. + The ownership and permissions of the data directory and + its contents must be set such that the server can read + and modify them. + + * Verify that the network interfaces the server wants to + use are available. + + Some storage engines have options that control their + behavior. You can create a my.cnf file and specify startup + options for the engines that you plan to use. If you are + going to use storage engines that support transactional + tables (InnoDB, NDB), be sure that you have them configured + the way you want before starting the server: - If you are using InnoDB tables, see Section 14.3.7, "InnoDB + If you are using InnoDB tables, see Section 14.6, "InnoDB Configuration." Storage engines will use default option values if you specify - none, but it is recommended that you review the available options - and specify explicit values for those for which the defaults are - not appropriate for your installation. - - When the mysqld server starts, it changes location to the data - directory. This is where it expects to find databases and where it - expects to write log files. The server also writes the pid - (process ID) file in the data directory. - - The data directory location is hardwired in when the server is - compiled. This is where the server looks for the data directory by - default. If the data directory is located somewhere else on your - system, the server will not work properly. You can determine what - the default path settings are by invoking mysqld with the - --verbose and --help options. + none, but it is recommended that you review the available + options and specify explicit values for those for which the + defaults are not appropriate for your installation. + + When the mysqld server starts, it changes location to the + data directory. This is where it expects to find databases + and where it expects to write log files. The server also + writes the pid (process ID) file in the data directory. + + The data directory location is hardwired in when the server + is compiled. This is where the server looks for the data + directory by default. If the data directory is located + somewhere else on your system, the server will not work + properly. You can determine what the default path settings + are by invoking mysqld with the --verbose and --help options. If the default locations do not match the MySQL installation - layout on your system, you can override them by specifying options - to mysqld or mysqld_safe on the command line or in an option file. - - To specify the location of the data directory explicitly, use the - --datadir option. However, normally you can tell mysqld the - location of the base directory under which MySQL is installed and - it looks for the data directory there. You can do this with the - --basedir option. - - To check the effect of specifying path options, invoke mysqld with - those options followed by the --verbose and --help options. For - example, if you change location into the directory where mysqld is - installed and then run the following command, it shows the effect - of starting the server with a base directory of /usr/local: + layout on your system, you can override them by specifying + options to mysqld or mysqld_safe on the command line or in an + option file. + + To specify the location of the data directory explicitly, use + the --datadir option. However, normally you can tell mysqld + the location of the base directory under which MySQL is + installed and it looks for the data directory there. You can + do this with the --basedir option. + + To check the effect of specifying path options, invoke mysqld + with those options followed by the --verbose and --help + options. For example, if you change location into the + directory where mysqld is installed and then run the + following command, it shows the effect of starting the server + with a base directory of /usr/local: shell> ./mysqld --basedir=/usr/local --verbose --help You can specify other options such as --datadir as well, but --verbose and --help must be the last options. - Once you determine the path settings you want, start the server - without --verbose and --help. + Once you determine the path settings you want, start the + server without --verbose and --help. If mysqld is currently running, you can find out what path settings it is using by executing this command: @@ -7149,393 +8151,138 @@ If you get Errcode 13 (which means Permission denied) when starting mysqld, this means that the privileges of the data - directory or its contents do not permit server access. In this - case, you change the permissions for the involved files and - directories so that the server has the right to use them. You can - also start the server as root, but this raises security issues and - should be avoided. - - Change location into the data directory and check the ownership of - the data directory and its contents to make sure the server has - access. For example, if the data directory is + directory or its contents do not permit server access. In + this case, you change the permissions for the involved files + and directories so that the server has the right to use them. + You can also start the server as root, but this raises + security issues and should be avoided. + + Change location into the data directory and check the + ownership of the data directory and its contents to make sure + the server has access. For example, if the data directory is /usr/local/mysql/var, use this command: shell> ls -la /usr/local/mysql/var - If the data directory or its files or subdirectories are not owned - by the login account that you use for running the server, change - their ownership to that account. If the account is named mysql, - use these commands: + If the data directory or its files or subdirectories are not + owned by the login account that you use for running the + server, change their ownership to that account. If the + account is named mysql, use these commands: shell> chown -R mysql /usr/local/mysql/var shell> chgrp -R mysql /usr/local/mysql/var - If it possible that even with correct ownership, MySQL may fail to - start up if there is other security software running on your - system that manages application access to various parts of the - file system. In this case, you may need to reconfigure that - software to enable mysqld to access the directories it uses during - normal operation. - - If the server fails to start up correctly, check the error log. - Log files are located in the data directory (typically C:\Program - Files\MySQL\MySQL Server 5.5\data on Windows, - /usr/local/mysql/data for a Unix/Linux binary distribution, and - /usr/local/var for a Unix/Linux source distribution). Look in the - data directory for files with names of the form host_name.err and - host_name.log, where host_name is the name of your server host. - Then examine the last few lines of these files. You can use tail - to display them: + If it possible that even with correct ownership, MySQL may + fail to start up if there is other security software running + on your system that manages application access to various + parts of the file system. In this case, you may need to + reconfigure that software to enable mysqld to access the + directories it uses during normal operation. + + If the server fails to start up correctly, check the error + log. Log files are located in the data directory (typically + C:\Program Files\MySQL\MySQL Server 5.5\data on Windows, + /usr/local/mysql/data for a Unix/Linux binary distribution, + and /usr/local/var for a Unix/Linux source distribution). + Look in the data directory for files with names of the form + host_name.err and host_name.log, where host_name is the name + of your server host. Then examine the last few lines of these + files. You can use tail to display them: shell> tail host_name.err shell> tail host_name.log - The error log should contain information that indicates why the - server could not start. + The error log should contain information that indicates why + the server could not start. - If either of the following errors occur, it means that some other - program (perhaps another mysqld server) is using the TCP/IP port - or Unix socket file that mysqld is trying to use: + If either of the following errors occur, it means that some + other program (perhaps another mysqld server) is using the + TCP/IP port or Unix socket file that mysqld is trying to use: Can't start server: Bind on TCP/IP port: Address already in use Can't start server: Bind on unix socket... Use ps to determine whether you have another mysqld server - running. If so, shut down the server before starting mysqld again. - (If another server is running, and you really want to run multiple - servers, you can find information about how to do so in Section - 5.3, "Running Multiple MySQL Instances on One Machine.") - - If no other server is running, try to execute the command telnet - your_host_name tcp_ip_port_number. (The default MySQL port number - is 3306.) Then press Enter a couple of times. If you do not get an - error message like telnet: Unable to connect to remote host: - Connection refused, some other program is using the TCP/IP port - that mysqld is trying to use. You will need to track down what - program this is and disable it, or else tell mysqld to listen to a - different port with the --port option. In this case, you will also - need to specify the port number for client programs when - connecting to the server using TCP/IP. - - Another reason the port might be inaccessible is that you have a - firewall running that blocks connections to it. If so, modify the - firewall settings to permit access to the port. - - If the server starts but you cannot connect to it, you should make - sure that you have an entry in /etc/hosts that looks like this: + running. If so, shut down the server before starting mysqld + again. (If another server is running, and you really want to + run multiple servers, you can find information about how to + do so in Section 5.3, "Running Multiple MySQL Instances on + One Machine.") + + If no other server is running, try to execute the command + telnet your_host_name tcp_ip_port_number. (The default MySQL + port number is 3306.) Then press Enter a couple of times. If + you do not get an error message like telnet: Unable to + connect to remote host: Connection refused, some other + program is using the TCP/IP port that mysqld is trying to + use. You will need to track down what program this is and + disable it, or else tell mysqld to listen to a different port + with the --port option. In this case, you will also need to + specify the port number for client programs when connecting + to the server using TCP/IP. + + Another reason the port might be inaccessible is that you + have a firewall running that blocks connections to it. If so, + modify the firewall settings to permit access to the port. + + If the server starts but you cannot connect to it, you should + make sure that you have an entry in /etc/hosts that looks + like this: 127.0.0.1 localhost - If you cannot get mysqld to start, you can try to make a trace - file to find the problem by using the --debug option. See Section - 23.4.3, "The DBUG Package." - -2.11.2. Securing the Initial MySQL Accounts - - Part of the MySQL installation process is to set up the mysql - database that contains the grant tables: - - * Windows distributions contain preinitialized grant tables. - - * On Unix, the mysql_install_db program populates the grant - tables. Some installation methods run this program for you. - Others require that you execute it manually. For details, see - Section 2.11.1, "Postinstallation Procedures for Unix-like - Systems." - - The mysql.user grant table defines the initial MySQL user accounts - and their access privileges: - - * Some accounts have the user name root. These are superuser - accounts that have all privileges and can do anything. The - initial root account passwords are empty, so anyone can - connect to the MySQL server as root without a password and be - granted all privileges. - - + On Windows, root accounts are created that permit - connections from the local host only. Connections can be - made by specifying the host name localhost, the IP - address 127.0.0.1, or the IPv6 address ::1. If the user - selects the Enable root access from remote machines - option during installation, the Windows installer creates - another root account that permits connections from any - host. - - + On Unix, each root account permits connections from the - local host. Connections can be made by specifying the - host name localhost, the IP address 127.0.0.1, the IPv6 - address ::1, or the actual host name or IP address. - An attempt to connect to the host 127.0.0.1 normally resolves - to the localhost account. However, this fails if the server is - run with the --skip-name-resolve option, so the 127.0.0.1 - account is useful in that case. The ::1 account is used for - IPv6 connections. - - * Some accounts are for anonymous users. These have an empty - user name. The anonymous accounts have no password, so anyone - can use them to connect to the MySQL server. - - + On Windows, there is one anonymous account that permits - connections from the local host. Connections can be made - by specifying a host name of localhost. - - + On Unix, each anonymous account permits connections from - the local host. Connections can be made by specifying a - host name of localhost for one of the accounts, or the - actual host name or IP address for the other. - - To display which accounts exist in the mysql.user table and check - whether their passwords are empty, use the following statement: -mysql> SELECT User, Host, Password FROM mysql.user; -+------+--------------------+----------+ -| User | Host | Password | -+------+--------------------+----------+ -| root | localhost | | -| root | myhost.example.com | | -| root | 127.0.0.1 | | -| root | ::1 | | -| | localhost | | -| | myhost.example.com | | -+------+--------------------+----------+ - - This output indicates that there are several root and - anonymous-user accounts, none of which have passwords. The output - might differ on your system, but the presence of accounts with - empty passwords means that your MySQL installation is unprotected - until you do something about it: - - * You should assign a password to each MySQL root account. - - * If you want to prevent clients from connecting as anonymous - users without a password, you should either assign a password - to each anonymous account or else remove the accounts. - - In addition, the mysql.db table contains rows that permit all - accounts to access the test database and other databases with - names that start with test_. This is true even for accounts that - otherwise have no special privileges such as the default anonymous - accounts. This is convenient for testing but inadvisable on - production servers. Administrators who want database access - restricted only to accounts that have permissions granted - explicitly for that purpose should remove these mysql.db table - rows. - - The following instructions describe how to set up passwords for - the initial MySQL accounts, first for the root accounts, then for - the anonymous accounts. The instructions also cover how to remove - the anonymous accounts, should you prefer not to permit anonymous - access at all, and describe how to remove permissive access to - test databases. Replace newpwd in the examples with the password - that you want to use. Replace host_name with the name of the - server host. You can determine this name from the output of the - preceding SELECT statement. For the output shown, host_name is - myhost.example.com. - Note - - For additional information about setting passwords, see Section - 6.3.5, "Assigning Account Passwords." If you forget your root - password after setting it, see Section C.5.4.1, "How to Reset the - Root Password." - - You might want to defer setting the passwords until later, to - avoid the need to specify them while you perform additional setup - or testing. However, be sure to set them before using your - installation for production purposes. - - To set up additional accounts, see Section 6.3.2, "Adding User - Accounts." - -Assigning root Account Passwords - - The root account passwords can be set several ways. The following - discussion demonstrates three methods: - - * Use the SET PASSWORD statement - - * Use the UPDATE statement - - * Use the mysqladmin command-line client program - - To assign passwords using SET PASSWORD, connect to the server as - root and issue a SET PASSWORD statement for each root account - listed in the mysql.user table. Be sure to encrypt the password - using the PASSWORD() function. - - For Windows, do this: -shell> mysql -u root -mysql> SET PASSWORD FOR 'root'@'localhost' = PASSWORD('newpwd'); -mysql> SET PASSWORD FOR 'root'@'127.0.0.1' = PASSWORD('newpwd'); -mysql> SET PASSWORD FOR 'root'@'::1' = PASSWORD('newpwd'); -mysql> SET PASSWORD FOR 'root'@'%' = PASSWORD('newpwd'); - - The last statement is unnecessary if the mysql.user table has no - root account with a host value of %. - - For Unix, do this: -shell> mysql -u root -mysql> SET PASSWORD FOR 'root'@'localhost' = PASSWORD('newpwd'); -mysql> SET PASSWORD FOR 'root'@'127.0.0.1' = PASSWORD('newpwd'); -mysql> SET PASSWORD FOR 'root'@'::1' = PASSWORD('newpwd'); -mysql> SET PASSWORD FOR 'root'@'host_name' = PASSWORD('newpwd'); - - You can also use a single statement that assigns a password to all - root accounts by using UPDATE to modify the mysql.user table - directly. This method works on any platform: -shell> mysql -u root -mysql> UPDATE mysql.user SET Password = PASSWORD('newpwd') - -> WHERE User = 'root'; -mysql> FLUSH PRIVILEGES; - - The FLUSH statement causes the server to reread the grant tables. - Without it, the password change remains unnoticed by the server - until you restart it. - - To assign passwords to the root accounts using mysqladmin, execute - the following commands: -shell> mysqladmin -u root password "newpwd" -shell> mysqladmin -u root -h host_name password "newpwd" - - Those commands apply both to Windows and to Unix. The double - quotation marks around the password are not always necessary, but - you should use them if the password contains spaces or other - characters that are special to your command interpreter. - - The mysqladmin method of setting the root account passwords does - not work for the 'root'@'127.0.0.1' or 'root'@'::1' account. Use - the SET PASSWORD method shown earlier. - - After the root passwords have been set, you must supply the - appropriate password whenever you connect as root to the server. - For example, to shut down the server with mysqladmin, use this - command: -shell> mysqladmin -u root -p shutdown -Enter password: (enter root password here) - -Assigning Anonymous Account Passwords - - The mysql commands in the following instructions include a -p - option based on the assumption that you have set the root account - passwords using the preceding instructions and must specify that - password when connecting to the server. - - To assign passwords to the anonymous accounts, connect to the - server as root, then use either SET PASSWORD or UPDATE. Be sure to - encrypt the password using the PASSWORD() function. - - To use SET PASSWORD on Windows, do this: -shell> mysql -u root -p -Enter password: (enter root password here) -mysql> SET PASSWORD FOR ''@'localhost' = PASSWORD('newpwd'); - - To use SET PASSWORD on Unix, do this: -shell> mysql -u root -p -Enter password: (enter root password here) -mysql> SET PASSWORD FOR ''@'localhost' = PASSWORD('newpwd'); -mysql> SET PASSWORD FOR ''@'host_name' = PASSWORD('newpwd'); - - To set the anonymous-user account passwords with a single UPDATE - statement, do this (on any platform): -shell> mysql -u root -p -Enter password: (enter root password here) -mysql> UPDATE mysql.user SET Password = PASSWORD('newpwd') - -> WHERE User = ''; -mysql> FLUSH PRIVILEGES; - - The FLUSH statement causes the server to reread the grant tables. - Without it, the password change remains unnoticed by the server - until you restart it. - -Removing Anonymous Accounts - - If you prefer to remove any anonymous accounts rather than - assigning them passwords, do so as follows on Windows: -shell> mysql -u root -p -Enter password: (enter root password here) -mysql> DROP USER ''@'localhost'; - - On Unix, remove the anonymous accounts like this: -shell> mysql -u root -p -Enter password: (enter root password here) -mysql> DROP USER ''@'localhost'; -mysql> DROP USER ''@'host_name'; - -Securing Test Databases - - By default, the mysql.db table contains rows that permit access by - any user to the test database and other databases with names that - start with test_. (These rows have an empty User column value, - which for access-checking purposes matches any user name.) This - means that such databases can be used even by accounts that - otherwise possess no privileges. If you want to remove any-user - access to test databases, do so as follows: -shell> mysql -u root -p -Enter password: (enter root password here) -mysql> DELETE FROM mysql.db WHERE Db LIKE 'test%'; -mysql> FLUSH PRIVILEGES; - - The FLUSH statement causes the server to reread the grant tables. - Without it, the privilege change remains unnoticed by the server - until you restart it. - - With the preceding change, only users who have global database - privileges or privileges granted explicitly for the test database - can use it. However, if you do not want the database to exist at - all, drop it: -mysql> DROP DATABASE test; + If you cannot get mysqld to start, you can try to make a + trace file to find the problem by using the --debug option. + See Section 24.4.3, "The DBUG Package." + +2.11 Upgrading or Downgrading MySQL + +2.11.1 Upgrading MySQL + + As a general rule, to upgrade from one release series to + another, go to the next series rather than skipping a series. + To upgrade from a release series previous to MySQL 5.1, + upgrade to each successive release series in turn until you + have reached MySQL 5.1, and then proceed with the upgrade to + MySQL 5.5. For example, if you currently are running MySQL + 5.0 and wish to upgrade to a newer series, upgrade to MySQL + 5.1 first before upgrading to 5.5, and so forth. For + information on upgrading to MySQL 5.1, see the MySQL 5.1 + Reference Manual. + + There is a special case for upgrading to MySQL 5.5, which is + that there was a short-lived MySQL 5.4 development series. + This series is no longer being worked on, but to accommodate + users of both series, this section includes one subsection + for users upgrading from MySQL 5.1 to 5.5 and another for + users upgrading from MySQL 5.4 to 5.5. - Note - - On Windows, you can also perform the process described in this - section using the Configuration Wizard (see Section 2.3.6.11, "The - Security Options Dialog"). On all platforms, the MySQL - distribution includes mysql_secure_installation, a command-line - utility that automates much of the process of securing a MySQL - installation. - -2.12. Upgrading or Downgrading MySQL - -2.12.1. Upgrading MySQL - - As a general rule, to upgrade from one release series to another, - go to the next series rather than skipping a series. To upgrade - from a release series previous to MySQL 5.1, upgrade to each - successive release series in turn until you have reached MySQL - 5.1, and then proceed with the upgrade to MySQL 5.5. For example, - if you currently are running MySQL 5.0 and wish to upgrade to a - newer series, upgrade to MySQL 5.1 first before upgrading to 5.5, - and so forth. For information on upgrading to MySQL 5.1, see the - MySQL 5.1 Reference Manual. - - There is a special case for upgrading to MySQL 5.5, which is that - there was a short-lived MySQL 5.4 development series. This series - is no longer being worked on, but to accommodate users of both - series, this section includes one subsection for users upgrading - from MySQL 5.1 to 5.5 and another for users upgrading from MySQL - 5.4 to 5.5. - - To upgrade to MySQL 5.5, use the items in the following checklist - as a guide: + To upgrade to MySQL 5.5, use the items in the following + checklist as a guide: * Before any upgrade, back up your databases, including the - mysql database that contains the grant tables. See Section - 7.2, "Database Backup Methods." + mysql database that contains the grant tables. See + Section 7.2, "Database Backup Methods." - * Read all the notes in Section 2.12.1.1, "Upgrading from MySQL - 5.1 to 5.5," or Section 2.12.1.2, "Upgrading from MySQL 5.4 to - 5.5," depending on whether you currently use MySQL 5.1 or 5.4. - These notes enable you to identify upgrade issues that apply - to your current MySQL installation. Some incompatibilities - discussed in that section require your attention before - upgrading. Others should be dealt with after upgrading. + * Read all the notes in Section 2.11.1.1, "Upgrading from + MySQL 5.1 to 5.5," or Section 2.11.1.2, "Upgrading from + MySQL 5.4 to 5.5," depending on whether you currently use + MySQL 5.1 or 5.4. These notes enable you to identify + upgrade issues that apply to your current MySQL + installation. Some incompatibilities discussed in that + section require your attention before upgrading. Others + should be dealt with after upgrading. * Read the Release Notes - (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/) as well, - which provide information about features that are new in MySQL - 5.5 or differ from those found in earlier MySQL releases. - - * After upgrading to a new version of MySQL, run mysql_upgrade - (see Section 4.4.7, "mysql_upgrade --- Check and Upgrade MySQL - Tables"). This program checks your tables, and attempts to - repair them if necessary. It also updates your grant tables to - make sure that they have the current structure so that you can - take advantage of any new capabilities. (Some releases of - MySQL introduce changes to the structure of the grant tables - to add new privileges or features.) + (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/) as + well, which provide information about features that are + new in MySQL 5.5 or differ from those found in earlier + MySQL releases. + + * After upgrading to a new version of MySQL, run + mysql_upgrade (see Section 4.4.7, "mysql_upgrade --- + Check and Upgrade MySQL Tables"). This program checks + your tables, and attempts to repair them if necessary. It + also updates your grant tables to make sure that they + have the current structure so that you can take advantage + of any new capabilities. (Some releases of MySQL + introduce changes to the structure of the grant tables to + add new privileges or features.) mysql_upgrade does not upgrade the contents of the help tables. For upgrade instructions, see Section 5.1.10, "Server-Side Help." @@ -7543,157 +8290,170 @@ * If you run MySQL Server on Windows, see Section 2.3.9, "Upgrading MySQL on Windows." - * If you use replication, see Section 16.4.3, "Upgrading a + * If you use replication, see Section 17.4.3, "Upgrading a Replication Setup," for information on upgrading your replication setup. - * If you use InnoDB, consider setting innodb_fast_shutdown to 0 - before shutting down and upgrading your server. When you set - innodb_fast_shutdown to 0, InnoDB does a slow shutdown, a full - purge and an insert buffer merge before shutting down, which - ensures that all data files are fully prepared in case the - upgrade process modifies the file format. + * If you use InnoDB, consider setting innodb_fast_shutdown + to 0 before shutting down and upgrading your server. When + you set innodb_fast_shutdown to 0, InnoDB does a slow + shutdown, a full purge and an insert buffer merge before + shutting down, which ensures that all data files are + fully prepared in case the upgrade process modifies the + file format. * If you upgrade an installation originally produced by - installing multiple RPM packages, it is best to upgrade all - the packages, not just some. For example, if you previously - installed the server and client RPMs, do not upgrade just the - server RPM. - - * If you have created a user-defined function (UDF) with a given - name and upgrade MySQL to a version that implements a new - built-in function with the same name, the UDF becomes - inaccessible. To correct this, use DROP FUNCTION to drop the - UDF, and then use CREATE FUNCTION to re-create the UDF with a - different nonconflicting name. The same is true if the new - version of MySQL implements a built-in function with the same - name as an existing stored function. See Section 9.2.4, - "Function Name Parsing and Resolution," for the rules - describing how the server interprets references to different - kinds of functions. - - For upgrades between versions of a MySQL release series that has - reached General Availability status, you can move the MySQL format - files and data files between different versions on systems with - the same architecture. For upgrades to a version of a MySQL - release series that is in development status, that is not - necessarily true. Use of development releases is at your own risk. + installing multiple RPM packages, it is best to upgrade + all the packages, not just some. For example, if you + previously installed the server and client RPMs, do not + upgrade just the server RPM. + + * If you have created a user-defined function (UDF) with a + given name and upgrade MySQL to a version that implements + a new built-in function with the same name, the UDF + becomes inaccessible. To correct this, use DROP FUNCTION + to drop the UDF, and then use CREATE FUNCTION to + re-create the UDF with a different nonconflicting name. + The same is true if the new version of MySQL implements a + built-in function with the same name as an existing + stored function. See Section 9.2.4, "Function Name + Parsing and Resolution," for the rules describing how the + server interprets references to different kinds of + functions. + + For upgrades between versions of a MySQL release series that + has reached General Availability status, you can move the + MySQL format files and data files between different versions + on systems with the same architecture. For upgrades to a + version of a MySQL release series that is in development + status, that is not necessarily true. Use of development + releases is at your own risk. If you are cautious about using new versions, you can always - rename your old mysqld before installing a newer one. For example, - if you are using a version of MySQL 5.1 and want to upgrade to - 5.5, rename your current server from mysqld to mysqld-5.1. If your - new mysqld then does something unexpected, you can simply shut it - down and restart with your old mysqld. - - If problems occur, such as that the new mysqld server does not - start or that you cannot connect without a password, verify that - you do not have an old my.cnf file from your previous - installation. You can check this with the --print-defaults option - (for example, mysqld --print-defaults). If this command displays - anything other than the program name, you have an active my.cnf - file that affects server or client operation. - - If, after an upgrade, you experience problems with compiled client - programs, such as Commands out of sync or unexpected core dumps, - you probably have used old header or library files when compiling - your programs. In this case, you should check the date for your - mysql.h file and libmysqlclient.a library to verify that they are - from the new MySQL distribution. If not, recompile your programs - with the new headers and libraries. Recompilation might also be - necessary for programs compiled against the shared client library - if the library major version number has changed (for example from - libmysqlclient.so.15 to libmysqlclient.so.16. - - If your MySQL installation contains a large amount of data that - might take a long time to convert after an in-place upgrade, you - might find it useful to create a "dummy" database instance for - assessing what conversions might be needed and the work involved - to perform them. Make a copy of your MySQL instance that contains - a full copy of the mysql database, plus all other databases - without data. Run your upgrade procedure on this dummy instance to - see what actions might be needed so that you can better evaluate - the work involved when performing actual data conversion on your + rename your old mysqld before installing a newer one. For + example, if you are using a version of MySQL 5.1 and want to + upgrade to 5.5, rename your current server from mysqld to + mysqld-5.1. If your new mysqld then does something + unexpected, you can simply shut it down and restart with your + old mysqld. + + If problems occur, such as that the new mysqld server does + not start or that you cannot connect without a password, + verify that you do not have an old my.cnf file from your + previous installation. You can check this with the + --print-defaults option (for example, mysqld + --print-defaults). If this command displays anything other + than the program name, you have an active my.cnf file that + affects server or client operation. + + If, after an upgrade, you experience problems with compiled + client programs, such as Commands out of sync or unexpected + core dumps, you probably have used old header or library + files when compiling your programs. In this case, you should + check the date for your mysql.h file and libmysqlclient.a + library to verify that they are from the new MySQL + distribution. If not, recompile your programs with the new + headers and libraries. Recompilation might also be necessary + for programs compiled against the shared client library if + the library major version number has changed (for example + from libmysqlclient.so.15 to libmysqlclient.so.16. + + If your MySQL installation contains a large amount of data + that might take a long time to convert after an in-place + upgrade, you might find it useful to create a "dummy" + database instance for assessing what conversions might be + needed and the work involved to perform them. Make a copy of + your MySQL instance that contains a full copy of the mysql + database, plus all other databases without data. Run your + upgrade procedure on this dummy instance to see what actions + might be needed so that you can better evaluate the work + involved when performing actual data conversion on your original database instance. - It is a good idea to rebuild and reinstall the Perl DBD::mysql - module whenever you install a new release of MySQL. The same - applies to other MySQL interfaces as well, such as PHP mysql - extensions and the Python MySQLdb module. + It is a good idea to rebuild and reinstall the Perl + DBD::mysql module whenever you install a new release of + MySQL. The same applies to other MySQL interfaces as well, + such as PHP mysql extensions and the Python MySQLdb module. -2.12.1.1. Upgrading from MySQL 5.1 to 5.5 +2.11.1.1 Upgrading from MySQL 5.1 to 5.5 Note - It is good practice to back up your data before installing any new - version of software. Although MySQL works very hard to ensure a - high level of quality, you should protect your data by making a - backup. + It is good practice to back up your data before installing + any new version of software. Although MySQL works very hard + to ensure a high level of quality, you should protect your + data by making a backup. - To upgrade to 5.5 from any previous version, MySQL recommends that - you dump your tables with mysqldump before upgrading and reload - the dump file after upgrading. Use the --all-databases option to - include all databases in the dump. If your databases include - stored programs, use the --routines and --events options as well. + To upgrade to 5.5 from any previous version, MySQL recommends + that you dump your tables with mysqldump before upgrading and + reload the dump file after upgrading. Use the --all-databases + option to include all databases in the dump. If your + databases include stored programs, use the --routines and + --events options as well. - In general, you should do the following when upgrading from MySQL - 5.1 to 5.5: + In general, you should do the following when upgrading from + MySQL 5.1 to 5.5: - * Read all the items in these sections to see whether any of - them might affect your applications: + * Read all the items in these sections to see whether any + of them might affect your applications: - + Section 2.12.1, "Upgrading MySQL," has general update - information. + + Section 2.11.1, "Upgrading MySQL," has general + update information. + The items in the change lists provided later in this - section enable you to identify upgrade issues that apply - to your current MySQL installation. Some - incompatibilities discussed there require your attention - before upgrading. Others should be dealt with after - upgrading. + section enable you to identify upgrade issues that + apply to your current MySQL installation. Some + incompatibilities discussed there require your + attention before upgrading. Others should be dealt + with after upgrading. + The MySQL 5.5 Release Notes (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/) - describe significant new features you can use in 5.5 or - that differ from those found in earlier MySQL releases. - Some of these changes may result in incompatibilities. - Note particularly any changes that are marked Known issue or - Incompatible change. These incompatibilities with earlier - versions of MySQL may require your attention before you - upgrade. Our aim is to avoid these changes, but occasionally - they are necessary to correct problems that would be worse - than an incompatibility between releases. If any upgrade issue - applicable to your installation involves an incompatibility - that requires special handling, follow the instructions given - in the incompatibility description. Sometimes this involves - dumping and reloading tables, or use of a statement such as - CHECK TABLE or REPAIR TABLE. - For dump and reload instructions, see Section 2.12.4, - "Rebuilding or Repairing Tables or Indexes." Any procedure - that involves REPAIR TABLE with the USE_FRM option must be - done before upgrading. Use of this statement with a version of - MySQL different from the one used to create the table (that - is, using it after upgrading) may damage the table. See - Section 13.7.2.5, "REPAIR TABLE Syntax." - - * Before upgrading to a new version of MySQL, Section 2.12.3, - "Checking Whether Tables or Indexes Must Be Rebuilt," to see - whether changes to table formats or to character sets or - collations were made between your current version of MySQL and - the version to which you are upgrading. If so and these - changes result in an incompatibility between MySQL versions, - you will need to upgrade the affected tables using the - instructions in Section 2.12.4, "Rebuilding or Repairing - Tables or Indexes." - - * After upgrading to a new version of MySQL, run mysql_upgrade - (see Section 4.4.7, "mysql_upgrade --- Check and Upgrade MySQL - Tables"). This program checks your tables, and attempts to - repair them if necessary. It also updates your grant tables to - make sure that they have the current structure so that you can - take advantage of any new capabilities. (Some releases of - MySQL introduce changes to the structure of the grant tables - to add new privileges or features.) + describe significant new features you can use in 5.5 + or that differ from those found in earlier MySQL + releases. Some of these changes may result in + incompatibilities. + Changes marked as either Known issue or Incompatible + change are incompatibilities with earlier versions of + MySQL, and may require your attention before you upgrade. + Our aim is to avoid these changes, but occasionally they + are necessary to correct problems that would be worse + than an incompatibility between releases. If any upgrade + issue applicable to your installation involves an + incompatibility that requires special handling, follow + the instructions given in the incompatibility + description. Sometimes this involves dumping and + reloading tables, or use of a statement such as CHECK + TABLE or REPAIR TABLE. + For dump and reload instructions, see Section 2.11.4, + "Rebuilding or Repairing Tables or Indexes." Any + procedure that involves REPAIR TABLE with the USE_FRM + option must be done before upgrading. Use of this + statement with a version of MySQL different from the one + used to create the table (that is, using it after + upgrading) may damage the table. See Section 13.7.2.5, + "REPAIR TABLE Syntax." + + * Before upgrading to a new version of MySQL, Section + 2.11.3, "Checking Whether Tables or Indexes Must Be + Rebuilt," to see whether changes to table formats or to + character sets or collations were made between your + current version of MySQL and the version to which you are + upgrading. If so and these changes result in an + incompatibility between MySQL versions, you will need to + upgrade the affected tables using the instructions in + Section 2.11.4, "Rebuilding or Repairing Tables or + Indexes." + + * After upgrading to a new version of MySQL, run + mysql_upgrade (see Section 4.4.7, "mysql_upgrade --- + Check and Upgrade MySQL Tables"). This program checks + your tables, and attempts to repair them if necessary. It + also updates your grant tables to make sure that they + have the current structure so that you can take advantage + of any new capabilities. (Some releases of MySQL + introduce changes to the structure of the grant tables to + add new privileges or features.) mysql_upgrade does not upgrade the contents of the help tables. For upgrade instructions, see Section 5.1.10, "Server-Side Help." @@ -7701,487 +8461,538 @@ * If you run MySQL Server on Windows, see Section 2.3.9, "Upgrading MySQL on Windows." - * If you use replication, see Section 16.4.3, "Upgrading a + * If you use replication, see Section 17.4.3, "Upgrading a Replication Setup," for information on upgrading your replication setup. - If your MySQL installation contains a large amount of data that - might take a long time to convert after an in-place upgrade, you - might find it useful to create a "dummy" database instance for - assessing what conversions might be needed and the work involved - to perform them. Make a copy of your MySQL instance that contains - a full copy of the mysql database, plus all other databases - without data. Run your upgrade procedure on this dummy instance to - see what actions might be needed so that you can better evaluate - the work involved when performing actual data conversion on your + If your MySQL installation contains a large amount of data + that might take a long time to convert after an in-place + upgrade, you might find it useful to create a "dummy" + database instance for assessing what conversions might be + needed and the work involved to perform them. Make a copy of + your MySQL instance that contains a full copy of the mysql + database, plus all other databases without data. Run your + upgrade procedure on this dummy instance to see what actions + might be needed so that you can better evaluate the work + involved when performing actual data conversion on your original database instance. - The following lists describe changes that may affect applications - and that you should watch out for when upgrading from MySQL 5.1 to - 5.5. + The following lists describe changes that may affect + applications and that you should watch out for when upgrading + from MySQL 5.1 to 5.5. Configuration Changes - * Incompatible change: The InnoDB Plugin is included in MySQL - 5.5 releases. It becomes the built-in version of InnoDB in - MySQL Server, replacing the version previously included as the - built-in InnoDB engine. InnoDB Plugin is also available in - MySQL 5.1 as of 5.1.38, but it is an optional storage engine - that must be enabled explicitly using two server options: + * Incompatible change: The InnoDB Plugin is included in + MySQL 5.5 releases. It becomes the built-in version of + InnoDB in MySQL Server, replacing the version previously + included as the built-in InnoDB engine. InnoDB Plugin is + also available in MySQL 5.1 as of 5.1.38, but it is an + optional storage engine that must be enabled explicitly + using two server options: [mysqld] ignore-builtin-innodb plugin-load=innodb=ha_innodb_plugin.so - If you were using InnoDB Plugin in MySQL 5.1 by means of those - options, you must remove them after an upgrade to 5.5 or the - server will fail to start. + + If you were using InnoDB Plugin in MySQL 5.1 by means of + those options, you must remove them after an upgrade to + 5.5 or the server will fail to start. In addition, in InnoDB Plugin, the innodb_file_io_threads system variable has been removed and replaced with - innodb_read_io_threads and innodb_write_io_threads. If you - upgrade from MySQL 5.1 to MySQL 5.5 and previously explicitly - set innodb_file_io_threads at server startup, you must change - your configuration. Either remove any reference to - innodb_file_io_threads or replace it with references to - innodb_read_io_threads and innodb_write_io_threads. + innodb_read_io_threads and innodb_write_io_threads. If + you upgrade from MySQL 5.1 to MySQL 5.5 and previously + explicitly set innodb_file_io_threads at server startup, + you must change your configuration. Either remove any + reference to innodb_file_io_threads or replace it with + references to innodb_read_io_threads and + innodb_write_io_threads. * Incompatible change: In MySQL 5.5, the server includes a - plugin services interface that complements the plugin API. The - services interface enables server functionality to be exposed - as a "service" that plugins can access through a function-call - interface. The libmysqlservices library provides access to the - available services and dynamic plugins now must be linked - against this library (use the -lmysqlservices flag). For an - example showing how to configure for CMake, see Section - 23.2.5, "MySQL Services for Plugins." + plugin services interface that complements the plugin + API. The services interface enables server functionality + to be exposed as a "service" that plugins can access + through a function-call interface. The libmysqlservices + library provides access to the available services and + dynamic plugins now must be linked against this library + (use the -lmysqlservices flag). For an example showing + how to configure for CMake, see Section 24.2.5, "MySQL + Services for Plugins." Server Changes - * Known issue: As of MySQL 5.5.32, for new installations, the - url columns in the mysql database help tables are now created - as type TEXT to accommodate longer URLs. For upgrades, - mysql_upgrade does not update the columns. Modify them - manually using these statements: + * On Linux systems, the libaio library may be needed. + Install it first, if it is not already present on your + system. + + * Known issue: As of MySQL 5.5.32, for new installations, + the url columns in the mysql database help tables are now + created as type TEXT to accommodate longer URLs. For + upgrades, mysql_upgrade does not update the columns. + Modify them manually using these statements: ALTER TABLE mysql.help_category MODIFY url TEXT NOT NULL; ALTER TABLE mysql.help_topic MODIFY url TEXT NOT NULL; - * Incompatible change: As of MySQL 5.5.3, due to work done for - Bug #989, FLUSH TABLES is not permitted when there is an - active LOCK TABLES ... READ. To provide a workaround for this - restriction, FLUSH TABLES has a new variant, FLUSH TABLES - tbl_list WITH READ LOCK, that enables tables to be flushed and - locked in a single operation. As a result of this change, - applications that previously used this statement sequence to - lock and flush tables will fail: + + * Incompatible change: As of MySQL 5.5.3, due to work done + for Bug #989, FLUSH TABLES is not permitted when there is + an active LOCK TABLES ... READ. To provide a workaround + for this restriction, FLUSH TABLES has a new variant, + FLUSH TABLES tbl_list WITH READ LOCK, that enables tables + to be flushed and locked in a single operation. As a + result of this change, applications that previously used + this statement sequence to lock and flush tables will + fail: LOCK TABLES tbl_list READ; FLUSH TABLES tbl_list; + Such applications should now use this statement instead: FLUSH TABLES tbl_list WITH READ LOCK; - * Incompatible change: As of MySQL 5.5.7, the server requires - that a new grant table, proxies_priv, be present in the mysql - database. If you are upgrading to 5.5.7 from a previous MySQL - release rather than performing a new installation, the server - will find that this table is missing and exit during startup - with the following message: + + * Incompatible change: As of MySQL 5.5.7, the server + requires that a new grant table, proxies_priv, be present + in the mysql database. If you are upgrading to 5.5.7 from + a previous MySQL release rather than performing a new + installation, the server will find that this table is + missing and exit during startup with the following + message: Table 'mysql.proxies_priv' doesn't exist - To create the proxies_priv table, start the server with the - --skip-grant-tables option to cause it to skip the normal - grant table checks, then run mysql_upgrade. For example: + + To create the proxies_priv table, start the server with + the --skip-grant-tables option to cause it to skip the + normal grant table checks, then run mysql_upgrade. For + example: shell> mysqld --skip-grant-tables & shell> mysql_upgrade + Then stop the server and restart it normally. - You can specify other options on the mysqld command line if - necessary. Alternatively, if your installation is configured - so that the server normally reads options from an option file, - use the --defaults-file option to specify the file (enter each - command on a single line): + You can specify other options on the mysqld command line + if necessary. Alternatively, if your installation is + configured so that the server normally reads options from + an option file, use the --defaults-file option to specify + the file (enter each command on a single line): shell> mysqld --defaults-file=/usr/local/mysql/etc/my.cnf --skip-grant-tables & shell> mysql_upgrade + With the --skip-grant-tables option, the server does no - password or privilege checking, so any client can connect and - effectively have all privileges. For additional security, use - the --skip-networking option as well to prevent remote clients - from connecting. + password or privilege checking, so any client can connect + and effectively have all privileges. For additional + security, use the --skip-networking option as well to + prevent remote clients from connecting. Note This problem is fixed in MySQL 5.5.8; the server treats a - missing proxies_priv table as equivalent to an empty table. - However, after starting the server, you should still run - mysql_upgrade to create the table. - - * Incompatible change: As of MySQL 5.5.7, InnoDB always uses the - fast truncation technique, equivalent to DROP TABLE and CREATE - TABLE. It no longer performs a row-by-row delete for tables - with parent-child foreign key relationships. TRUNCATE TABLE - returns an error for such tables. Modify your SQL to issue - DELETE FROM table_name for such tables instead. - - * Incompatible change: Prior to MySQL 5.5.7, if you flushed the - logs using FLUSH LOGS or mysqladmin flush-logs and mysqld was - writing the error log to a file (for example, if it was - started with the --log-error option), it renames the current - log file with the suffix -old, then created a new empty log - file. This had the problem that a second log-flushing - operation thus caused the original error log file to be lost - unless you saved it under a different name. For example, you - could use the following commands to save the file: + missing proxies_priv table as equivalent to an empty + table. However, after starting the server, you should + still run mysql_upgrade to create the table. + + * Incompatible change: As of MySQL 5.5.7, InnoDB always + uses the fast truncation technique, equivalent to DROP + TABLE and CREATE TABLE. It no longer performs a + row-by-row delete for tables with parent-child foreign + key relationships. TRUNCATE TABLE returns an error for + such tables. Modify your SQL to issue DELETE FROM + table_name for such tables instead. + + * Incompatible change: Prior to MySQL 5.5.7, if you flushed + the logs using FLUSH LOGS or mysqladmin flush-logs and + mysqld was writing the error log to a file (for example, + if it was started with the --log-error option), it + renames the current log file with the suffix -old, then + created a new empty log file. This had the problem that a + second log-flushing operation thus caused the original + error log file to be lost unless you saved it under a + different name. For example, you could use the following + commands to save the file: shell> mysqladmin flush-logs shell> mv host_name.err-old backup-directory - To avoid the preceding file-loss problem, no renaming occurs - as of MySQL 5.5.7; the server merely closes and reopens the - log file. To rename the file, you can do so manually before - flushing. Then flushing the logs reopens a new file with the - original file name. For example, you can rename the file and - create a new one using the following commands: + + To avoid the preceding file-loss problem, no renaming + occurs as of MySQL 5.5.7; the server merely closes and + reopens the log file. To rename the file, you can do so + manually before flushing. Then flushing the logs reopens + a new file with the original file name. For example, you + can rename the file and create a new one using the + following commands: shell> mv host_name.err host_name.err-old shell> mysqladmin flush-logs shell> mv host_name.err-old backup-directory - * Incompatible change: As of MySQL 5.5.6, handling of CREATE - TABLE IF NOT EXISTS ... SELECT statements has been changed for - the case that the destination table already exists: - - + Previously, for CREATE TABLE IF NOT EXISTS ... SELECT, - MySQL produced a warning that the table exists, but - inserted the rows and wrote the statement to the binary - log anyway. By contrast, CREATE TABLE ... SELECT (without - IF NOT EXISTS) failed with an error, but MySQL inserted - no rows and did not write the statement to the binary - log. - - + MySQL now handles both statements the same way when the - destination table exists, in that neither statement - inserts rows or is written to the binary log. The - difference between them is that MySQL produces a warning - when IF NOT EXISTS is present and an error when it is - not. + + * Incompatible change: As of MySQL 5.5.6, handling of + CREATE TABLE IF NOT EXISTS ... SELECT statements has been + changed for the case that the destination table already + exists: + + + Previously, for CREATE TABLE IF NOT EXISTS ... + SELECT, MySQL produced a warning that the table + exists, but inserted the rows and wrote the + statement to the binary log anyway. By contrast, + CREATE TABLE ... SELECT (without IF NOT EXISTS) + failed with an error, but MySQL inserted no rows and + did not write the statement to the binary log. + + + MySQL now handles both statements the same way when + the destination table exists, in that neither + statement inserts rows or is written to the binary + log. The difference between them is that MySQL + produces a warning when IF NOT EXISTS is present and + an error when it is not. This change in handling of IF NOT EXISTS results in an - incompatibility for statement-based replication from a MySQL - 5.1 master with the original behavior and a MySQL 5.5 slave - with the new behavior. Suppose that CREATE TABLE IF NOT EXISTS - ... SELECT is executed on the master and the destination table - exists. The result is that rows are inserted on the master but - not on the slave. (Row-based replication does not have this - problem.) + incompatibility for statement-based replication from a + MySQL 5.1 master with the original behavior and a MySQL + 5.5 slave with the new behavior. Suppose that CREATE + TABLE IF NOT EXISTS ... SELECT is executed on the master + and the destination table exists. The result is that rows + are inserted on the master but not on the slave. + (Row-based replication does not have this problem.) To address this issue, statement-based binary logging for - CREATE TABLE IF NOT EXISTS ... SELECT is changed in MySQL 5.1 - as of 5.1.51: + CREATE TABLE IF NOT EXISTS ... SELECT is changed in MySQL + 5.1 as of 5.1.51: + If the destination table does not exist, there is no change: The statement is logged as is. - + If the destination table does exist, the statement is - logged as the equivalent pair of CREATE TABLE IF NOT - EXISTS and INSERT ... SELECT statements. (If the SELECT - in the original statement is preceded by IGNORE or - REPLACE, the INSERT becomes INSERT IGNORE or REPLACE, - respectively.) - This change provides forward compatibility for statement-based - replication from MySQL 5.1 to 5.5 because when the destination - table exists, the rows will be inserted on both the master and - slave. To take advantage of this compatibility measure, the - 5.1 server must be at least 5.1.51 and the 5.5 server must be - at least 5.5.6. + + If the destination table does exist, the statement + is logged as the equivalent pair of CREATE TABLE IF + NOT EXISTS and INSERT ... SELECT statements. (If the + SELECT in the original statement is preceded by + IGNORE or REPLACE, the INSERT becomes INSERT IGNORE + or REPLACE, respectively.) + This change provides forward compatibility for + statement-based replication from MySQL 5.1 to 5.5 because + when the destination table exists, the rows will be + inserted on both the master and slave. To take advantage + of this compatibility measure, the 5.1 server must be at + least 5.1.51 and the 5.5 server must be at least 5.5.6. To upgrade an existing 5.1-to-5.5 replication scenario, - upgrade the master first to 5.1.51 or higher. Note that this - differs from the usual replication upgrade advice of upgrading - the slave first. + upgrade the master first to 5.1.51 or higher. Note that + this differs from the usual replication upgrade advice of + upgrading the slave first. A workaround for applications that wish to achieve the original effect (rows inserted regardless of whether the - destination table exists) is to use CREATE TABLE IF NOT EXISTS - and INSERT ... SELECT statements rather than CREATE TABLE IF - NOT EXISTS ... SELECT statements. - Along with the change just described, the following related - change was made: Previously, if an existing view was named as - the destination table for CREATE TABLE IF NOT EXISTS ... - SELECT, rows were inserted into the underlying base table and - the statement was written to the binary log. As of MySQL - 5.1.51 and 5.5.6, nothing is inserted or logged. - - * Incompatible change: Prior to MySQL 5.5.6, if the server was - started with character_set_server set to utf16, it crashed - during full-text stopword initialization. Now the stopword - file is loaded and searched using latin1 if - character_set_server is ucs2, utf16, or utf32. If any table - was created with FULLTEXT indexes while the server character - set was ucs2, utf16, or utf32, it should be repaired using - this statement: + destination table exists) is to use CREATE TABLE IF NOT + EXISTS and INSERT ... SELECT statements rather than + CREATE TABLE IF NOT EXISTS ... SELECT statements. + Along with the change just described, the following + related change was made: Previously, if an existing view + was named as the destination table for CREATE TABLE IF + NOT EXISTS ... SELECT, rows were inserted into the + underlying base table and the statement was written to + the binary log. As of MySQL 5.1.51 and 5.5.6, nothing is + inserted or logged. + + * Incompatible change: Prior to MySQL 5.5.6, if the server + was started with character_set_server set to utf16, it + crashed during full-text stopword initialization. Now the + stopword file is loaded and searched using latin1 if + character_set_server is ucs2, utf16, or utf32. If any + table was created with FULLTEXT indexes while the server + character set was ucs2, utf16, or utf32, it should be + repaired using this statement: REPAIR TABLE tbl_name QUICK; - * Incompatible change: As of MySQL 5.5.5, all numeric operators - and functions on integer, floating-point and DECIMAL values - throw an "out of range" error (ER_DATA_OUT_OF_RANGE) rather - than returning an incorrect value or NULL, when the result is - out of the supported range for the corresponding data type. - See Section 11.2.6, "Out-of-Range and Overflow Handling." - - * Incompatible change: In very old versions of MySQL (prior to - 4.1), the TIMESTAMP data type supported a display width, which - was silently ignored beginning with MySQL 4.1. This is - deprecated in MySQL 5.1, and removed altogether in MySQL 5.5. - These changes in behavior can lead to two problem scenarios - when trying to use TIMESTAMP(N) columns with a MySQL 5.5 or - later server: + + * Incompatible change: As of MySQL 5.5.5, all numeric + operators and functions on integer, floating-point and + DECIMAL values throw an "out of range" error + (ER_DATA_OUT_OF_RANGE) rather than returning an incorrect + value or NULL, when the result is out of the supported + range for the corresponding data type. See Section + 11.2.6, "Out-of-Range and Overflow Handling." + + * Incompatible change: In very old versions of MySQL (prior + to 4.1), the TIMESTAMP data type supported a display + width, which was silently ignored beginning with MySQL + 4.1. This is deprecated in MySQL 5.1, and removed + altogether in MySQL 5.5. These changes in behavior can + lead to two problem scenarios when trying to use + TIMESTAMP(N) columns with a MySQL 5.5 or later server: + When importing a dump file (for example, one created - using mysqldump) created in a MySQL 5.0 or earlier server - into a server from a newer release series, a CREATE TABLE - or ALTER TABLE statement containing TIMESTAMP(N) causes - the import to fail with a syntax error. - To fix this problem, edit the dump file in a text editor - to replace any instances of TIMESTAMP(N) with TIMESTAMP - prior to importing the file. Be sure to use a plain text - editor for this, and not a word processor; otherwise, the - result is almost certain to be unusable for importing - into the MySQL server. - - + When trying replicate any CREATE TABLE or ALTER TABLE - statement containing TIMESTAMP(N) from a master MySQL - server that supports the TIMESTAMP(N) syntax to a MySQL - 5.5.3 or newer slave, the statement causes replication to - fail. Similarly, when you try to restore from a binary - log written by a server that supports TIMESTAMP(N) to a - MySQL 5.5.3 or newer server, any CREATE TABLE or ALTER - TABLE statement containing TIMESTAMP(N) causes the backup + using mysqldump) created in a MySQL 5.0 or earlier + server into a server from a newer release series, a + CREATE TABLE or ALTER TABLE statement containing + TIMESTAMP(N) causes the import to fail with a syntax + error. + To fix this problem, edit the dump file in a text + editor to replace any instances of TIMESTAMP(N) with + TIMESTAMP prior to importing the file. Be sure to + use a plain text editor for this, and not a word + processor; otherwise, the result is almost certain + to be unusable for importing into the MySQL server. + + + When trying replicate any CREATE TABLE or ALTER + TABLE statement containing TIMESTAMP(N) from a + master MySQL server that supports the TIMESTAMP(N) + syntax to a MySQL 5.5.3 or newer slave, the + statement causes replication to fail. Similarly, + when you try to restore from a binary log written by + a server that supports TIMESTAMP(N) to a MySQL 5.5.3 + or newer server, any CREATE TABLE or ALTER TABLE + statement containing TIMESTAMP(N) causes the backup to fail. This holds true regardless of the logging format. - It may be possible to fix such issues using a hex editor, - by replacing any width arguments used with TIMESTAMP, and - the parentheses containing them, with space characters - (hexadecimal 20). Be sure to use a programmer's binary - hex editor and not a regular text editor or word - processor for this; otherwise, the result is almost - certain to be a corrupted binary log file. To guard - against accidental corruption of the binary log, you - should always work on a copy of the file rather than the - original. + It may be possible to fix such issues using a hex + editor, by replacing any width arguments used with + TIMESTAMP, and the parentheses containing them, with + space characters (hexadecimal 20). Be sure to use a + programmer's binary hex editor and not a regular + text editor or word processor for this; otherwise, + the result is almost certain to be a corrupted + binary log file. To guard against accidental + corruption of the binary log, you should always work + on a copy of the file rather than the original. You should try to handle potential issues of these types proactively by updating with ALTER TABLE any TIMESTAMP(N) - columns in your databases so that they use TIMESTAMP instead, - before performing any upgrades. + columns in your databases so that they use TIMESTAMP + instead, before performing any upgrades. * Incompatible change: As of MySQL 5.5.3, the Unicode implementation has been extended to provide support for supplementary characters that lie outside the Basic Multilingual Plane (BMP). Noteworthy features: - + utf16 and utf32 character sets have been added. These - correspond to the UTF-16 and UTF-32 encodings of the - Unicode character set, and they both support + + utf16 and utf32 character sets have been added. + These correspond to the UTF-16 and UTF-32 encodings + of the Unicode character set, and they both support supplementary characters. - + The utf8mb4 character set has been added. This is similar - to utf8, but its encoding allows up to four bytes per - character to enable support for supplementary characters. - - + The ucs2 character set is essentially unchanged except - for the inclusion of some newer BMP characters. - In most respects, upgrading to MySQL 5.5 should present few - problems with regard to Unicode usage, although there are some - potential areas of incompatibility. These are the primary - areas of concern: - - + For the variable-length character data types (VARCHAR and - the TEXT types), the maximum length in characters is less - for utf8mb4 columns than for utf8 columns. - - + For all character data types (CHAR, VARCHAR, and the TEXT - types), the maximum number of characters that can be - indexed is less for utf8mb4 columns than for utf8 + + The utf8mb4 character set has been added. This is + similar to utf8, but its encoding allows up to four + bytes per character to enable support for + supplementary characters. + + + The ucs2 character set is essentially unchanged + except for the inclusion of some newer BMP + characters. + In most respects, upgrading to MySQL 5.5 should present + few problems with regard to Unicode usage, although there + are some potential areas of incompatibility. These are + the primary areas of concern: + + + For the variable-length character data types + (VARCHAR and the TEXT types), the maximum length in + characters is less for utf8mb4 columns than for utf8 columns. + + + For all character data types (CHAR, VARCHAR, and the + TEXT types), the maximum number of characters that + can be indexed is less for utf8mb4 columns than for + utf8 columns. Consequently, if you want to upgrade tables from utf8 to - utf8mb4 to take advantage of supplementary-character support, - it may be necessary to change some column or index - definitions. - For additional details about the new Unicode character sets - and potential incompatibilities, see Section 10.1.10, "Unicode - Support," and Section 10.1.11, "Upgrading from Previous to - Current Unicode Support." - - * Incompatible change: As of MySQL 5.5.3, the server includes - dtoa, a library for conversion between strings and numbers by - David M. Gay. In MySQL, this library provides the basis for - improved conversion between string or DECIMAL values and - approximate-value (FLOAT or DOUBLE) numbers. - Because the conversions produced by this library differ in - some cases from previous results, the potential exists for - incompatibilities in applications that rely on previous - results. For example, applications that depend on a specific - exact result from previous conversions might need adjustment - to accommodate additional precision. + utf8mb4 to take advantage of supplementary-character + support, it may be necessary to change some column or + index definitions. + For additional details about the new Unicode character + sets and potential incompatibilities, see Section + 10.1.10, "Unicode Support," and Section 10.1.11, + "Upgrading from Previous to Current Unicode Support." + + * Incompatible change: As of MySQL 5.5.3, the server + includes dtoa, a library for conversion between strings + and numbers by David M. Gay. In MySQL, this library + provides the basis for improved conversion between string + or DECIMAL values and approximate-value (FLOAT or DOUBLE) + numbers. + Because the conversions produced by this library differ + in some cases from previous results, the potential exists + for incompatibilities in applications that rely on + previous results. For example, applications that depend + on a specific exact result from previous conversions + might need adjustment to accommodate additional + precision. For additional information about the properties of dtoa - conversions, see Section 12.2, "Type Conversion in Expression - Evaluation." + conversions, see Section 12.2, "Type Conversion in + Expression Evaluation." - * Incompatible change: In MySQL 5.5, several changes were made - regarding the language and character set of error messages: - - + The --language option for specifying the directory for - the error message file is now deprecated. The new - lc_messages_dir and lc_messages system variables should - be used instead, and the server treats --language as an - alias for lc_messages_dir. + * Incompatible change: In MySQL 5.5, several changes were + made regarding the language and character set of error + messages: + + + The --language option for specifying the directory + for the error message file is now deprecated. The + new lc_messages_dir and lc_messages system variables + should be used instead, and the server treats + --language as an alias for lc_messages_dir. + The language system variable has been removed and - replaced with the new lc_messages_dir and lc_messages - system variables. lc_messages_dir has only a global value - and is read only. lc_messages has global and session - values and can be modified at runtime, so the error - message language can be changed while the server is - running, and individual clients each can have a different - error message language by changing their session - lc_messages value to a different locale name. - - + Error messages previously were constructed in a mix of - character sets. This issue is resolved by constructing - error messages internally within the server using UTF-8 - and returning them to the client in the character set - specified by the character_set_results system variable. - The content of error messages therefore may in some cases - differ from the messages returned previously. - For more information, see Section 10.2, "Setting the Error - Message Language," and Section 10.1.6, "Character Set for - Error Messages." - - * Incompatible change: MySQL 5.5 implements new functions used - to calculate row placement for tables partitioned by KEY and - LINEAR KEY. Tables that were created using KEY or LINEAR KEY - partitioning in MySQL 5.1 can be upgraded in MySQL 5.5.31 and - later using ALTER TABLE ... PARTITION BY ALGORITHM=2 [LINEAR] - KEY (...). (Bug #14521864, Bug #66462) + replaced with the new lc_messages_dir and + lc_messages system variables. lc_messages_dir has + only a global value and is read only. lc_messages + has global and session values and can be modified at + runtime, so the error message language can be + changed while the server is running, and individual + clients each can have a different error message + language by changing their session lc_messages value + to a different locale name. + + + Error messages previously were constructed in a mix + of character sets. This issue is resolved by + constructing error messages internally within the + server using UTF-8 and returning them to the client + in the character set specified by the + character_set_results system variable. The content + of error messages therefore may in some cases differ + from the messages returned previously. + For more information, see Section 10.2, "Setting the + Error Message Language," and Section 10.1.6, "Character + Set for Error Messages." + + * Incompatible change: MySQL 5.5 implements new functions + used to calculate row placement for tables partitioned by + KEY and LINEAR KEY. Tables that were created using KEY or + LINEAR KEY partitioning in MySQL 5.1 can be upgraded in + MySQL 5.5.31 and later using ALTER TABLE ... PARTITION BY + ALGORITHM=2 [LINEAR] KEY (...). (Bug #14521864, Bug + #66462) SQL Changes - * Incompatible change: Previously, the parser accepted an INTO - clause in nested SELECT statements, which is invalid because - such statements must return their results to the outer - context. As of MySQL 5.5.3, this syntax is no longer permitted - and statements that use it must be changed. - - * Incompatible change: In MySQL 5.5.3, several changes were made - to alias resolution in multiple-table DELETE statements so - that it is no longer possible to have inconsistent or - ambiguous table aliases. + * Incompatible change: Previously, the parser accepted an + INTO clause in nested SELECT statements, which is invalid + because such statements must return their results to the + outer context. As of MySQL 5.5.3, this syntax is no + longer permitted and statements that use it must be + changed. + + * Incompatible change: In MySQL 5.5.3, several changes were + made to alias resolution in multiple-table DELETE + statements so that it is no longer possible to have + inconsistent or ambiguous table aliases. + In MySQL 5.1.23, alias declarations outside the - table_references part of the statement were disallowed - for the USING variant of multiple-table DELETE syntax, to - reduce the possibility of ambiguous aliases that could - lead to ambiguous statements that have unexpected results - such as deleting rows from the wrong table. + table_references part of the statement were + disallowed for the USING variant of multiple-table + DELETE syntax, to reduce the possibility of + ambiguous aliases that could lead to ambiguous + statements that have unexpected results such as + deleting rows from the wrong table. As of MySQL 5.5.3, alias declarations outside - table_references are disallowed for all multiple-table - DELETE statements. Alias declarations are permitted only - in the table_references part. + table_references are disallowed for all + multiple-table DELETE statements. Alias declarations + are permitted only in the table_references part. Incorrect: DELETE FROM t1 AS a2 USING t1 AS a1 INNER JOIN t2 AS a2; DELETE t1 AS a2 FROM t1 AS a1 INNER JOIN t2 AS a2; + Correct: DELETE FROM t1 USING t1 AS a1 INNER JOIN t2 AS a2; DELETE t1 FROM t1 AS a1 INNER JOIN t2 AS a2; - + Previously, for alias references in the list of tables - from which to delete rows in a multiple-table delete, the - default database is used unless one is specified - explicitly. For example, if the default database is db1, - the following statement does not work because the - unqualified alias reference a2 is interpreted as having a - database of db1: + + + Previously, for alias references in the list of + tables from which to delete rows in a multiple-table + delete, the default database is used unless one is + specified explicitly. For example, if the default + database is db1, the following statement does not + work because the unqualified alias reference a2 is + interpreted as having a database of db1: DELETE a1, a2 FROM db1.t1 AS a1 INNER JOIN db2.t2 AS a2 WHERE a1.id=a2.id; + To correctly match an alias that refers to a table - outside the default database, you must explicitly qualify - the reference with the name of the proper database: + outside the default database, you must explicitly + qualify the reference with the name of the proper + database: DELETE a1, db2.a2 FROM db1.t1 AS a1 INNER JOIN db2.t2 AS a2 WHERE a1.id=a2.id; + As of MySQL 5.5.3, alias resolution does not require qualification and alias references should not be - qualified with the database name. Qualified names are - interpreted as referring to tables, not aliases. + qualified with the database name. Qualified names + are interpreted as referring to tables, not aliases. Statements containing alias constructs that are no longer permitted must be rewritten. * Some keywords may be reserved in MySQL 5.5 that were not reserved in MySQL 5.1. See Section 9.3, "Reserved Words." -2.12.1.2. Upgrading from MySQL 5.4 to 5.5 +2.11.1.2 Upgrading from MySQL 5.4 to 5.5 - This section is for the special case of upgrading to MySQL 5.5 - from the short-lived MySQL 5.4 development series, which is no - longer being worked on. + This section is for the special case of upgrading to MySQL + 5.5 from the short-lived MySQL 5.4 development series, which + is no longer being worked on. Note - It is good practice to back up your data before installing any new - version of software. Although MySQL works very hard to ensure a - high level of quality, you should protect your data by making a - backup. + It is good practice to back up your data before installing + any new version of software. Although MySQL works very hard + to ensure a high level of quality, you should protect your + data by making a backup. - To upgrade to 5.5 from any previous version, MySQL recommends that - you dump your tables with mysqldump before upgrading and reload - the dump file after upgrading. Use the --all-databases option to - include all databases in the dump. If your databases include - stored programs, use the --routines and --events options as well. + To upgrade to 5.5 from any previous version, MySQL recommends + that you dump your tables with mysqldump before upgrading and + reload the dump file after upgrading. Use the --all-databases + option to include all databases in the dump. If your + databases include stored programs, use the --routines and + --events options as well. - In general, you should do the following when upgrading from MySQL - 5.4 to 5.5: + In general, you should do the following when upgrading from + MySQL 5.4 to 5.5: - * Read all the items in these sections to see whether any of - them might affect your applications: + * Read all the items in these sections to see whether any + of them might affect your applications: - + Section 2.12.1, "Upgrading MySQL," has general update - information. + + Section 2.11.1, "Upgrading MySQL," has general + update information. + The items in the change lists provided later in this - section enable you to identify upgrade issues that apply - to your current MySQL installation. Some - incompatibilities discussed there require your attention - before upgrading. Others should be dealt with after - upgrading. + section enable you to identify upgrade issues that + apply to your current MySQL installation. Some + incompatibilities discussed there require your + attention before upgrading. Others should be dealt + with after upgrading. + The MySQL 5.5 Release Notes (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/) - describe significant new features you can use in 5.5 or - that differ from those found in earlier MySQL releases. - Some of these changes may result in incompatibilities. - Note particularly any changes that are marked Known issue or - Incompatible change. These incompatibilities with earlier - versions of MySQL may require your attention before you - upgrade. Our aim is to avoid these changes, but occasionally - they are necessary to correct problems that would be worse - than an incompatibility between releases. If any upgrade issue - applicable to your installation involves an incompatibility - that requires special handling, follow the instructions given - in the incompatibility description. Sometimes this involves - dumping and reloading tables, or use of a statement such as - CHECK TABLE or REPAIR TABLE. - For dump and reload instructions, see Section 2.12.4, - "Rebuilding or Repairing Tables or Indexes." Any procedure - that involves REPAIR TABLE with the USE_FRM option must be - done before upgrading. Use of this statement with a version of - MySQL different from the one used to create the table (that - is, using it after upgrading) may damage the table. See - Section 13.7.2.5, "REPAIR TABLE Syntax." - - * Before upgrading to a new version of MySQL, Section 2.12.3, - "Checking Whether Tables or Indexes Must Be Rebuilt," to see - whether changes to table formats or to character sets or - collations were made between your current version of MySQL and - the version to which you are upgrading. If so and these - changes result in an incompatibility between MySQL versions, - you will need to upgrade the affected tables using the - instructions in Section 2.12.4, "Rebuilding or Repairing - Tables or Indexes." - - * After upgrading to a new version of MySQL, run mysql_upgrade - (see Section 4.4.7, "mysql_upgrade --- Check and Upgrade MySQL - Tables"). This program checks your tables, and attempts to - repair them if necessary. It also updates your grant tables to - make sure that they have the current structure so that you can - take advantage of any new capabilities. (Some releases of - MySQL introduce changes to the structure of the grant tables - to add new privileges or features.) + describe significant new features you can use in 5.5 + or that differ from those found in earlier MySQL + releases. Some of these changes may result in + incompatibilities. + Note particularly any changes that are marked Known issue + or Incompatible change. These incompatibilities with + earlier versions of MySQL may require your attention + before you upgrade. Our aim is to avoid these changes, + but occasionally they are necessary to correct problems + that would be worse than an incompatibility between + releases. If any upgrade issue applicable to your + installation involves an incompatibility that requires + special handling, follow the instructions given in the + incompatibility description. Sometimes this involves + dumping and reloading tables, or use of a statement such + as CHECK TABLE or REPAIR TABLE. + For dump and reload instructions, see Section 2.11.4, + "Rebuilding or Repairing Tables or Indexes." Any + procedure that involves REPAIR TABLE with the USE_FRM + option must be done before upgrading. Use of this + statement with a version of MySQL different from the one + used to create the table (that is, using it after + upgrading) may damage the table. See Section 13.7.2.5, + "REPAIR TABLE Syntax." + + * Before upgrading to a new version of MySQL, Section + 2.11.3, "Checking Whether Tables or Indexes Must Be + Rebuilt," to see whether changes to table formats or to + character sets or collations were made between your + current version of MySQL and the version to which you are + upgrading. If so and these changes result in an + incompatibility between MySQL versions, you will need to + upgrade the affected tables using the instructions in + Section 2.11.4, "Rebuilding or Repairing Tables or + Indexes." + + * After upgrading to a new version of MySQL, run + mysql_upgrade (see Section 4.4.7, "mysql_upgrade --- + Check and Upgrade MySQL Tables"). This program checks + your tables, and attempts to repair them if necessary. It + also updates your grant tables to make sure that they + have the current structure so that you can take advantage + of any new capabilities. (Some releases of MySQL + introduce changes to the structure of the grant tables to + add new privileges or features.) mysql_upgrade does not upgrade the contents of the help tables. For upgrade instructions, see Section 5.1.10, "Server-Side Help." @@ -8189,524 +9000,569 @@ * If you run MySQL Server on Windows, see Section 2.3.9, "Upgrading MySQL on Windows." - * If you use replication, see Section 16.4.3, "Upgrading a + * If you use replication, see Section 17.4.3, "Upgrading a Replication Setup," for information on upgrading your replication setup. - If your MySQL installation contains a large amount of data that - might take a long time to convert after an in-place upgrade, you - might find it useful to create a "dummy" database instance for - assessing what conversions might be needed and the work involved - to perform them. Make a copy of your MySQL instance that contains - a full copy of the mysql database, plus all other databases - without data. Run your upgrade procedure on this dummy instance to - see what actions might be needed so that you can better evaluate - the work involved when performing actual data conversion on your + If your MySQL installation contains a large amount of data + that might take a long time to convert after an in-place + upgrade, you might find it useful to create a "dummy" + database instance for assessing what conversions might be + needed and the work involved to perform them. Make a copy of + your MySQL instance that contains a full copy of the mysql + database, plus all other databases without data. Run your + upgrade procedure on this dummy instance to see what actions + might be needed so that you can better evaluate the work + involved when performing actual data conversion on your original database instance. - The following lists describe changes that may affect applications - and that you should watch out for when upgrading from MySQL 5.4 to - 5.5. + The following lists describe changes that may affect + applications and that you should watch out for when upgrading + from MySQL 5.4 to 5.5. Configuration Changes * Incompatible change: In MySQL 5.5, the server includes a - plugin services interface that complements the plugin API. The - services interface enables server functionality to be exposed - as a "service" that plugins can access through a function-call - interface. The libmysqlservices library provides access to the - available services and dynamic plugins now must be linked - against this library (use the -lmysqlservices flag). For an - example showing how to configure for CMake, see Section - 23.2.5, "MySQL Services for Plugins." + plugin services interface that complements the plugin + API. The services interface enables server functionality + to be exposed as a "service" that plugins can access + through a function-call interface. The libmysqlservices + library provides access to the available services and + dynamic plugins now must be linked against this library + (use the -lmysqlservices flag). For an example showing + how to configure for CMake, see Section 24.2.5, "MySQL + Services for Plugins." Server Changes - * Incompatible change: As of MySQL 5.5.7, the server requires - that a new grant table, proxies_priv, be present in the mysql - database. If you are upgrading from a previous MySQL release - rather than performing a new installation, the server will - find that this table is missing and exit during startup with - the following message: + * On Linux systems, the libaio library may be needed. + Install it first, if it is not already present on your + system. + + * Incompatible change: As of MySQL 5.5.7, the server + requires that a new grant table, proxies_priv, be present + in the mysql database. If you are upgrading from a + previous MySQL release rather than performing a new + installation, the server will find that this table is + missing and exit during startup with the following + message: Table 'mysql.proxies_priv' doesn't exist - To create the proxies_priv table, start the server with the - --skip-grant-tables option to cause it to skip the normal - grant table checks, then run mysql_upgrade. For example: + + To create the proxies_priv table, start the server with + the --skip-grant-tables option to cause it to skip the + normal grant table checks, then run mysql_upgrade. For + example: shell> mysqld --skip-grant-tables & shell> mysql_upgrade + Then stop the server and restart it normally. - You can specify other options on the mysqld command line if - necessary. Alternatively, if your installation is configured - so that the server normally reads options from an option file, - use the --defaults-file option to specify the file (enter each - command on a single line): + You can specify other options on the mysqld command line + if necessary. Alternatively, if your installation is + configured so that the server normally reads options from + an option file, use the --defaults-file option to specify + the file (enter each command on a single line): shell> mysqld --defaults-file=/usr/local/mysql/etc/my.cnf --skip-grant-tables & shell> mysql_upgrade + With the --skip-grant-tables option, the server does no - password or privilege checking, so any client can connect and - effectively have all privileges. For additional security, use - the --skip-networking option as well to prevent remote clients - from connecting. + password or privilege checking, so any client can connect + and effectively have all privileges. For additional + security, use the --skip-networking option as well to + prevent remote clients from connecting. * Incompatible change: As of MySQL 5.5.3, the Unicode implementation has been extended to provide support for supplementary characters that lie outside the Basic Multilingual Plane (BMP). Noteworthy features: - + utf16 and utf32 character sets have been added. These - correspond to the UTF-16 and UTF-32 encodings of the - Unicode character set, and they both support + + utf16 and utf32 character sets have been added. + These correspond to the UTF-16 and UTF-32 encodings + of the Unicode character set, and they both support + supplementary characters. + + + The utf8mb4 character set has been added. This is + similar to utf8, but its encoding allows up to four + bytes per character to enable support for supplementary characters. - + The utf8mb4 character set has been added. This is similar - to utf8, but its encoding allows up to four bytes per - character to enable support for supplementary characters. - - + The ucs2 character set is essentially unchanged except - for the inclusion of some newer BMP characters. - In most respects, upgrading to MySQL 5.5 should present few - problems with regard to Unicode usage, although there are some - potential areas of incompatibility. These are the primary - areas of concern: - - + For the variable-length character data types (VARCHAR and - the TEXT types), the maximum length in characters is less - for utf8mb4 columns than for utf8 columns. - - + For all character data types (CHAR, VARCHAR, and the TEXT - types), the maximum number of characters that can be - indexed is less for utf8mb4 columns than for utf8 + + The ucs2 character set is essentially unchanged + except for the inclusion of some newer BMP + characters. + In most respects, upgrading to MySQL 5.5 should present + few problems with regard to Unicode usage, although there + are some potential areas of incompatibility. These are + the primary areas of concern: + + + For the variable-length character data types + (VARCHAR and the TEXT types), the maximum length in + characters is less for utf8mb4 columns than for utf8 columns. + + + For all character data types (CHAR, VARCHAR, and the + TEXT types), the maximum number of characters that + can be indexed is less for utf8mb4 columns than for + utf8 columns. Consequently, if you want to upgrade tables from utf8 to - utf8mb4 to take advantage of supplementary-character support, - it may be necessary to change some column or index - definitions. - For additional details about the new Unicode character sets - and potential incompatibilities, see Section 10.1.10, "Unicode - Support," and Section 10.1.11, "Upgrading from Previous to - Current Unicode Support." - - * Incompatible change: As of MySQL 5.5.3, the server includes - dtoa, a library for conversion between strings and numbers by - David M. Gay. In MySQL, this library provides the basis for - improved conversion between string or DECIMAL values and - approximate-value (FLOAT/DOUBLE) numbers. - Because the conversions produced by this library differ in - some cases from previous results, the potential exists for - incompatibilities in applications that rely on previous - results. For example, applications that depend on a specific - exact result from previous conversions might need adjustment - to accommodate additional precision. + utf8mb4 to take advantage of supplementary-character + support, it may be necessary to change some column or + index definitions. + For additional details about the new Unicode character + sets and potential incompatibilities, see Section + 10.1.10, "Unicode Support," and Section 10.1.11, + "Upgrading from Previous to Current Unicode Support." + + * Incompatible change: As of MySQL 5.5.3, the server + includes dtoa, a library for conversion between strings + and numbers by David M. Gay. In MySQL, this library + provides the basis for improved conversion between string + or DECIMAL values and approximate-value (FLOAT/DOUBLE) + numbers. + Because the conversions produced by this library differ + in some cases from previous results, the potential exists + for incompatibilities in applications that rely on + previous results. For example, applications that depend + on a specific exact result from previous conversions + might need adjustment to accommodate additional + precision. For additional information about the properties of dtoa - conversions, see Section 12.2, "Type Conversion in Expression - Evaluation." - - * Incompatible change: In MySQL 5.5, several changes were made - regarding the language and character set of error messages: + conversions, see Section 12.2, "Type Conversion in + Expression Evaluation." - + The --language option for specifying the directory for - the error message file is now deprecated. The new - lc_messages_dir and lc_messages system variables should - be used instead, and the server treats --language as an - alias for lc_messages_dir. + * Incompatible change: In MySQL 5.5, several changes were + made regarding the language and character set of error + messages: + + + The --language option for specifying the directory + for the error message file is now deprecated. The + new lc_messages_dir and lc_messages system variables + should be used instead, and the server treats + --language as an alias for lc_messages_dir. + The language system variable has been removed and - replaced with the new lc_messages_dir and lc_messages - system variables. lc_messages_dir has only a global value - and is read only. lc_messages has global and session - values and can be modified at runtime, so the error - message language can be changed while the server is - running, and individual clients each can have a different - error message language by changing their session - lc_messages value to a different locale name. - - + Error messages previously were constructed in a mix of - character sets. This issue is resolved by constructing - error messages internally within the server using UTF-8 - and returning them to the client in the character set - specified by the character_set_results system variable. - The content of error messages therefore may in some cases - differ from the messages returned previously. - For more information, see Section 10.2, "Setting the Error - Message Language," and Section 10.1.6, "Character Set for - Error Messages." - - * Before MySQL 5.1.36, plugin options were boolean options (see - Section 4.2.3.2, "Program Option Modifiers"). If you upgrade - to MySQL 5.5 from a version older than 5.1.36 and previously - used options of the form --plugin_name=0 or --plugin_name=1, - the equivalent options are now --plugin_name=OFF and - --plugin_name=ON, respectively. You also have the choice of - requiring plugins to start successfully by using - --plugin_name=FORCE or --plugin_name=FORCE_PLUS_PERMANENT. + replaced with the new lc_messages_dir and + lc_messages system variables. lc_messages_dir has + only a global value and is read only. lc_messages + has global and session values and can be modified at + runtime, so the error message language can be + changed while the server is running, and individual + clients each can have a different error message + language by changing their session lc_messages value + to a different locale name. + + + Error messages previously were constructed in a mix + of character sets. This issue is resolved by + constructing error messages internally within the + server using UTF-8 and returning them to the client + in the character set specified by the + character_set_results system variable. The content + of error messages therefore may in some cases differ + from the messages returned previously. + For more information, see Section 10.2, "Setting the + Error Message Language," and Section 10.1.6, "Character + Set for Error Messages." + + * Before MySQL 5.1.36, plugin options were boolean options + (see Section 4.2.5, "Program Option Modifiers"). If you + upgrade to MySQL 5.5 from a version older than 5.1.36 and + previously used options of the form --plugin_name=0 or + --plugin_name=1, the equivalent options are now + --plugin_name=OFF and --plugin_name=ON, respectively. You + also have the choice of requiring plugins to start + successfully by using --plugin_name=FORCE or + --plugin_name=FORCE_PLUS_PERMANENT. SQL Changes - * Incompatible change: Previously, the parser accepted an INTO - clause in nested SELECT statements, which is invalid because - such statements must return their results to the outer - context. As of MySQL 5.5.3, this syntax is no longer permitted - and statements that use it must be changed. + * Incompatible change: Previously, the parser accepted an + INTO clause in nested SELECT statements, which is invalid + because such statements must return their results to the + outer context. As of MySQL 5.5.3, this syntax is no + longer permitted and statements that use it must be + changed. * Some keywords may be reserved in MySQL 5.5 that were not reserved in MySQL 5.4. See Section 9.3, "Reserved Words." -2.12.2. Downgrading MySQL +2.11.2 Downgrading MySQL - This section describes what you should do to downgrade to an older - MySQL version in the unlikely case that the previous version - worked better than the new one. - - It is always a good idea to make a backup beforehand, in case a - downgrade fails and leaves the instance in an unusable state. - - To downgrade between General Availability (GA) status versions - within the same release series, typically you just install the new - binaries on top of the old ones and do not make any changes to the - databases. - - Downgrades between milestone releases (or from a GA release to a - milestone release) within the same release series are not - supported and you may encounter issues. + This section describes what you should do to downgrade to an + older MySQL version in the unlikely case that the previous + version worked better than the new one. + + It is always a good idea to make a backup beforehand, in case + a downgrade fails and leaves the instance in an unusable + state. + + To downgrade between General Availability (GA) status + versions within the same release series, typically you just + install the new binaries on top of the old ones and do not + make any changes to the databases. + + Downgrades between milestone releases (or from a GA release + to a milestone release) within the same release series are + not supported and you may encounter issues. The following items form a checklist of things you should do whenever you perform a downgrade: - * Read the upgrading section for the release series from which - you are downgrading to be sure that it does not have any - features you really need. See Section 2.12.1, "Upgrading - MySQL." - - * If there is a downgrading section for that version, you should - read that as well. - - * To see which new features were added between the version to - which you are downgrading and your current version, see the - Release Notes + * Read the upgrading section for the release series from + which you are downgrading to be sure that it does not + have any features you really need. See Section 2.11.1, + "Upgrading MySQL." + + * If there is a downgrading section for that version, you + should read that as well. + + * To see which new features were added between the version + to which you are downgrading and your current version, + see the Release Notes (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/). - * Check Section 2.12.3, "Checking Whether Tables or Indexes Must - Be Rebuilt," to see whether changes to table formats or to - character sets or collations were made between your current - version of MySQL and the version to which you are downgrading. - If so and these changes result in an incompatibility between - MySQL versions, you will need to downgrade the affected tables - using the instructions in Section 2.12.4, "Rebuilding or - Repairing Tables or Indexes." - - In most cases, you can move the MySQL format files and data files - between different GA versions on the same architecture as long as - you stay within versions for the same release series of MySQL. - - If you downgrade from one release series to another, there may be - incompatibilities in table storage formats. In this case, use - mysqldump to dump your tables before downgrading. After - downgrading, reload the dump file using mysql or mysqlimport to - re-create your tables. For examples, see Section 2.12.5, "Copying - MySQL Databases to Another Machine." - - A typical symptom of a downward-incompatible table format change - when you downgrade is that you cannot open tables. In that case, - use the following procedure: + * Check Section 2.11.3, "Checking Whether Tables or Indexes + Must Be Rebuilt," to see whether changes to table formats + or to character sets or collations were made between your + current version of MySQL and the version to which you are + downgrading. If so and these changes result in an + incompatibility between MySQL versions, you will need to + downgrade the affected tables using the instructions in + Section 2.11.4, "Rebuilding or Repairing Tables or + Indexes." + + In most cases, you can move the MySQL format files and data + files between different GA versions on the same architecture + as long as you stay within versions for the same release + series of MySQL. + + If you downgrade from one release series to another, there + may be incompatibilities in table storage formats. In this + case, use mysqldump to dump your tables before downgrading. + After downgrading, reload the dump file using mysql or + mysqlimport to re-create your tables. For examples, see + Section 2.11.5, "Copying MySQL Databases to Another Machine." + + A typical symptom of a downward-incompatible table format + change when you downgrade is that you cannot open tables. In + that case, use the following procedure: 1. Stop the older MySQL server that you are downgrading to. 2. Restart the newer MySQL server you are downgrading from. - 3. Dump any tables that were inaccessible to the older server by - using mysqldump to create a dump file. + 3. Dump any tables that were inaccessible to the older + server by using mysqldump to create a dump file. 4. Stop the newer MySQL server and restart the older one. - 5. Reload the dump file into the older server. Your tables should - be accessible. + 5. Reload the dump file into the older server. Your tables + should be accessible. - It might also be the case that system tables in the mysql database - have changed and that downgrading introduces some loss of - functionality or requires some adjustments. Here are some - examples: - - * Trigger creation requires the TRIGGER privilege as of MySQL - 5.1. In MySQL 5.0, there is no TRIGGER privilege and SUPER is - required instead. If you downgrade from MySQL 5.1 to 5.0, you - will need to give the SUPER privilege to those accounts that - had the TRIGGER privilege in 5.1. - - * Triggers were added in MySQL 5.0, so if you downgrade from 5.0 - to 4.1, you cannot use triggers at all. - - * The mysql.proc.comment column definition changed between MySQL - 5.1 and 5.5. After a downgrade from 5.5 to 5.1, this table is - seen as corrupt and in need of repair. To workaround this - problem, execute mysql_upgrade from the version of MySQL to - which you downgraded. - -2.12.2.1. Downgrading to MySQL 5.1 - - When downgrading to MySQL 5.1 from MySQL 5.5, you should keep in - mind the following issues relating to features found in MySQL 5.5, - but not in MySQL 5.1: - - * InnoDB. MySQL 5.5 uses InnoDB Plugin as the built-in version - of InnoDB. MySQL 5.1 includes InnoDB Plugin as of 5.1.38, but - as an option that must be enabled explicitly. See the Release - Notes (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/) for + It might also be the case that system tables in the mysql + database have changed and that downgrading introduces some + loss of functionality or requires some adjustments. Here are + some examples: + + * Trigger creation requires the TRIGGER privilege as of + MySQL 5.1. In MySQL 5.0, there is no TRIGGER privilege + and SUPER is required instead. If you downgrade from + MySQL 5.1 to 5.0, you will need to give the SUPER + privilege to those accounts that had the TRIGGER + privilege in 5.1. + + * Triggers were added in MySQL 5.0, so if you downgrade + from 5.0 to 4.1, you cannot use triggers at all. + + * The mysql.proc.comment column definition changed between + MySQL 5.1 and 5.5. After a downgrade from 5.5 to 5.1, + this table is seen as corrupt and in need of repair. To + workaround this problem, execute mysql_upgrade from the + version of MySQL to which you downgraded. + +2.11.2.1 Downgrading to MySQL 5.1 + + When downgrading to MySQL 5.1 from MySQL 5.5, you should keep + in mind the following issues relating to features found in + MySQL 5.5, but not in MySQL 5.1: + + * InnoDB. MySQL 5.5 uses InnoDB Plugin as the built-in + version of InnoDB. MySQL 5.1 includes InnoDB Plugin as of + 5.1.38, but as an option that must be enabled explicitly. + See the Release Notes + (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/) for MySQL 5.1.38. - * Tables partitioned by [LINEAR] KEY. MySQL 5.5 implements new - functions used to calculate row placement for tables - partitioned by KEY and LINEAR KEY. Tables that were created - using KEY or LINEAR KEY partitioning in MySQL 5.5 cannot be - used by a MySQL 5.1 server. In MySQL 5.5.31 and later, you can - downgrade such tables with ALTER TABLE ... PARTITION BY - ALGORITHM=1 [LINEAR] KEY (...) to make them compatible with - MySQL 5.1. + * Tables partitioned by [LINEAR] KEY. MySQL 5.5 implements + new functions used to calculate row placement for tables + partitioned by KEY and LINEAR KEY. Tables that were + created using KEY or LINEAR KEY partitioning in MySQL 5.5 + cannot be used by a MySQL 5.1 server. In MySQL 5.5.31 and + later, you can downgrade such tables with ALTER TABLE ... + PARTITION BY ALGORITHM=1 [LINEAR] KEY (...) to make them + compatible with MySQL 5.1. -2.12.2.2. Downgrading from MySQL Enterprise Edition to MySQL +2.11.2.2 Downgrading from MySQL Enterprise Edition to MySQL Community Server - This section describes the steps required to downgrade from MySQL - Enterprise Edition to MySQL Community Edition. This can be done at - any time, and is required at the expiration of a MySQL Enterprise - Edition subscription if you wish to continue using MySQL Server. + This section describes the steps required to downgrade from + MySQL Enterprise Edition to MySQL Community Edition. This can + be done at any time, and is required at the expiration of a + MySQL Enterprise Edition subscription if you wish to continue + using MySQL Server. When you perform such a downgrade, all commercially licensed - components of the MySQL Enterprise Edition subscription must be - uninstalled. These components and related considerations are - described in the rest of this section. + components of the MySQL Enterprise Edition subscription must + be uninstalled. These components and related considerations + are described in the rest of this section. Note - The issues described in this section are in addition to any that - may be encountered as a result of any upgrade or downgrade of the - MySQL Server version (such as between MySQL 5.5 and 5.1). - Information about upgrading and downgrading between MySQL release - series can be found elsewhere in this chapter; see Section 2.12.1, - "Upgrading MySQL," and Section 2.12.2, "Downgrading MySQL." + The issues described in this section are in addition to any + that may be encountered as a result of any upgrade or + downgrade of the MySQL Server version (such as between MySQL + 5.5 and 5.1). Information about upgrading and downgrading + between MySQL release series can be found elsewhere in this + chapter; see Section 2.11.1, "Upgrading MySQL," and Section + 2.11.2, "Downgrading MySQL." MySQL Enterprise Database Server. All commercial versions of MySQL Database Server must be uninstalled. - Commercially licensed extensions. All commercially licensed MySQL - Enterprise Database Server extensions must be uninstalled. This - includes the following commercial extensions: + Commercially licensed extensions. All commercially licensed + MySQL Enterprise Database Server extensions must be + uninstalled. This includes the following commercial + extensions: * MySQL External Authentication for Windows: Following - uninstallation of this plugin, existing MySQL user accounts - must be re-created using local authentication. See Section - 6.3, "MySQL User Account Management," for more information. + uninstallation of this plugin, existing MySQL user + accounts must be re-created using local authentication. + See Section 6.3, "MySQL User Account Management," for + more information. * MySQL External Authentication for PAM: Following - uninstallation of this plugin, existing MySQL user accounts - must be re-created using local authentication. See Section - 6.3, "MySQL User Account Management," for more information. + uninstallation of this plugin, existing MySQL user + accounts must be re-created using local authentication. + See Section 6.3, "MySQL User Account Management," for + more information. * MySQL Enterprise Scalability (Thread Pool): Following - uninstallation of this plugin, existing MySQL servers revert - to default thread and connection handling. + uninstallation of this plugin, existing MySQL servers + revert to default thread and connection handling. * MySQL Enterprise Audit: Following uninstallation of this - plugin, no logging of user logins or query activity occurs. + plugin, no logging of user logins or query activity + occurs. * MySQL High Availability: Following uninstallation of this plugin, automated failover is no longer available. MySQL Enterprise Backup. MySQL Enterprise Backup must be - uninstalled. Uninstalling this application has the effects listed - here: + uninstalled. Uninstalling this application has the effects + listed here: * Automated backup scripts no longer work. - * Existing backup images taken with MySQL Enterprise Backup can - no longer be used for recovery. + * Existing backup images taken with MySQL Enterprise Backup + can no longer be used for recovery. * Third-party integration with multimedia systems such as - NetBackup, Tivoli, and Oracle Secure Backup no longer works. + NetBackup, Tivoli, and Oracle Secure Backup no longer + works. - MySQL Enterprise Monitor, MySQL Query Analyzer, agents. MySQL - Enterprise Monitor, MySQL Query Analyzer, and all server-side - agents must be uninstalled. Uninstalling these applications and - agents has the following effects: + MySQL Enterprise Monitor, MySQL Query Analyzer, agents. + MySQL Enterprise Monitor, MySQL Query Analyzer, and all + server-side agents must be uninstalled. Uninstalling these + applications and agents has the following effects: * Automated SNMP and SMTP alerts no longer work. - * All historical MySQL, OS monitoring, query, and performance - metrics as well as all trending data are lost. + * All historical MySQL, OS monitoring, query, and + performance metrics as well as all trending data are + lost. * All environment-specific monitoring templates, custom advisors, graphs and scripts are also lost. -2.12.3. Checking Whether Tables or Indexes Must Be Rebuilt +2.11.3 Checking Whether Tables or Indexes Must Be Rebuilt - A binary upgrade or downgrade is one that installs one version of - MySQL "in place" over an existing version, without dumping and - reloading tables: + A binary upgrade or downgrade is one that installs one + version of MySQL "in place" over an existing version, without + dumping and reloading tables: - 1. Stop the server for the existing version if it is running. + 1. Stop the server for the existing version if it is + running. - 2. Install a different version of MySQL. This is an upgrade if - the new version is higher than the original version, a + 2. Install a different version of MySQL. This is an upgrade + if the new version is higher than the original version, a downgrade if the version is lower. 3. Start the server for the new version. - In many cases, the tables from the previous version of MySQL can - be used without problem by the new version. However, sometimes - changes occur that require tables or table indexes to be rebuilt, - as described in this section. If you have tables that are affected - by any of the issues described here, rebuild the tables or indexes - as necessary using the instructions given in Section 2.12.4, - "Rebuilding or Repairing Tables or Indexes." + In many cases, the tables from the previous version of MySQL + can be used without problem by the new version. However, + sometimes changes occur that require tables or table indexes + to be rebuilt, as described in this section. If you have + tables that are affected by any of the issues described here, + rebuild the tables or indexes as necessary using the + instructions given in Section 2.11.4, "Rebuilding or + Repairing Tables or Indexes." Table Incompatibilities - After a binary upgrade to MySQL 5.1 from a MySQL 5.0 installation - that contains ARCHIVE tables, accessing those tables causes the - server to crash, even if you have run mysql_upgrade or CHECK TABLE - ... FOR UPGRADE. To work around this problem, use mysqldump to - dump all ARCHIVE tables before upgrading, and reload them into - MySQL 5.1 after upgrading. The same problem occurs for binary - downgrades from MySQL 5.1 to 5.0. - - The upgrade problem is fixed in MySQL 5.6.4: The server can open - ARCHIVE tables created in MySQL 5.0. However, it remains the - recommended upgrade procedure to dump 5.0 ARCHIVE tables before - upgrading and reload them after upgrading. + After a binary upgrade to MySQL 5.1 from a MySQL 5.0 + installation that contains ARCHIVE tables, accessing those + tables causes the server to crash, even if you have run + mysql_upgrade or CHECK TABLE ... FOR UPGRADE. To work around + this problem, use mysqldump to dump all ARCHIVE tables before + upgrading, and reload them into MySQL 5.1 after upgrading. + The same problem occurs for binary downgrades from MySQL 5.1 + to 5.0. + + The upgrade problem is fixed in MySQL 5.6.4: The server can + open ARCHIVE tables created in MySQL 5.0. However, it remains + the recommended upgrade procedure to dump 5.0 ARCHIVE tables + before upgrading and reload them after upgrading. Index Incompatibilities In MySQL 5.6.3, the length limit for index prefix keys is - increased from 767 bytes to 3072 bytes, for InnoDB tables using - ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED. See Section 14.3.9.7, - "Limits on InnoDB Tables" for details. This change is also - backported to MySQL 5.5.14. If you downgrade from one of these - releases or higher, to an earlier release with a lower length - limit, the index prefix keys could be truncated at 767 bytes or - the downgrade could fail. This issue could only occur if the - configuration option innodb_large_prefix was enabled on the server - being downgraded. + increased from 767 bytes to 3072 bytes, for InnoDB tables + using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED. See + Section 14.9.7, "Limits on InnoDB Tables" for details. This + change is also backported to MySQL 5.5.14. If you downgrade + from one of these releases or higher, to an earlier release + with a lower length limit, the index prefix keys could be + truncated at 767 bytes or the downgrade could fail. This + issue could only occur if the configuration option + innodb_large_prefix was enabled on the server being + downgraded. If you perform a binary upgrade without dumping and reloading tables, you cannot upgrade directly from MySQL 4.1 to 5.1 or - higher. This occurs due to an incompatible change in the MyISAM - table index format in MySQL 5.0. Upgrade from MySQL 4.1 to 5.0 and - repair all MyISAM tables. Then upgrade from MySQL 5.0 to 5.1 and - check and repair your tables. + higher. This occurs due to an incompatible change in the + MyISAM table index format in MySQL 5.0. Upgrade from MySQL + 4.1 to 5.0 and repair all MyISAM tables. Then upgrade from + MySQL 5.0 to 5.1 and check and repair your tables. Modifications to the handling of character sets or collations - might change the character sort order, which causes the ordering - of entries in any index that uses an affected character set or - collation to be incorrect. Such changes result in several possible - problems: + might change the character sort order, which causes the + ordering of entries in any index that uses an affected + character set or collation to be incorrect. Such changes + result in several possible problems: * Comparison results that differ from previous results - * Inability to find some index values due to misordered index - entries + * Inability to find some index values due to misordered + index entries * Misordered ORDER BY results - * Tables that CHECK TABLE reports as being in need of repair + * Tables that CHECK TABLE reports as being in need of + repair - The solution to these problems is to rebuild any indexes that use - an affected character set or collation, either by dropping and - re-creating the indexes, or by dumping and reloading the entire - table. In some cases, it is possible to alter affected columns to - use a different collation. For information about rebuilding - indexes, see Section 2.12.4, "Rebuilding or Repairing Tables or - Indexes." - - To check whether a table has indexes that must be rebuilt, consult - the following list. It indicates which versions of MySQL - introduced character set or collation changes that require indexes - to be rebuilt. Each entry indicates the version in which the - change occurred and the character sets or collations that the - change affects. If the change is associated with a particular bug - report, the bug number is given. + The solution to these problems is to rebuild any indexes that + use an affected character set or collation, either by + dropping and re-creating the indexes, or by dumping and + reloading the entire table. In some cases, it is possible to + alter affected columns to use a different collation. For + information about rebuilding indexes, see Section 2.11.4, + "Rebuilding or Repairing Tables or Indexes." + + To check whether a table has indexes that must be rebuilt, + consult the following list. It indicates which versions of + MySQL introduced character set or collation changes that + require indexes to be rebuilt. Each entry indicates the + version in which the change occurred and the character sets + or collations that the change affects. If the change is + associated with a particular bug report, the bug number is + given. The list applies both for binary upgrades and downgrades. For - example, Bug #27877 was fixed in MySQL 5.1.24, so it applies to - upgrades from versions older than 5.1.24 to 5.1.24 or newer, and - to downgrades from 5.1.24 or newer to versions older than 5.1.24. - - In many cases, you can use CHECK TABLE ... FOR UPGRADE to identify - tables for which index rebuilding is required. It will report this - message: + example, Bug #27877 was fixed in MySQL 5.1.24, so it applies + to upgrades from versions older than 5.1.24 to 5.1.24 or + newer, and to downgrades from 5.1.24 or newer to versions + older than 5.1.24. + + In many cases, you can use CHECK TABLE ... FOR UPGRADE to + identify tables for which index rebuilding is required. It + will report this message: Table upgrade required. Please do "REPAIR TABLE `tbl_name`" or dump/reload to fix it! - In these cases, you can also use mysqlcheck --check-upgrade or - mysql_upgrade, which execute CHECK TABLE. However, the use of - CHECK TABLE applies only after upgrades, not downgrades. Also, - CHECK TABLE is not applicable to all storage engines. For details - about which storage engines CHECK TABLE supports, see Section - 13.7.2.2, "CHECK TABLE Syntax." + In these cases, you can also use mysqlcheck --check-upgrade + or mysql_upgrade, which execute CHECK TABLE. However, the use + of CHECK TABLE applies only after upgrades, not downgrades. + Also, CHECK TABLE is not applicable to all storage engines. + For details about which storage engines CHECK TABLE supports, + see Section 13.7.2.2, "CHECK TABLE Syntax." These changes cause index rebuilding to be necessary: * MySQL 5.1.24 (Bug #27877) Affects indexes that use the utf8_general_ci or - ucs2_general_ci collation for columns that contain 'ß' LATIN - SMALL LETTER SHARP S (German). The bug fix corrected an error - in the original collations but introduced an incompatibility - such that 'ß' compares equal to characters with which it - previously compared different. - Affected tables can be detected by CHECK TABLE ... FOR UPGRADE - as of MySQL 5.1.30 (see Bug #40053). - A workaround for this issue is implemented as of MySQL 5.1.62, - 5.5.21, and 5.6.5. The workaround involves altering affected - columns to use the utf8_general_mysql500_ci and - ucs2_general_mysql500_ci collations, which preserve the - original pre-5.1.24 ordering of utf8_general_ci and - ucs2_general_ci. + ucs2_general_ci collation for columns that contain 'ß' + LATIN SMALL LETTER SHARP S (German). The bug fix + corrected an error in the original collations but + introduced an incompatibility such that 'ß' compares + equal to characters with which it previously compared + different. + Affected tables can be detected by CHECK TABLE ... FOR + UPGRADE as of MySQL 5.1.30 (see Bug #40053). + A workaround for this issue is implemented as of MySQL + 5.1.62, 5.5.21, and 5.6.5. The workaround involves + altering affected columns to use the + utf8_general_mysql500_ci and ucs2_general_mysql500_ci + collations, which preserve the original pre-5.1.24 + ordering of utf8_general_ci and ucs2_general_ci. * MySQL 5.0.48, 5.1.23 (Bug #27562) - Affects indexes that use the ascii_general_ci collation for - columns that contain any of these characters: '`' GRAVE - ACCENT, '[' LEFT SQUARE BRACKET, '\' REVERSE SOLIDUS, ']' - RIGHT SQUARE BRACKET, '~' TILDE - Affected tables can be detected by CHECK TABLE ... FOR UPGRADE - as of MySQL 5.1.29 (see Bug #39585). + Affects indexes that use the ascii_general_ci collation + for columns that contain any of these characters: '`' + GRAVE ACCENT, '[' LEFT SQUARE BRACKET, '\' REVERSE + SOLIDUS, ']' RIGHT SQUARE BRACKET, '~' TILDE + Affected tables can be detected by CHECK TABLE ... FOR + UPGRADE as of MySQL 5.1.29 (see Bug #39585). * MySQL 5.0.48, 5.1.21 (Bug #29461) - Affects indexes for columns that use any of these character - sets: eucjpms, euc_kr, gb2312, latin7, macce, ujis - Affected tables can be detected by CHECK TABLE ... FOR UPGRADE - as of MySQL 5.1.29 (see Bug #39585). + Affects indexes for columns that use any of these + character sets: eucjpms, euc_kr, gb2312, latin7, macce, + ujis + Affected tables can be detected by CHECK TABLE ... FOR + UPGRADE as of MySQL 5.1.29 (see Bug #39585). -2.12.4. Rebuilding or Repairing Tables or Indexes +2.11.4 Rebuilding or Repairing Tables or Indexes This section describes how to rebuild a table. This can be necessitated by changes to MySQL such as how data types are handled or changes to character set handling. For example, an - error in a collation might have been corrected, necessitating a - table rebuild to update the indexes for character columns that use - the collation. (For examples, see Section 2.12.3, "Checking - Whether Tables or Indexes Must Be Rebuilt.") It might also be that - a table repair or upgrade should be done as indicated by a table - check operation such as that performed by CHECK TABLE, mysqlcheck, - or mysql_upgrade. - - Methods for rebuilding a table include dumping and reloading it, - or using ALTER TABLE or REPAIR TABLE. - Note - - If you are rebuilding tables because a different version of MySQL - will not handle them after a binary (in-place) upgrade or - downgrade, you must use the dump-and-reload method. Dump the - tables before upgrading or downgrading using your original version - of MySQL. Then reload the tables after upgrading or downgrading. - - If you use the dump-and-reload method of rebuilding tables only - for the purpose of rebuilding indexes, you can perform the dump - either before or after upgrading or downgrading. Reloading still - must be done afterward. + error in a collation might have been corrected, necessitating + a table rebuild to update the indexes for character columns + that use the collation. (For examples, see Section 2.11.3, + "Checking Whether Tables or Indexes Must Be Rebuilt.") It + might also be that a table repair or upgrade should be done + as indicated by a table check operation such as that + performed by CHECK TABLE, mysqlcheck, or mysql_upgrade. + + Methods for rebuilding a table include dumping and reloading + it, or using ALTER TABLE or REPAIR TABLE. REPAIR TABLE only + applies to MyISAM, ARCHIVE, and CSV tables. + Note + + If you are rebuilding tables because a different version of + MySQL will not handle them after a binary (in-place) upgrade + or downgrade, you must use the dump-and-reload method. Dump + the tables before upgrading or downgrading using your + original version of MySQL. Then reload the tables after + upgrading or downgrading. + + If you use the dump-and-reload method of rebuilding tables + only for the purpose of rebuilding indexes, you can perform + the dump either before or after upgrading or downgrading. + Reloading still must be done afterward. - To rebuild a table by dumping and reloading it, use mysqldump to - create a dump file and mysql to reload the file: + To rebuild a table by dumping and reloading it, use mysqldump + to create a dump file and mysql to reload the file: shell> mysqldump db_name t1 > dump.sql shell> mysql db_name < dump.sql @@ -8715,85 +9571,94 @@ shell> mysqldump db_name > dump.sql shell> mysql db_name < dump.sql - To rebuild all tables in all databases, use the --all-databases - option: + To rebuild all tables in all databases, use the + --all-databases option: shell> mysqldump --all-databases > dump.sql shell> mysql < dump.sql - To rebuild a table with ALTER TABLE, use a "null" alteration; that - is, an ALTER TABLE statement that "changes" the table to use the - storage engine that it already has. For example, if t1 is a MyISAM - table, use this statement: -mysql> ALTER TABLE t1 ENGINE = MyISAM; - - If you are not sure which storage engine to specify in the ALTER - TABLE statement, use SHOW CREATE TABLE to display the table - definition. - - If you must rebuild a table because a table checking operation - indicates that the table is corrupt or needs an upgrade, you can - use REPAIR TABLE if that statement supports the table's storage - engine. For example, to repair a MyISAM table, use this statement: + To rebuild a table with ALTER TABLE, use a "null" alteration; + that is, an ALTER TABLE statement that "changes" the table to + use the storage engine that it already has. For example, if + t1 is an InnoDB table, use this statement: +mysql> ALTER TABLE t1 ENGINE = InnoDB; + + If you are not sure which storage engine to specify in the + ALTER TABLE statement, use SHOW CREATE TABLE to display the + table definition. + + If you need to rebuild an InnoDB table because a CHECK TABLE + operation indicates that a table upgrade is required, use + mysqldump to create a dump file and mysql to reload the file, + as described earlier. If the CHECK TABLE operation indicates + that there is a corruption or causes InnoDB to fail, refer to + Section 14.21.2, "Forcing InnoDB Recovery" for information + about using the innodb_force_recovery option to restart + InnoDB. To understand the type of problem that CHECK TABLE + may be encountering, refer to the InnoDB notes in Section + 13.7.2.2, "CHECK TABLE Syntax." + + For MyISAM, ARCHIVE, or CSV tables, you can use REPAIR TABLE + if the table checking operation indicates that there is a + corruption or that an upgrade is required. For example, to + repair a MyISAM table, use this statement: mysql> REPAIR TABLE t1; - For storage engines such as InnoDB that REPAIR TABLE does not - support, use mysqldump to create a dump file and mysql to reload - the file, as described earlier. - - For specifics about which storage engines REPAIR TABLE supports, - see Section 13.7.2.5, "REPAIR TABLE Syntax." - - mysqlcheck --repair provides command-line access to the REPAIR - TABLE statement. This can be a more convenient means of repairing - tables because you can use the --databases or --all-databases - option to repair all tables in specific databases or all - databases, respectively: + mysqlcheck --repair provides command-line access to the + REPAIR TABLE statement. This can be a more convenient means + of repairing tables because you can use the --databases or + --all-databases option to repair all tables in specific + databases or all databases, respectively: shell> mysqlcheck --repair --databases db_name ... shell> mysqlcheck --repair --all-databases - For incompatibilities introduced in MySQL 5.1.24 by the fix for - Bug #27877 that corrected the utf8_general_ci and ucs2_general_ci - collations, a workaround is implemented as of MySQL 5.1.62, - 5.5.21, and 5.6.5. Upgrade to one of those versions, then convert - each affected table using one of the following methods. In each - case, the workaround altering affected columns to use the - utf8_general_mysql500_ci and ucs2_general_mysql500_ci collations, - which preserve the original pre-5.1.24 ordering of utf8_general_ci - and ucs2_general_ci. + For incompatibilities introduced in MySQL 5.1.24 by the fix + for Bug #27877 that corrected the utf8_general_ci and + ucs2_general_ci collations, a workaround is implemented as of + MySQL 5.1.62, 5.5.21, and 5.6.5. Upgrade to one of those + versions, then convert each affected table using one of the + following methods. In each case, the workaround altering + affected columns to use the utf8_general_mysql500_ci and + ucs2_general_mysql500_ci collations, which preserve the + original pre-5.1.24 ordering of utf8_general_ci and + ucs2_general_ci. * To convert an affected table after a binary upgrade that - leaves the table files in place, alter the table to use the - new collation. Suppose that the table t1 contains one or more - problematic utf8 columns. To convert the table at the table - level, use a statement like this: + leaves the table files in place, alter the table to use + the new collation. Suppose that the table t1 contains one + or more problematic utf8 columns. To convert the table at + the table level, use a statement like this: ALTER TABLE t1 CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_mysql500_ci; + To apply the change on a column-specific basis, use a - statement like this (be sure to repeat the column definition - as originally specified except for the COLLATE clause): + statement like this (be sure to repeat the column + definition as originally specified except for the COLLATE + clause): ALTER TABLE t1 -MODIFY c1 CHAR(N) CHARACTER SET utf8 COLLATE utf8_general_mysql500_ci -; +MODIFY c1 CHAR(N) CHARACTER SET utf8 COLLATE utf8_general_mysql500_ci; + - * To upgrade the table using a dump and reload procedure, dump - the table using mysqldump, modify the CREATE TABLE statement - in the dump file to use the new collation, and reload the - table. + * To upgrade the table using a dump and reload procedure, + dump the table using mysqldump, modify the CREATE TABLE + statement in the dump file to use the new collation, and + reload the table. - After making the appropriate changes, CHECK TABLE should report no - error. + After making the appropriate changes, CHECK TABLE should + report no error. -2.12.5. Copying MySQL Databases to Another Machine +2.11.5 Copying MySQL Databases to Another Machine + + In cases where you need to transfer databases between + different architectures, you can use mysqldump to create a + file containing SQL statements. You can then transfer the + file to the other machine and feed it as input to the mysql + client. + Note You can copy the .frm, .MYI, and .MYD files for MyISAM tables between different architectures that support the same floating-point format. (MySQL takes care of any byte-swapping - issues.) See Section 14.4, "The MyISAM Storage Engine." - - In cases where you need to transfer databases between different - architectures, you can use mysqldump to create a file containing - SQL statements. You can then transfer the file to the other - machine and feed it as input to the mysql client. + issues.) See Section 15.3, "The MyISAM Storage Engine." Use mysqldump --help to see what options are available. @@ -8803,28 +9668,28 @@ shell> mysqladmin -h 'other_hostname' create db_name shell> mysqldump db_name | mysql -h 'other_hostname' db_name - If you want to copy a database from a remote machine over a slow - network, you can use these commands: + If you want to copy a database from a remote machine over a + slow network, you can use these commands: shell> mysqladmin create db_name -shell> mysqldump -h 'other_hostname' --compress db_name | mysql db_na -me +shell> mysqldump -h 'other_hostname' --compress db_name | mysql db_nam +e - You can also store the dump in a file, transfer the file to the - target machine, and then load the file into the database there. - For example, you can dump a database to a compressed file on the - source machine like this: + You can also store the dump in a file, transfer the file to + the target machine, and then load the file into the database + there. For example, you can dump a database to a compressed + file on the source machine like this: shell> mysqldump --quick db_name | gzip > db_name.gz - Transfer the file containing the database contents to the target - machine and run these commands there: + Transfer the file containing the database contents to the + target machine and run these commands there: shell> mysqladmin create db_name shell> gunzip < db_name.gz | mysql db_name You can also use mysqldump and mysqlimport to transfer the - database. For large tables, this is much faster than simply using - mysqldump. In the following commands, DUMPDIR represents the full - path name of the directory you use to store the output from - mysqldump. + database. For large tables, this is much faster than simply + using mysqldump. In the following commands, DUMPDIR + represents the full path name of the directory you use to + store the output from mysqldump. First, create the directory for the output files and dump the database: @@ -8832,48 +9697,46 @@ shell> mysqldump --tab=DUMPDIR db_name Then transfer the files in the DUMPDIR directory to some - corresponding directory on the target machine and load the files - into MySQL there: + corresponding directory on the target machine and load the + files into MySQL there: shell> mysqladmin create db_name # create database -shell> cat DUMPDIR/*.sql | mysql db_name # create tables in databas -e +shell> cat DUMPDIR/*.sql | mysql db_name # create tables in database shell> mysqlimport db_name DUMPDIR/*.txt # load data into tables - Do not forget to copy the mysql database because that is where the - grant tables are stored. You might have to run commands as the - MySQL root user on the new machine until you have the mysql - database in place. - - After you import the mysql database on the new machine, execute - mysqladmin flush-privileges so that the server reloads the grant - table information. - -2.13. Environment Variables - - This section lists all the environment variables that are used - directly or indirectly by MySQL. Most of these can also be found - in other places in this manual. - - Note that any options on the command line take precedence over - values specified in option files and environment variables, and - values in option files take precedence over values in environment - variables. - - In many cases, it is preferable to use an option file instead of - environment variables to modify the behavior of MySQL. See Section - 4.2.3.3, "Using Option Files." + Do not forget to copy the mysql database because that is + where the grant tables are stored. You might have to run + commands as the MySQL root user on the new machine until you + have the mysql database in place. + + After you import the mysql database on the new machine, + execute mysqladmin flush-privileges so that the server + reloads the grant table information. + +2.12 Environment Variables + + This section lists all the environment variables that are + used directly or indirectly by MySQL. Most of these can also + be found in other places in this manual. + + Options on the command line take precedence over values + specified in option files and environment variables, and + values in option files take precedence over values in + environment variables. + + In many cases, it is preferable to use an option file instead + of environment variables to modify the behavior of MySQL. See + Section 4.2.6, "Using Option Files." Variable Description CXX The name of your C++ compiler (for running CMake). CC The name of your C compiler (for running CMake). - CFLAGS Flags for your C compiler (for running CMake). - CXXFLAGS Flags for your C++ compiler (for running CMake). DBI_USER The default user name for Perl DBI. DBI_TRACE Trace options for Perl DBI. HOME The default path for the mysql history file is $HOME/.mysql_history. - LD_RUN_PATH Used to specify the location of libmysqlclient.so. + LD_RUN_PATH Used to specify the location of + libmysqlclient.so. LIBMYSQL_ENABLE_CLEARTEXT_PLUGIN Enable mysql_clear_password - authentication plugin; see Section 6.3.6.6, "The Cleartext + authentication plugin; see Section 6.3.7.5, "The Cleartext Client-Side Authentication Plugin." MYSQL_DEBUG Debug trace options when debugging. MYSQL_GROUP_SUFFIX Option group suffix value (like specifying @@ -8881,214 +9744,223 @@ MYSQL_HISTFILE The path to the mysql history file. If this variable is set, its value overrides the default for $HOME/.mysql_history. - MYSQL_HOME The path to the directory in which the server-specific - my.cnf file resides. - MYSQL_HOST The default host name used by the mysql command-line - client. + MYSQL_HOME The path to the directory in which the + server-specific my.cnf file resides. + MYSQL_HOST The default host name used by the mysql + command-line client. MYSQL_PS1 The command prompt to use in the mysql command-line client. - MYSQL_PWD The default password when connecting to mysqld. Note - that using this is insecure. See Section 6.1.2.1, "End-User - Guidelines for Password Security." + MYSQL_PWD The default password when connecting to mysqld. + Note that using this is insecure. See Section 6.1.2.1, + "End-User Guidelines for Password Security." MYSQL_TCP_PORT The default TCP/IP port number. MYSQL_UNIX_PORT The default Unix socket file name; used for connections to localhost. PATH Used by the shell to find MySQL programs. TMPDIR The directory where temporary files are created. TZ This should be set to your local time zone. See Section - C.5.4.6, "Time Zone Problems." - UMASK The user-file creation mode when creating files. See note - following table. + B.5.4.6, "Time Zone Problems." + UMASK The user-file creation mode when creating files. See + note following table. UMASK_DIR The user-directory creation mode when creating directories. See note following table. - USER The default user name on Windows when connecting to mysqld. - - For information about the mysql history file, see Section 4.5.1.3, - "mysql Logging." + USER The default user name on Windows when connecting to + mysqld. - The UMASK and UMASK_DIR variables, despite their names, are used - as modes, not masks: + For information about the mysql history file, see Section + 4.5.1.3, "mysql Logging." - * If UMASK is set, mysqld uses ($UMASK | 0600) as the mode for - file creation, so that newly created files have a mode in the - range from 0600 to 0666 (all values octal). + The UMASK and UMASK_DIR variables, despite their names, are + used as modes, not masks: - * If UMASK_DIR is set, mysqld uses ($UMASK_DIR | 0700) as the - base mode for directory creation, which then is AND-ed with - ~(~$UMASK & 0666), so that newly created directories have a - mode in the range from 0700 to 0777 (all values octal). The - AND operation may remove read and write permissions from the - directory mode, but not execute permissions. + * If UMASK is set, mysqld uses ($UMASK | 0600) as the mode + for file creation, so that newly created files have a + mode in the range from 0600 to 0666 (all values octal). + + * If UMASK_DIR is set, mysqld uses ($UMASK_DIR | 0700) as + the base mode for directory creation, which then is + AND-ed with ~(~$UMASK & 0666), so that newly created + directories have a mode in the range from 0700 to 0777 + (all values octal). The AND operation may remove read and + write permissions from the directory mode, but not + execute permissions. - MySQL assumes that the value for UMASK or UMASK_DIR is in octal if - it starts with a zero. + MySQL assumes that the value for UMASK or UMASK_DIR is in + octal if it starts with a zero. -2.14. Perl Installation Notes +2.13 Perl Installation Notes The Perl DBI module provides a generic interface for database - access. You can write a DBI script that works with many different - database engines without change. To use DBI, you must install the - DBI module, as well as a DataBase Driver (DBD) module for each - type of database server you want to access. For MySQL, this driver - is the DBD::mysql module. - - Perl, and the DBD::MySQL module for DBI must be installed if you - want to run the MySQL benchmark scripts; see Section 8.12.2, "The - MySQL Benchmark Suite." They are also required for the MySQL - Cluster ndb_size.pl utility; see Section 17.4.23, "ndb_size.pl --- - NDBCLUSTER Size Requirement Estimator." - Note - - Perl support is not included with MySQL distributions. You can - obtain the necessary modules from http://search.cpan.org for Unix, - or by using the ActiveState ppm program on Windows. The following - sections describe how to do this. - - The DBI/DBD interface requires Perl 5.6.0, and 5.6.1 or later is - preferred. DBI does not work if you have an older version of Perl. - You should use DBD::mysql 4.009 or higher. Although earlier - versions are available, they do not support the full functionality - of MySQL 5.5. - -2.14.1. Installing Perl on Unix - - MySQL Perl support requires that you have installed MySQL client - programming support (libraries and header files). Most - installation methods install the necessary files. If you install - MySQL from RPM files on Linux, be sure to install the developer - RPM as well. The client programs are in the client RPM, but client - programming support is in the developer RPM. + access. You can write a DBI script that works with many + different database engines without change. To use DBI, you + must install the DBI module, as well as a DataBase Driver + (DBD) module for each type of database server you want to + access. For MySQL, this driver is the DBD::mysql module. + + Perl, and the DBD::MySQL module for DBI must be installed if + you want to run the MySQL benchmark scripts; see Section + 8.12.2, "The MySQL Benchmark Suite." They are also required + for the MySQL Cluster ndb_size.pl utility; see Section + 18.4.24, "ndb_size.pl --- NDBCLUSTER Size Requirement + Estimator." + Note + + Perl support is not included with MySQL distributions. You + can obtain the necessary modules from http://search.cpan.org + for Unix, or by using the ActiveState ppm program on Windows. + The following sections describe how to do this. + + The DBI/DBD interface requires Perl 5.6.0, and 5.6.1 or later + is preferred. DBI does not work if you have an older version + of Perl. You should use DBD::mysql 4.009 or higher. Although + earlier versions are available, they do not support the full + functionality of MySQL 5.5. + +2.13.1 Installing Perl on Unix + + MySQL Perl support requires that you have installed MySQL + client programming support (libraries and header files). Most + installation methods install the necessary files. If you + install MySQL from RPM files on Linux, be sure to install the + developer RPM as well. The client programs are in the client + RPM, but client programming support is in the developer RPM. + + The files you need for Perl support can be obtained from the + CPAN (Comprehensive Perl Archive Network) at + http://search.cpan.org. - The files you need for Perl support can be obtained from the CPAN - (Comprehensive Perl Archive Network) at http://search.cpan.org. - - The easiest way to install Perl modules on Unix is to use the CPAN - module. For example: + The easiest way to install Perl modules on Unix is to use the + CPAN module. For example: shell> perl -MCPAN -e shell cpan> install DBI cpan> install DBD::mysql - The DBD::mysql installation runs a number of tests. These tests - attempt to connect to the local MySQL server using the default - user name and password. (The default user name is your login name - on Unix, and ODBC on Windows. The default password is "no - password.") If you cannot connect to the server with those values - (for example, if your account has a password), the tests fail. You - can use force install DBD::mysql to ignore the failed tests. - - DBI requires the Data::Dumper module. It may be installed; if not, - you should install it before installing DBI. - - It is also possible to download the module distributions in the - form of compressed tar archives and build the modules manually. - For example, to unpack and build a DBI distribution, use a - procedure such as this: + The DBD::mysql installation runs a number of tests. These + tests attempt to connect to the local MySQL server using the + default user name and password. (The default user name is + your login name on Unix, and ODBC on Windows. The default + password is "no password.") If you cannot connect to the + server with those values (for example, if your account has a + password), the tests fail. You can use force install + DBD::mysql to ignore the failed tests. + + DBI requires the Data::Dumper module. It may be installed; if + not, you should install it before installing DBI. + + It is also possible to download the module distributions in + the form of compressed tar archives and build the modules + manually. For example, to unpack and build a DBI + distribution, use a procedure such as this: 1. Unpack the distribution into the current directory: shell> gunzip < DBI-VERSION.tar.gz | tar xvf - + This command creates a directory named DBI-VERSION. - 2. Change location into the top-level directory of the unpacked - distribution: + 2. Change location into the top-level directory of the + unpacked distribution: shell> cd DBI-VERSION + 3. Build the distribution and compile everything: shell> perl Makefile.PL shell> make shell> make test shell> make install - The make test command is important because it verifies that the - module is working. Note that when you run that command during the - DBD::mysql installation to exercise the interface code, the MySQL - server must be running or the test fails. + The make test command is important because it verifies that + the module is working. Note that when you run that command + during the DBD::mysql installation to exercise the interface + code, the MySQL server must be running or the test fails. It is a good idea to rebuild and reinstall the DBD::mysql - distribution whenever you install a new release of MySQL. This - ensures that the latest versions of the MySQL client libraries are - installed correctly. - - If you do not have access rights to install Perl modules in the - system directory or if you want to install local Perl modules, the - following reference may be useful: - http://servers.digitaldaze.com/extensions/perl/modules.html#module - s - - Look under the heading "Installing New Modules that Require - Locally Installed Modules." + distribution whenever you install a new release of MySQL. + This ensures that the latest versions of the MySQL client + libraries are installed correctly. + + If you do not have access rights to install Perl modules in + the system directory or if you want to install local Perl + modules, the following reference may be useful: + http://learn.perl.org/faq/perlfaq8.html#How-do-I-keep-my-own- + module-library-directory- -2.14.2. Installing ActiveState Perl on Windows +2.13.2 Installing ActiveState Perl on Windows - On Windows, you should do the following to install the MySQL DBD - module with ActiveState Perl: + On Windows, you should do the following to install the MySQL + DBD module with ActiveState Perl: 1. Get ActiveState Perl from - http://www.activestate.com/Products/ActivePerl/ and install - it. + http://www.activestate.com/Products/ActivePerl/ and + install it. 2. Open a console window. - 3. If necessary, set the HTTP_proxy variable. For example, you - might try a setting like this: + 3. If necessary, set the HTTP_proxy variable. For example, + you might try a setting like this: C:\> set HTTP_proxy=my.proxy.com:3128 + 4. Start the PPM program: C:\> C:\perl\bin\ppm.pl + 5. If you have not previously done so, install DBI: ppm> install DBI + 6. If this succeeds, run the following command: ppm> install DBD-mysql - This procedure should work with ActiveState Perl 5.6 or newer. + This procedure should work with ActiveState Perl 5.6 or + newer. - If you cannot get the procedure to work, you should install the - ODBC driver instead and connect to the MySQL server through ODBC: + If you cannot get the procedure to work, you should install + the ODBC driver instead and connect to the MySQL server + through ODBC: use DBI; $dbh= DBI->connect("DBI:ODBC:$dsn",$user,$password) || die "Got error $DBI::errstr when connecting to $dsn\n"; -2.14.3. Problems Using the Perl DBI/DBD Interface +2.13.3 Problems Using the Perl DBI/DBD Interface - If Perl reports that it cannot find the ../mysql/mysql.so module, - the problem is probably that Perl cannot locate the - libmysqlclient.so shared library. You should be able to fix this - problem by one of the following methods: + If Perl reports that it cannot find the ../mysql/mysql.so + module, the problem is probably that Perl cannot locate the + libmysqlclient.so shared library. You should be able to fix + this problem by one of the following methods: * Copy libmysqlclient.so to the directory where your other shared libraries are located (probably /usr/lib or /lib). - * Modify the -L options used to compile DBD::mysql to reflect - the actual location of libmysqlclient.so. - - * On Linux, you can add the path name of the directory where - libmysqlclient.so is located to the /etc/ld.so.conf file. + * Modify the -L options used to compile DBD::mysql to + reflect the actual location of libmysqlclient.so. - * Add the path name of the directory where libmysqlclient.so is - located to the LD_RUN_PATH environment variable. Some systems - use LD_LIBRARY_PATH instead. - - Note that you may also need to modify the -L options if there are - other libraries that the linker fails to find. For example, if the - linker cannot find libc because it is in /lib and the link command - specifies -L/usr/lib, change the -L option to -L/lib or add -L/lib - to the existing link command. - - If you get the following errors from DBD::mysql, you are probably - using gcc (or using an old binary compiled with gcc): + * On Linux, you can add the path name of the directory + where libmysqlclient.so is located to the /etc/ld.so.conf + file. + + * Add the path name of the directory where + libmysqlclient.so is located to the LD_RUN_PATH + environment variable. Some systems use LD_LIBRARY_PATH + instead. + + Note that you may also need to modify the -L options if there + are other libraries that the linker fails to find. For + example, if the linker cannot find libc because it is in /lib + and the link command specifies -L/usr/lib, change the -L + option to -L/lib or add -L/lib to the existing link command. + + If you get the following errors from DBD::mysql, you are + probably using gcc (or using an old binary compiled with + gcc): /usr/bin/perl: can't resolve symbol '__moddi3' /usr/bin/perl: can't resolve symbol '__divdi3' Add -L/usr/lib/gcc-lib/... -lgcc to the link command when the mysql.so library gets built (check the output from make for - mysql.so when you compile the Perl client). The -L option should - specify the path name of the directory where libgcc.a is located - on your system. - - Another cause of this problem may be that Perl and MySQL are not - both compiled with gcc. In this case, you can solve the mismatch - by compiling both with gcc. - - Copyright (c) 1997, 2013, Oracle and/or its affiliates. All rights - reserved. Legal Notices + mysql.so when you compile the Perl client). The -L option + should specify the path name of the directory where libgcc.a + is located on your system. + + Another cause of this problem may be that Perl and MySQL are + not both compiled with gcc. In this case, you can solve the + mismatch by compiling both with gcc. diff -Nru mysql-5.5-5.5.35+dfsg/libmysql/authentication_win/CMakeLists.txt mysql-5.5-5.5.43/libmysql/authentication_win/CMakeLists.txt --- mysql-5.5-5.5.35+dfsg/libmysql/authentication_win/CMakeLists.txt 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/libmysql/authentication_win/CMakeLists.txt 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -# Copyright (c) 2011, Oracle and/or its affiliates. All rights reserved. +# Copyright (c) 2011, 2014, Oracle and/or its affiliates. All rights reserved. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -32,7 +32,6 @@ SOURCE_GROUP(Headers REGULAR_EXPRESSION ".*h$") -INSTALL_DEBUG_SYMBOLS(auth_win_client) IF(MSVC) INSTALL_DEBUG_TARGET(auth_win_client DESTINATION ${INSTALL_LIBDIR}/debug) ENDIF() diff -Nru mysql-5.5-5.5.35+dfsg/libmysql/CMakeLists.txt mysql-5.5-5.5.43/libmysql/CMakeLists.txt --- mysql-5.5-5.5.35+dfsg/libmysql/CMakeLists.txt 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/libmysql/CMakeLists.txt 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -# Copyright (c) 2006, 2012, Oracle and/or its affiliates. All rights reserved. +# Copyright (c) 2006, 2014, Oracle and/or its affiliates. All rights reserved. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -168,12 +168,17 @@ MERGE_LIBRARIES(mysqlclient STATIC ${LIBS} COMPONENT Development) # Visual Studio users need debug static library for debug projects -INSTALL_DEBUG_SYMBOLS(clientlib) IF(MSVC) INSTALL_DEBUG_TARGET(mysqlclient DESTINATION ${INSTALL_LIBDIR}/debug) INSTALL_DEBUG_TARGET(clientlib DESTINATION ${INSTALL_LIBDIR}/debug) ENDIF() +MACRO(GET_TARGET_NAME target out_name) + GET_TARGET_PROPERTY(location ${target} LOCATION) + GET_FILENAME_COMPONENT(name ${location} NAME) + SET(${out_name} ${name}) +ENDMACRO() + IF(UNIX) MACRO(GET_VERSIONED_LIBNAME LIBNAME EXTENSION VERSION OUTNAME) SET(DOT_VERSION ".${VERSION}") @@ -186,11 +191,19 @@ SET(${OUTNAME} ${LIBNAME}${EXTENSION}${DOT_VERSION}) ENDIF() ENDMACRO() - INSTALL_SYMLINK(${CMAKE_STATIC_LIBRARY_PREFIX}mysqlclient_r.a mysqlclient ${INSTALL_LIBDIR} Development) +ENDIF() + +IF(UNIX) + GET_TARGET_NAME(mysqlclient lib_name) + INSTALL_SYMLINK(mysqlclient + ${lib_name} ${CMAKE_STATIC_LIBRARY_PREFIX}mysqlclient_r.a + ${INSTALL_LIBDIR} Development) ENDIF() IF(NOT DISABLE_SHARED) - MERGE_LIBRARIES(libmysql SHARED ${LIBS} EXPORTS ${CLIENT_API_FUNCTIONS} COMPONENT SharedLibraries) + MERGE_LIBRARIES(libmysql SHARED ${LIBS} + EXPORTS ${CLIENT_API_FUNCTIONS} + COMPONENT SharedLibraries) IF(UNIX) # libtool compatability IF(CMAKE_SYSTEM_NAME MATCHES "FreeBSD" OR APPLE) @@ -198,7 +211,8 @@ ELSEIF(CMAKE_SYSTEM_NAME MATCHES "HP-UX") SET(OS_SHARED_LIB_VERSION "${SHARED_LIB_MAJOR_VERSION}.0") ELSE() - SET(OS_SHARED_LIB_VERSION "${SHARED_LIB_MAJOR_VERSION}.0.0") + SET(OS_SHARED_LIB_VERSION + "${SHARED_LIB_MAJOR_VERSION}.${SHARED_LIB_MINOR_VERSION}.0") ENDIF() # Name of shared library is mysqlclient on Unix SET_TARGET_PROPERTIES(libmysql PROPERTIES @@ -224,8 +238,13 @@ "${CMAKE_SHARED_LIBRARY_SUFFIX}" "" linkname) - INSTALL_SYMLINK(${linkname} libmysql ${INSTALL_LIBDIR} SharedLibraries) - SET(OS_SHARED_LIB_SYMLINKS "${SHARED_LIB_MAJOR_VERSION}" "${OS_SHARED_LIB_VERSION}") + GET_TARGET_NAME(libmysql lib_name) + GET_FILENAME_COMPONENT(lib_name_we ${lib_name} NAME_WE) + INSTALL_SYMLINK(libmysql + ${lib_name} ${linkname} + ${INSTALL_LIBDIR} SharedLibraries) + SET(OS_SHARED_LIB_SYMLINKS + "${SHARED_LIB_MAJOR_VERSION}" "${OS_SHARED_LIB_VERSION}") LIST(REMOVE_DUPLICATES OS_SHARED_LIB_SYMLINKS) FOREACH(ver ${OS_SHARED_LIB_SYMLINKS}) GET_VERSIONED_LIBNAME( @@ -233,7 +252,11 @@ "${CMAKE_SHARED_LIBRARY_SUFFIX}" "${ver}" linkname) - INSTALL_SYMLINK(${linkname} libmysql ${INSTALL_LIBDIR} SharedLibraries) + GET_VERSIONED_LIBNAME( + ${lib_name_we} "${CMAKE_SHARED_LIBRARY_SUFFIX}" "${ver}" lib_name_ver) + INSTALL_SYMLINK(libmysql + ${lib_name_ver} ${linkname} + ${INSTALL_LIBDIR} SharedLibraries) ENDFOREACH() ENDIF() ENDIF() diff -Nru mysql-5.5-5.5.35+dfsg/libmysql/conf_to_src.c mysql-5.5-5.5.43/libmysql/conf_to_src.c --- mysql-5.5-5.5.35+dfsg/libmysql/conf_to_src.c 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/libmysql/conf_to_src.c 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -/* Copyright (C) 2000-2004 MySQL AB +/* Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/libmysql/errmsg.c mysql-5.5-5.5.43/libmysql/errmsg.c --- mysql-5.5-5.5.35+dfsg/libmysql/errmsg.c 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/libmysql/errmsg.c 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -/* Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved. +/* Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -105,6 +105,8 @@ void init_client_errs(void) { + compile_time_assert(array_elements(client_errors) == + (CR_ERROR_LAST - CR_ERROR_FIRST + 2)); (void) my_error_register(get_client_errmsgs, CR_ERROR_FIRST, CR_ERROR_LAST); } diff -Nru mysql-5.5-5.5.35+dfsg/libmysql/libmysql.c mysql-5.5-5.5.43/libmysql/libmysql.c --- mysql-5.5-5.5.35+dfsg/libmysql/libmysql.c 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/libmysql/libmysql.c 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -/* Copyright (c) 2000, 2012, Oracle and/or its affiliates. All rights reserved. +/* Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -1316,6 +1316,10 @@ res= net_realloc(net, buf_length + length); if (res) { + if (net->last_errno == ER_OUT_OF_RESOURCES) + net->last_errno= CR_OUT_OF_MEMORY; + else if (net->last_errno == ER_NET_PACKET_TOO_LARGE) + net->last_errno= CR_NET_PACKET_TOO_LARGE; strmov(net->sqlstate, unknown_sqlstate); strmov(net->last_error, ER(net->last_errno)); } diff -Nru mysql-5.5-5.5.35+dfsg/libmysqld/CMakeLists.txt mysql-5.5-5.5.43/libmysqld/CMakeLists.txt --- mysql-5.5-5.5.35+dfsg/libmysqld/CMakeLists.txt 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/libmysqld/CMakeLists.txt 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -# Copyright (c) 2006, 2011, Oracle and/or its affiliates. All rights reserved. +# Copyright (c) 2006, 2014, Oracle and/or its affiliates. All rights reserved. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -93,6 +93,14 @@ ) +# These files have unused result errors, so we skip Werror +CHECK_C_COMPILER_FLAG("-Werror" HAVE_WERROR_FLAG) +IF(HAVE_WERROR_FLAG) + INCLUDE(${MYSQL_CMAKE_SCRIPT_DIR}/compile_flags.cmake) + ADD_COMPILE_FLAGS(../sql/filesort.cc COMPILE_FLAGS "-Wno-error") + ADD_COMPILE_FLAGS(../sql/opt_range.cc COMPILE_FLAGS "-Wno-error") +ENDIF() + ADD_CONVENIENCE_LIBRARY(sql_embedded ${SQL_EMBEDDED_SOURCES}) DTRACE_INSTRUMENT(sql_embedded) ADD_DEPENDENCIES(sql_embedded GenError GenServerSource) @@ -143,3 +151,37 @@ MERGE_LIBRARIES(libmysqld SHARED ${LIBS} EXPORTS ${CLIENT_API_FUNCTIONS} COMPONENT Embedded) ENDIF() + +OPTION(WITH_EMBEDDED_SHARED_LIBRARY + "Generate shared version of embedded library (in addition to the static one)" + OFF) +IF(WITH_EMBEDDED_SHARED_LIBRARY) + MERGE_LIBRARIES(libmysqld SHARED + mysqlserver + EXPORTS ${CLIENT_API_FUNCTIONS} + OUTPUT_NAME "mysqld" + COMPONENT Embedded) + SET_TARGET_PROPERTIES(libmysqld PROPERTIES + VERSION "${SHARED_LIB_MAJOR_VERSION}.${SHARED_LIB_MINOR_VERSION}.0" + SOVERSION "${SHARED_LIB_MAJOR_VERSION}" + ) + + GET_TARGET_PROPERTY(libmysqld_link_flags libmysqld LINK_FLAGS) + IF(NOT libmysqld_link_flag) + SET(libmysqld_link_flags) + ENDIF() + SET(libmysqld_link_flags + "${CMAKE_SHARED_LIBRARY_C_FLAGS} ${libmysqld_link_flags}") + SET_TARGET_PROPERTIES(libmysqld + PROPERTIES LINK_FLAGS "${libmysqld_link_flags}") + + IF(LINK_FLAG_NO_UNDEFINED) + SET(libmysqld_link_flags + "${libmysqld_link_flags} ${LINK_FLAG_NO_UNDEFINED}") + SET_TARGET_PROPERTIES(libmysqld + PROPERTIES LINK_FLAGS "${libmysqld_link_flags}") + ENDIF() + + SET_TARGET_PROPERTIES(libmysqld PROPERTIES CLEAN_DIRECT_OUTPUT 1) + SET_TARGET_PROPERTIES(mysqlserver PROPERTIES CLEAN_DIRECT_OUTPUT 1) +ENDIF() diff -Nru mysql-5.5-5.5.35+dfsg/libmysqld/examples/CMakeLists.txt mysql-5.5-5.5.43/libmysqld/examples/CMakeLists.txt --- mysql-5.5-5.5.35+dfsg/libmysqld/examples/CMakeLists.txt 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/libmysqld/examples/CMakeLists.txt 2015-02-27 08:30:34.000000000 +0000 @@ -33,6 +33,12 @@ ENDIF(UNIX) MYSQL_ADD_EXECUTABLE(mysqltest_embedded ../../client/mysqltest.cc) +# mysqltest has unused result errors, so we skip Werror +CHECK_C_COMPILER_FLAG("-Werror" HAVE_WERROR_FLAG) +IF(HAVE_WERROR_FLAG) + INCLUDE(${MYSQL_CMAKE_SCRIPT_DIR}/compile_flags.cmake) + ADD_COMPILE_FLAGS(../../client/mysqltest.cc COMPILE_FLAGS "-Wno-error") +ENDIF() TARGET_LINK_LIBRARIES(mysqltest_embedded mysqlserver) diff -Nru mysql-5.5-5.5.35+dfsg/libmysqld/examples/test-run mysql-5.5-5.5.43/libmysqld/examples/test-run --- mysql-5.5-5.5.35+dfsg/libmysqld/examples/test-run 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/libmysqld/examples/test-run 2015-02-27 08:30:34.000000000 +0000 @@ -1,6 +1,7 @@ #! /bin/sh # Copyright (C) 2001, 2006 MySQL AB +# Use is subject to license terms # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/libmysqld/lib_sql.cc mysql-5.5-5.5.43/libmysqld/lib_sql.cc --- mysql-5.5-5.5.35+dfsg/libmysqld/lib_sql.cc 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/libmysqld/lib_sql.cc 2015-02-27 08:30:34.000000000 +0000 @@ -2,6 +2,9 @@ * Copyright (c) 2000 * SWsoft company * + * Modifications copyright (c) 2001, 2013. Oracle and/or its affiliates. + * All rights reserved. + * * This material is provided "as is", with absolutely no warranty expressed * or implied. Any use is at your own risk. * @@ -558,7 +561,7 @@ opt_mysql_tmpdir=getenv("TMP"); #endif if (!opt_mysql_tmpdir || !opt_mysql_tmpdir[0]) - opt_mysql_tmpdir=(char*) P_tmpdir; /* purecov: inspected */ + opt_mysql_tmpdir= const_cast(DEFAULT_TMPDIR); /* purecov: inspected*/ init_ssl(); umask(((~my_umask) & 0666)); diff -Nru mysql-5.5-5.5.35+dfsg/man/comp_err.1 mysql-5.5-5.5.43/man/comp_err.1 --- mysql-5.5-5.5.35+dfsg/man/comp_err.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/comp_err.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBcomp_err\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBCOMP_ERR\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBCOMP_ERR\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -124,8 +124,8 @@ Write a debugging log\&. A typical \fIdebug_options\fR string is -\*(Aqd:t:O,\fIfile_name\fR\*(Aq\&. The default is -\*(Aqd:t:O,/tmp/comp_err\&.trace\*(Aq\&. +d:t:O,\fIfile_name\fR\&. The default is +d:t:O,/tmp/comp_err\&.trace\&. .RE .sp .RS 4 @@ -264,7 +264,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/innochecksum.1 mysql-5.5-5.5.43/man/innochecksum.1 --- mysql-5.5-5.5.35+dfsg/man/innochecksum.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/innochecksum.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBinnochecksum\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBINNOCHECKSUM\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBINNOCHECKSUM\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -43,6 +43,8 @@ tablespace file, calculates the checksum for each page, compares the calculated checksum to the stored checksum, and reports mismatches, which indicate damaged pages\&. It was originally developed to speed up verifying the integrity of tablespace files after power outages but can also be used after file copies\&. Because checksum mismatches will cause InnoDB to deliberately shut down a running server, it can be preferable to use this tool rather than waiting for a server in production usage to encounter the damaged pages\&. +\fBinnochecksum\fR +supports files up to 2GB in size\&. .PP \fBinnochecksum\fR cannot be used on tablespace files that the server already has open\&. For such files, you should use @@ -150,7 +152,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/msql2mysql.1 mysql-5.5-5.5.43/man/msql2mysql.1 --- mysql-5.5-5.5.35+dfsg/man/msql2mysql.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/msql2mysql.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmsql2mysql\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMSQL2MYSQL\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMSQL2MYSQL\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -69,7 +69,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/myisamchk.1 mysql-5.5-5.5.43/man/myisamchk.1 --- mysql-5.5-5.5.35+dfsg/man/myisamchk.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/myisamchk.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmyisamchk\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYISAMCHK\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYISAMCHK\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -249,10 +249,8 @@ \fBmyisamchk\fR supports the following options, which can be specified on the command line or in the [myisamchk] -group of an option file\&. -\fBmyisamchk\fR -also supports the options for processing option files described at -Section\ \&4.2.3.4, \(lqCommand-Line Options that Affect Option-File Handling\(rq\&. +group of an option file\&. For information about option files used by MySQL programs, see +Section\ \&4.2.6, \(lqUsing Option Files\(rq\&. .SH "MYISAMCHK GENERAL OPTIONS" .\" options: myisamchk .\" myisamchk: options @@ -308,8 +306,100 @@ Write a debugging log\&. A typical \fIdebug_options\fR string is -\*(Aqd:t:o,\fIfile_name\fR\*(Aq\&. The default is -\*(Aqd:t:o,/tmp/myisamchk\&.trace\*(Aq\&. +d:t:o,\fIfile_name\fR\&. The default is +d:t:o,/tmp/myisamchk\&.trace\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" myisamchk: defaults-extra-file option +.\" defaults-extra-file option: myisamchk +\fB\-\-defaults\-extra\-file=\fR\fB\fIfile_name\fR\fR +.sp +Read this option file after the global option file but (on Unix) before the user option file\&. If the file does not exist or is otherwise inaccessible, an error occurs\&. Before MySQL 5\&.5\&.8, +\fIfile_name\fR +must be the full path name to the file\&. As of MySQL 5\&.5\&.8, the name is interpreted relative to the current directory if given as a relative path name\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" myisamchk: defaults-file option +.\" defaults-file option: myisamchk +\fB\-\-defaults\-file=\fR\fB\fIfile_name\fR\fR +.sp +Use only the given option file\&. If the file does not exist or is otherwise inaccessible, an error occurs\&. Before MySQL 5\&.5\&.8, +\fIfile_name\fR +must be the full path name to the file\&. As of MySQL 5\&.5\&.8, the name is interpreted relative to the current directory if given as a relative path name\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" myisamchk: defaults-group-suffix option +.\" defaults-group-suffix option: myisamchk +\fB\-\-defaults\-group\-suffix=\fR\fB\fIstr\fR\fR +.sp +Read not only the usual option groups, but also groups with the usual names and a suffix of +\fIstr\fR\&. For example, +\fBmyisamchk\fR +normally reads the +[myisamchk] +group\&. If the +\fB\-\-defaults\-group\-suffix=_other\fR +option is given, +\fBmyisamchk\fR +also reads the +[myisamchk_other] +group\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" myisamchk: no-defaults option +.\" no-defaults option: myisamchk +\fB\-\-no\-defaults\fR +.sp +Do not read any option files\&. If program startup fails due to reading unknown options from an option file, +\fB\-\-no\-defaults\fR +can be used to prevent them from being read\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" myisamchk: print-defaults option +.\" print-defaults option: myisamchk +\fB\-\-print\-defaults\fR +.sp +Print the program name and all options that it gets from option files\&. .RE .sp .RS 4 @@ -2490,7 +2580,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/myisam_ftdump.1 mysql-5.5-5.5.43/man/myisam_ftdump.1 --- mysql-5.5-5.5.35+dfsg/man/myisam_ftdump.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/myisam_ftdump.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmyisam_ftdump\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYISAM_FTDUMP\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYISAM_FTDUMP\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -251,7 +251,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/myisamlog.1 mysql-5.5-5.5.43/man/myisamlog.1 --- mysql-5.5-5.5.35+dfsg/man/myisamlog.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/myisamlog.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmyisamlog\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYISAMLOG\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYISAMLOG\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -228,7 +228,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/myisampack.1 mysql-5.5-5.5.43/man/myisampack.1 --- mysql-5.5-5.5.35+dfsg/man/myisampack.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/myisampack.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmyisampack\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYISAMPACK\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYISAMPACK\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -83,6 +83,18 @@ .\} After packing a table, it becomes read only\&. This is generally intended (such as when accessing packed tables on a CD)\&. .RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fBmyisampack\fR +does not support partitioned tables\&. +.RE .PP Invoke \fBmyisampack\fR @@ -110,7 +122,7 @@ .PP \fBmyisampack\fR supports the following options\&. It also reads option files and supports the options for processing them described at -Section\ \&4.2.3.4, \(lqCommand-Line Options that Affect Option-File Handling\(rq\&. +Section\ \&4.2.7, \(lqCommand-Line Options that Affect Option-File Handling\(rq\&. .sp .RS 4 .ie n \{\ @@ -177,8 +189,8 @@ Write a debugging log\&. A typical \fIdebug_options\fR string is -\*(Aqd:t:o,\fIfile_name\fR\*(Aq\&. The default is -\*(Aqd:t:o\*(Aq\&. +d:t:o,\fIfile_name\fR\&. The default is +d:t:o\&. .RE .sp .RS 4 @@ -841,7 +853,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/my_print_defaults.1 mysql-5.5-5.5.43/man/my_print_defaults.1 --- mysql-5.5-5.5.35+dfsg/man/my_print_defaults.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/my_print_defaults.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmy_print_defaults\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMY_PRINT_DEFAULTS" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMY_PRINT_DEFAULTS" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -115,8 +115,8 @@ Write a debugging log\&. A typical \fIdebug_options\fR string is -\*(Aqd:t:o,\fIfile_name\fR\*(Aq\&. The default is -\*(Aqd:t:o,/tmp/my_print_defaults\&.trace\*(Aq\&. +d:t:o,\fIfile_name\fR\&. The default is +d:t:o,/tmp/my_print_defaults\&.trace\&. .RE .sp .RS 4 @@ -204,7 +204,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysql.1 mysql-5.5-5.5.43/man/mysql.1 --- mysql-5.5-5.5.35+dfsg/man/mysql.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysql.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysql\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQL\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQL\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -121,10 +121,8 @@ [mysql] and [client] -groups of an option file\&. -\fBmysql\fR -also supports the options for processing option files described at -Section\ \&4.2.3.4, \(lqCommand-Line Options that Affect Option-File Handling\(rq\&. +groups of an option file\&. For information about option files used by MySQL programs, see +Section\ \&4.2.6, \(lqUsing Option Files\(rq\&. .sp .RS 4 .ie n \{\ @@ -160,11 +158,32 @@ \fBmysql\fR to start faster, but you must issue the rehash -command if you want to use name completion\&. +command or its +\e# +shortcut if you want to use name completion\&. .sp To complete a name, enter the first part and press Tab\&. If the name is unambiguous, \fBmysql\fR completes it\&. Otherwise, you can press Tab again to see the possible names that begin with what you have typed so far\&. Completion does not occur if there is no default database\&. +.if n \{\ +.sp +.\} +.RS 4 +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fBNote\fR +.ps -1 +.br +This feature requires a MySQL client that is compiled with the +\fBreadline\fR +library\&. Typically, the +\fBreadline\fR +library is not available on Windows\&. +.sp .5v +.RE .RE .sp .RS 4 @@ -219,7 +238,7 @@ .\" bind-address option: mysql \fB\-\-bind\-address=\fR\fB\fIip_address\fR\fR .sp -On a computer having multiple network interfaces, this option can be used to select which interface is employed when connecting to the MySQL server\&. +On a computer having multiple network interfaces, use this option to select which interface to use for connecting to the MySQL server\&. .sp This option is supported only in the version of the \fBmysql\fR @@ -337,8 +356,8 @@ Write a debugging log\&. A typical \fIdebug_options\fR string is -\*(Aqd:t:o,\fIfile_name\fR\*(Aq\&. The default is -\*(Aqd:t:o,/tmp/mysql\&.trace\*(Aq\&. +d:t:o,\fIfile_name\fR\&. The default is +d:t:o,/tmp/mysql\&.trace\&. .RE .sp .RS 4 @@ -384,7 +403,7 @@ .\" default-auth option: mysql \fB\-\-default\-auth=\fR\fB\fIplugin\fR\fR .sp -The client\-side authentication plugin to use\&. See +A hint about the client\-side authentication plugin to use\&. See Section\ \&6.3.6, \(lqPluggable Authentication\(rq\&. .sp This option was added in MySQL 5\&.5\&.7\&. @@ -408,7 +427,7 @@ .sp A common issue that can occur when the operating system uses utf8 -or another multi\-byte character set is that output from the +or another multibyte character set is that output from the \fBmysql\fR client is formatted incorrectly, due to the fact that the MySQL client uses the latin1 @@ -426,6 +445,70 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysql: defaults-extra-file option +.\" defaults-extra-file option: mysql +\fB\-\-defaults\-extra\-file=\fR\fB\fIfile_name\fR\fR +.sp +Read this option file after the global option file but (on Unix) before the user option file\&. If the file does not exist or is otherwise inaccessible, an error occurs\&. Before MySQL 5\&.5\&.8, +\fIfile_name\fR +must be the full path name to the file\&. As of MySQL 5\&.5\&.8, the name is interpreted relative to the current directory if given as a relative path name\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysql: defaults-file option +.\" defaults-file option: mysql +\fB\-\-defaults\-file=\fR\fB\fIfile_name\fR\fR +.sp +Use only the given option file\&. If the file does not exist or is otherwise inaccessible, an error occurs\&. Before MySQL 5\&.5\&.8, +\fIfile_name\fR +must be the full path name to the file\&. As of MySQL 5\&.5\&.8, the name is interpreted relative to the current directory if given as a relative path name\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysql: defaults-group-suffix option +.\" defaults-group-suffix option: mysql +\fB\-\-defaults\-group\-suffix=\fR\fB\fIstr\fR\fR +.sp +Read not only the usual option groups, but also groups with the usual names and a suffix of +\fIstr\fR\&. For example, +\fBmysql\fR +normally reads the +[client] +and +[mysql] +groups\&. If the +\fB\-\-defaults\-group\-suffix=_other\fR +option is given, +\fBmysql\fR +also reads the +[client_other] +and +[mysql_other] +groups\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysql: delimiter option .\" delimiter option: mysql \fB\-\-delimiter=\fR\fB\fIstr\fR\fR @@ -470,7 +553,7 @@ Enable the mysql_clear_password cleartext authentication plugin\&. (See -Section\ \&6.3.6.6, \(lqThe Cleartext Client-Side Authentication Plugin\(rq\&.) This option was added in MySQL 5\&.5\&.27\&. +Section\ \&6.3.7.5, \(lqThe Cleartext Client-Side Authentication Plugin\(rq\&.) This option was added in MySQL 5\&.5\&.27\&. .RE .sp .RS 4 @@ -488,7 +571,7 @@ .sp Execute the statement and quit\&. The default output format is like that produced with \fB\-\-batch\fR\&. See -Section\ \&4.2.3.1, \(lqUsing Options on the Command Line\(rq, for some examples\&. With this option, +Section\ \&4.2.4, \(lqUsing Options on the Command Line\(rq, for some examples\&. With this option, \fBmysql\fR does not use the history file\&. .RE @@ -656,7 +739,7 @@ \fB\-A\fR .sp This has the same effect as -\fB\-skip\-auto\-rehash\fR\&. See the description for +\fB\-\-skip\-auto\-rehash\fR\&. See the description for \fB\-\-auto\-rehash\fR\&. .RE .sp @@ -684,6 +767,23 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysql: no-defaults option +.\" no-defaults option: mysql +\fB\-\-no\-defaults\fR +.sp +Do not read any option files\&. If program startup fails due to reading unknown options from an option file, +\fB\-\-no\-defaults\fR +can be used to prevent them from being read\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysql: no-named-commands option .\" no-named-commands option: mysql \fB\-\-no\-named\-commands\fR, @@ -954,6 +1054,21 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysql: print-defaults option +.\" print-defaults option: mysql +\fB\-\-print\-defaults\fR +.sp +Print the program name and all options that it gets from option files\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysql: prompt option .\" prompt option: mysql \fB\-\-prompt=\fR\fB\fIformat_str\fR\fR @@ -1132,6 +1247,26 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysql: shared-memory-base-name option +.\" shared-memory-base-name option: mysql +\fB\-\-shared\-memory\-base\-name=\fR\fB\fIname\fR\fR +.sp +On Windows, the shared\-memory name to use, for connections made using shared memory to a local server\&. The default value is +MYSQL\&. The shared\-memory name is case sensitive\&. +.sp +The server must be started with the +\fB\-\-shared\-memory\fR +option to enable shared\-memory connections\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysql: show-warnings option .\" show-warnings option: mysql \fB\-\-show\-warnings\fR @@ -1241,7 +1376,7 @@ Options that begin with \fB\-\-ssl\fR specify whether to connect to the server using SSL and indicate where to find SSL keys and certificates\&. See -Section\ \&6.3.8.4, \(lqSSL Command Options\(rq\&. +Section\ \&6.3.9.4, \(lqSSL Command Options\(rq\&. .RE .sp .RS 4 @@ -1699,8 +1834,8 @@ \(lq;\(rq, instances of that character are sent to the server without interpretation\&. However, the server itself still interprets \(lq;\(rq as a statement delimiter and processes statements accordingly\&. This behavior on the server side comes into play for multiple\-statement execution (see -Section\ \&22.8.17, \(lqC API Support for Multiple Statement Execution\(rq), and for parsing the body of stored procedures and functions, triggers, and events (see -Section\ \&19.1, \(lqDefining Stored Programs\(rq)\&. +Section\ \&23.8.17, \(lqC API Support for Multiple Statement Execution\(rq), and for parsing the body of stored procedures and functions, triggers, and events (see +Section\ \&20.1, \(lqDefining Stored Programs\(rq)\&. .RE .sp .RS 4 @@ -1831,7 +1966,7 @@ nowarning, \ew .sp -Enable display of warnings after each statement\&. +Disable display of warnings after each statement\&. .RE .sp .RS 4 @@ -2512,7 +2647,7 @@ In this example, note that the backslashes are doubled\&. If you set the prompt using the prompt option in an option file, it is advisable to double the backslashes when using the special prompt options\&. There is some overlap in the set of permissible prompt options and the set of special escape sequences that are recognized in option files\&. (The rules for escape sequences in option files are listed in -Section\ \&4.2.3.3, \(lqUsing Option Files\(rq\&.) The overlap may cause you problems if you use single backslashes\&. For example, +Section\ \&4.2.6, \(lqUsing Option Files\(rq\&.) The overlap may cause you problems if you use single backslashes\&. For example, \es is interpreted as a space rather than as the current seconds value\&. The following example shows how to define a prompt within an option file to include the current time in HH:MM:SS> @@ -2575,8 +2710,7 @@ in your home directory\&. To specify a different file, set the value of the MYSQL_HISTFILE environment variable\&. - How Logging Occurs -.PP +How Logging Occurs.PP Statement logging occurs as follows: .sp .RS 4 @@ -2663,8 +2797,7 @@ .RE .\} .sp - Controlling the History File -.PP +Controlling the History File.PP The \&.mysql_history file should be protected with a restrictive access mode because sensitive information might be written to it, such as the text of SQL statements that contain passwords\&. See @@ -2826,7 +2959,7 @@ .RE .\} .PP -The search string can contain the the wildcard characters +The search string can contain the wildcard characters \(lq%\(rq and \(lq_\(rq\&. These have the same meaning as for pattern\-matching operations performed with the @@ -3221,11 +3354,11 @@ option\&. .PP For more information about auto\-reconnect and its effect on state information when a reconnection occurs, see -Section\ \&22.8.16, \(lqControlling Automatic Reconnection Behavior\(rq\&. +Section\ \&23.8.16, \(lqControlling Automatic Reconnection Behavior\(rq\&. .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysqlaccess.1 mysql-5.5-5.5.43/man/mysqlaccess.1 --- mysql-5.5-5.5.35+dfsg/man/mysqlaccess.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysqlaccess.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysqlaccess\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQLACCESS\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQLACCESS\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -432,7 +432,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysqladmin.1 mysql-5.5-5.5.43/man/mysqladmin.1 --- mysql-5.5-5.5.35+dfsg/man/mysqladmin.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysqladmin.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysqladmin\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQLADMIN\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQLADMIN\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -84,7 +84,7 @@ Tell the server to write debug information to the error log\&. Format and content of this information is subject to change\&. .sp This includes information about the Event Scheduler\&. See -Section\ \&19.4.5, \(lqEvent Scheduler Status\(rq\&. +Section\ \&20.4.5, \(lqEvent Scheduler Status\(rq\&. .RE .sp .RS 4 @@ -609,10 +609,8 @@ [mysqladmin] and [client] -groups of an option file\&. -\fBmysqladmin\fR -also supports the options for processing option files described at -Section\ \&4.2.3.4, \(lqCommand-Line Options that Affect Option-File Handling\(rq\&. +groups of an option file\&. For information about option files used by MySQL programs, see +Section\ \&4.2.6, \(lqUsing Option Files\(rq\&. .sp .RS 4 .ie n \{\ @@ -642,7 +640,7 @@ .\" bind-address option: mysqladmin \fB\-\-bind\-address=\fR\fB\fIip_address\fR\fR .sp -On a computer having multiple network interfaces, this option can be used to select which interface is employed when connecting to the MySQL server\&. +On a computer having multiple network interfaces, use this option to select which interface to use for connecting to the MySQL server\&. .sp This option is supported only in the version of \fBmysqladmin\fR @@ -715,8 +713,8 @@ Write a debugging log\&. A typical \fIdebug_options\fR string is -\*(Aqd:t:o,\fIfile_name\fR\*(Aq\&. The default is -\*(Aqd:t:o,/tmp/mysqladmin\&.trace\*(Aq\&. +d:t:o,\fIfile_name\fR\&. The default is +d:t:o,/tmp/mysqladmin\&.trace\&. .RE .sp .RS 4 @@ -761,7 +759,7 @@ .\" default-auth option: mysqladmin \fB\-\-default\-auth=\fR\fB\fIplugin\fR\fR .sp -The client\-side authentication plugin to use\&. See +A hint about the client\-side authentication plugin to use\&. See Section\ \&6.3.6, \(lqPluggable Authentication\(rq\&. .sp This option was added in MySQL 5\&.5\&.9\&. @@ -793,6 +791,70 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqladmin: defaults-extra-file option +.\" defaults-extra-file option: mysqladmin +\fB\-\-defaults\-extra\-file=\fR\fB\fIfile_name\fR\fR +.sp +Read this option file after the global option file but (on Unix) before the user option file\&. If the file does not exist or is otherwise inaccessible, an error occurs\&. Before MySQL 5\&.5\&.8, +\fIfile_name\fR +must be the full path name to the file\&. As of MySQL 5\&.5\&.8, the name is interpreted relative to the current directory if given as a relative path name\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysqladmin: defaults-file option +.\" defaults-file option: mysqladmin +\fB\-\-defaults\-file=\fR\fB\fIfile_name\fR\fR +.sp +Use only the given option file\&. If the file does not exist or is otherwise inaccessible, an error occurs\&. Before MySQL 5\&.5\&.8, +\fIfile_name\fR +must be the full path name to the file\&. As of MySQL 5\&.5\&.8, the name is interpreted relative to the current directory if given as a relative path name\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysqladmin: defaults-group-suffix option +.\" defaults-group-suffix option: mysqladmin +\fB\-\-defaults\-group\-suffix=\fR\fB\fIstr\fR\fR +.sp +Read not only the usual option groups, but also groups with the usual names and a suffix of +\fIstr\fR\&. For example, +\fBmysqladmin\fR +normally reads the +[client] +and +[mysqladmin] +groups\&. If the +\fB\-\-defaults\-group\-suffix=_other\fR +option is given, +\fBmysqladmin\fR +also reads the +[client_other] +and +[mysqladmin_other] +groups\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqladmin: enable-cleartext-plugin option .\" enable-cleartext-plugin option: mysqladmin \fB\-\-enable\-cleartext\-plugin\fR @@ -800,7 +862,7 @@ Enable the mysql_clear_password cleartext authentication plugin\&. (See -Section\ \&6.3.6.6, \(lqThe Cleartext Client-Side Authentication Plugin\(rq\&.) This option was added in MySQL 5\&.5\&.27\&. +Section\ \&6.3.7.5, \(lqThe Cleartext Client-Side Authentication Plugin\(rq\&.) This option was added in MySQL 5\&.5\&.27\&. .RE .sp .RS 4 @@ -861,6 +923,23 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqladmin: no-defaults option +.\" no-defaults option: mysqladmin +\fB\-\-no\-defaults\fR +.sp +Do not read any option files\&. If program startup fails due to reading unknown options from an option file, +\fB\-\-no\-defaults\fR +can be used to prevent them from being read\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqladmin: password option .\" password option: mysqladmin \fB\-\-password[=\fR\fB\fIpassword\fR\fR\fB]\fR, @@ -944,6 +1023,21 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqladmin: print-defaults option +.\" print-defaults option: mysqladmin +\fB\-\-print\-defaults\fR +.sp +Print the program name and all options that it gets from option files\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqladmin: protocol option .\" protocol option: mysqladmin \fB\-\-protocol={TCP|SOCKET|PIPE|MEMORY}\fR @@ -980,6 +1074,26 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqladmin: shared-memory-base-name option +.\" shared-memory-base-name option: mysqladmin +\fB\-\-shared\-memory\-base\-name=\fR\fB\fIname\fR\fR +.sp +On Windows, the shared\-memory name to use, for connections made using shared memory to a local server\&. The default value is +MYSQL\&. The shared\-memory name is case sensitive\&. +.sp +The server must be started with the +\fB\-\-shared\-memory\fR +option to enable shared\-memory connections\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqladmin: silent option .\" silent option: mysqladmin \fB\-\-silent\fR, @@ -1044,7 +1158,7 @@ Options that begin with \fB\-\-ssl\fR specify whether to connect to the server using SSL and indicate where to find SSL keys and certificates\&. See -Section\ \&6.3.8.4, \(lqSSL Command Options\(rq\&. +Section\ \&6.3.9.4, \(lqSSL Command Options\(rq\&. .RE .sp .RS 4 @@ -1168,7 +1282,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysqlbinlog.1 mysql-5.5-5.5.43/man/mysqlbinlog.1 --- mysql-5.5-5.5.35+dfsg/man/mysqlbinlog.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysqlbinlog.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysqlbinlog\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQLBINLOG\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQLBINLOG\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -43,7 +43,7 @@ \fBmysqlbinlog\fR to display the contents of relay log files written by a slave server in a replication setup because relay logs have the same format as binary logs\&. The binary log and relay log are discussed further in Section\ \&5.2.4, \(lqThe Binary Log\(rq, and -Section\ \&16.2.2, \(lqReplication Relay and Status Logs\(rq\&. +Section\ \&17.2.2, \(lqReplication Relay and Status Logs\(rq\&. .PP Invoke \fBmysqlbinlog\fR @@ -74,7 +74,7 @@ .PP The output includes events contained in binlog\&.000003\&. For statement\-based logging, event information includes the SQL statement, the ID of the server on which it was executed, the timestamp when the statement was executed, how much time it took, and so forth\&. For row\-based logging, the event indicates a row change rather than an SQL statement\&. See -Section\ \&16.1.2, \(lqReplication Formats\(rq, for information about logging modes\&. +Section\ \&17.1.2, \(lqReplication Formats\(rq, for information about logging modes\&. .PP Events are preceded by header comments that provide additional information\&. For example: .sp @@ -92,7 +92,7 @@ .PP In the first line, the number following at -indicates the starting position of the event in the binary log file\&. +indicates the file offset, or starting position, of the event in the binary log file\&. .PP The second line starts with a date and time indicating when the statement started on the server where the event originated\&. For replication, this timestamp is propagated to slave servers\&. server id @@ -107,6 +107,22 @@ is the time spent executing the event, on a master server\&. On a slave, it is the difference of the end execution time on the slave minus the beginning execution time on the master\&. The difference serves as an indicator of how much replication lags behind the master\&. error_code indicates the result from executing the event\&. Zero means that no error occurred\&. +.if n \{\ +.sp +.\} +.RS 4 +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fBNote\fR +.ps -1 +.br +.PP +When using event groups, the file offsets of events may be grouped together and the comments of events may be grouped together\&. Do not mistake these grouped events for blank file offsets\&. +.sp .5v +.RE .PP The output from \fBmysqlbinlog\fR @@ -128,15 +144,21 @@ \fB\-\-read\-from\-remote\-server\fR option\&. .PP +When running +\fBmysqlbinlog\fR +against a large binary log, be careful that the filesystem has enough space for the resulting files\&. To configure the directory that +\fBmysqlbinlog\fR +uses for temporary files, use the +TMPDIR +environment variable\&. +.PP \fBmysqlbinlog\fR supports the following options, which can be specified on the command line or in the [mysqlbinlog] and [client] -groups of an option file\&. -\fBmysqlbinlog\fR -also supports the options for processing option files described at -Section\ \&4.2.3.4, \(lqCommand-Line Options that Affect Option-File Handling\(rq\&. +groups of an option file\&. For information about option files used by MySQL programs, see +Section\ \&4.2.6, \(lqUsing Option Files\(rq\&. .sp .RS 4 .ie n \{\ @@ -301,7 +323,7 @@ .\" bind-address option: mysqlbinlog \fB\-\-bind\-address=\fR\fB\fIip_address\fR\fR .sp -On a computer having multiple network interfaces, this option can be used to select which interface is employed when connecting to the MySQL server\&. +On a computer having multiple network interfaces, use this option to select which interface to use for connecting to the MySQL server\&. .sp This option is supported beginning with MySQL 5\&.5\&.8\&. .RE @@ -503,8 +525,8 @@ Write a debugging log\&. A typical \fIdebug_options\fR string is -\*(Aqd:t:o,\fIfile_name\fR\*(Aq\&. The default is -\*(Aqd:t:o,/tmp/mysqlbinlog\&.trace\*(Aq\&. +d:t:o,\fIfile_name\fR\&. The default is +d:t:o,/tmp/mysqlbinlog\&.trace\&. .RE .sp .RS 4 @@ -549,7 +571,7 @@ .\" default-auth option: mysqlbinlog \fB\-\-default\-auth=\fR\fB\fIplugin\fR\fR .sp -The client\-side authentication plugin to use\&. See +A hint about the client\-side authentication plugin to use\&. See Section\ \&6.3.6, \(lqPluggable Authentication\(rq\&. .sp This option was added in MySQL 5\&.5\&.10\&. @@ -563,6 +585,70 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqlbinlog: defaults-extra-file option +.\" defaults-extra-file option: mysqlbinlog +\fB\-\-defaults\-extra\-file=\fR\fB\fIfile_name\fR\fR +.sp +Read this option file after the global option file but (on Unix) before the user option file\&. If the file does not exist or is otherwise inaccessible, an error occurs\&. Before MySQL 5\&.5\&.8, +\fIfile_name\fR +must be the full path name to the file\&. As of MySQL 5\&.5\&.8, the name is interpreted relative to the current directory if given as a relative path name\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysqlbinlog: defaults-file option +.\" defaults-file option: mysqlbinlog +\fB\-\-defaults\-file=\fR\fB\fIfile_name\fR\fR +.sp +Use only the given option file\&. If the file does not exist or is otherwise inaccessible, an error occurs\&. Before MySQL 5\&.5\&.8, +\fIfile_name\fR +must be the full path name to the file\&. As of MySQL 5\&.5\&.8, the name is interpreted relative to the current directory if given as a relative path name\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysqlbinlog: defaults-group-suffix option +.\" defaults-group-suffix option: mysqlbinlog +\fB\-\-defaults\-group\-suffix=\fR\fB\fIstr\fR\fR +.sp +Read not only the usual option groups, but also groups with the usual names and a suffix of +\fIstr\fR\&. For example, +\fBmysqlbinlog\fR +normally reads the +[client] +and +[mysqlbinlog] +groups\&. If the +\fB\-\-defaults\-group\-suffix=_other\fR +option is given, +\fBmysqlbinlog\fR +also reads the +[client_other] +and +[mysqlbinlog_other] +groups\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqlbinlog: disable-log-bin option .\" disable-log-bin option: mysqlbinlog \fB\-\-disable\-log\-bin\fR, @@ -697,6 +783,23 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqlbinlog: no-defaults option +.\" no-defaults option: mysqlbinlog +\fB\-\-no\-defaults\fR +.sp +Do not read any option files\&. If program startup fails due to reading unknown options from an option file, +\fB\-\-no\-defaults\fR +can be used to prevent them from being read\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqlbinlog: offset option .\" offset option: mysqlbinlog \fB\-\-offset=\fR\fB\fIN\fR\fR, @@ -801,6 +904,21 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqlbinlog: print-defaults option +.\" print-defaults option: mysqlbinlog +\fB\-\-print\-defaults\fR +.sp +Print the program name and all options that it gets from option files\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqlbinlog: protocol option .\" protocol option: mysqlbinlog \fB\-\-protocol={TCP|SOCKET|PIPE|MEMORY}\fR @@ -918,6 +1036,26 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqlbinlog: shared-memory-base-name option +.\" shared-memory-base-name option: mysqlbinlog +\fB\-\-shared\-memory\-base\-name=\fR\fB\fIname\fR\fR +.sp +On Windows, the shared\-memory name to use, for connections made using shared memory to a local server\&. The default value is +MYSQL\&. The shared\-memory name is case sensitive\&. +.sp +The server must be started with the +\fB\-\-shared\-memory\fR +option to enable shared\-memory connections\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqlbinlog: short-form option .\" short-form option: mysqlbinlog \fB\-\-short\-form\fR, @@ -2053,7 +2191,7 @@ .sp -1 .IP \(bu 2.3 .\} -For multi\-byte character sets, the maximum number of bytes per character is not present in the binary log, so the length for string types is displayed in bytes rather than in characters\&. For example, +For multibyte character sets, the maximum number of bytes per character is not present in the binary log, so the length for string types is displayed in bytes rather than in characters\&. For example, STRING(4) will be used as the data type for values from either of these column types: .sp @@ -2102,7 +2240,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysqlbug.1 mysql-5.5-5.5.43/man/mysqlbug.1 --- mysql-5.5-5.5.35+dfsg/man/mysqlbug.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysqlbug.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysqlbug\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQLBUG\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQLBUG\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -42,7 +42,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysqlcheck.1 mysql-5.5-5.5.43/man/mysqlcheck.1 --- mysql-5.5-5.5.35+dfsg/man/mysqlcheck.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysqlcheck.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysqlcheck\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQLCHECK\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQLCHECK\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -110,7 +110,7 @@ If \fBmysqlcheck\fR is unable to repair a table, see -Section\ \&2.12.4, \(lqRebuilding or Repairing Tables or Indexes\(rq +Section\ \&2.11.4, \(lqRebuilding or Repairing Tables or Indexes\(rq for manual table repair strategies\&. This will be the case, for example, for InnoDB tables, which can be checked with @@ -204,10 +204,8 @@ [mysqlcheck] and [client] -groups of an option file\&. -\fBmysqlcheck\fR -also supports the options for processing option files described at -Section\ \&4.2.3.4, \(lqCommand-Line Options that Affect Option-File Handling\(rq\&. +groups of an option file\&. For information about option files used by MySQL programs, see +Section\ \&4.2.6, \(lqUsing Option Files\(rq\&. .sp .RS 4 .ie n \{\ @@ -240,7 +238,13 @@ .sp Check all tables in all databases\&. This is the same as using the \fB\-\-databases\fR -option and naming all the databases on the command line\&. +option and naming all the databases on the command line, except that the +INFORMATION_SCHEMA +and +performace_schema +databases are not dumped\&. They can be dumped by explicitly naming them with the +\fB\-\-databases\fR +option\&. .RE .sp .RS 4 @@ -302,7 +306,7 @@ .\" bind-address option: mysqlcheck \fB\-\-bind\-address=\fR\fB\fIip_address\fR\fR .sp -On a computer having multiple network interfaces, this option can be used to select which interface is employed when connecting to the MySQL server\&. +On a computer having multiple network interfaces, use this option to select which interface to use for connecting to the MySQL server\&. .sp This option is supported only in the version of \fBmysqlcheck\fR @@ -412,6 +416,16 @@ Process all tables in the named databases\&. Normally, \fBmysqlcheck\fR treats the first name argument on the command line as a database name and following names as table names\&. With this option, it treats all name arguments as database names\&. +.sp +This option may be used to dump the +INFORMATION_SCHEMA +and +performace_schema +databases, which normally are not dumped even with the +\fB\-\-all\-databases\fR +option\&. (Also use the +\fB\-\-skip\-lock\-tables\fR +option\&.) .RE .sp .RS 4 @@ -430,8 +444,8 @@ Write a debugging log\&. A typical \fIdebug_options\fR string is -\*(Aqd:t:o,\fIfile_name\fR\*(Aq\&. The default is -\*(Aqd:t:o\*(Aq\&. +d:t:o,\fIfile_name\fR\&. The default is +d:t:o\&. .RE .sp .RS 4 @@ -490,6 +504,70 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqlcheck: defaults-extra-file option +.\" defaults-extra-file option: mysqlcheck +\fB\-\-defaults\-extra\-file=\fR\fB\fIfile_name\fR\fR +.sp +Read this option file after the global option file but (on Unix) before the user option file\&. If the file does not exist or is otherwise inaccessible, an error occurs\&. Before MySQL 5\&.5\&.8, +\fIfile_name\fR +must be the full path name to the file\&. As of MySQL 5\&.5\&.8, the name is interpreted relative to the current directory if given as a relative path name\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysqlcheck: defaults-file option +.\" defaults-file option: mysqlcheck +\fB\-\-defaults\-file=\fR\fB\fIfile_name\fR\fR +.sp +Use only the given option file\&. If the file does not exist or is otherwise inaccessible, an error occurs\&. Before MySQL 5\&.5\&.8, +\fIfile_name\fR +must be the full path name to the file\&. As of MySQL 5\&.5\&.8, the name is interpreted relative to the current directory if given as a relative path name\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysqlcheck: defaults-group-suffix option +.\" defaults-group-suffix option: mysqlcheck +\fB\-\-defaults\-group\-suffix=\fR\fB\fIstr\fR\fR +.sp +Read not only the usual option groups, but also groups with the usual names and a suffix of +\fIstr\fR\&. For example, +\fBmysqlcheck\fR +normally reads the +[client] +and +[mysqlcheck] +groups\&. If the +\fB\-\-defaults\-group\-suffix=_other\fR +option is given, +\fBmysqlcheck\fR +also reads the +[client_other] +and +[mysqlcheck_other] +groups\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqlcheck: extended option .\" extended option: mysqlcheck \fB\-\-extended\fR, @@ -512,7 +590,7 @@ .\" default-auth option: mysqlcheck \fB\-\-default\-auth=\fR\fB\fIplugin\fR\fR .sp -The client\-side authentication plugin to use\&. See +A hint about the client\-side authentication plugin to use\&. See Section\ \&6.3.6, \(lqPluggable Authentication\(rq\&. .sp This option was added in MySQL 5\&.5\&.10\&. @@ -622,6 +700,23 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqlcheck: no-defaults option +.\" no-defaults option: mysqlcheck +\fB\-\-no\-defaults\fR +.sp +Do not read any option files\&. If program startup fails due to reading unknown options from an option file, +\fB\-\-no\-defaults\fR +can be used to prevent them from being read\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqlcheck: optimize option .\" optimize option: mysqlcheck \fB\-\-optimize\fR, @@ -721,6 +816,21 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqlcheck: print-defaults option +.\" print-defaults option: mysqlcheck +\fB\-\-print\-defaults\fR +.sp +Print the program name and all options that it gets from option files\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqlcheck: protocol option .\" protocol option: mysqlcheck \fB\-\-protocol={TCP|SOCKET|PIPE|MEMORY}\fR @@ -771,6 +881,26 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqlcheck: shared-memory-base-name option +.\" shared-memory-base-name option: mysqlcheck +\fB\-\-shared\-memory\-base\-name=\fR\fB\fIname\fR\fR +.sp +On Windows, the shared\-memory name to use, for connections made using shared memory to a local server\&. The default value is +MYSQL\&. The shared\-memory name is case sensitive\&. +.sp +The server must be started with the +\fB\-\-shared\-memory\fR +option to enable shared\-memory connections\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqlcheck: silent option .\" silent option: mysqlcheck \fB\-\-silent\fR, @@ -811,7 +941,7 @@ Options that begin with \fB\-\-ssl\fR specify whether to connect to the server using SSL and indicate where to find SSL keys and certificates\&. See -Section\ \&6.3.8.4, \(lqSSL Command Options\(rq\&. +Section\ \&6.3.9.4, \(lqSSL Command Options\(rq\&. .RE .sp .RS 4 @@ -931,7 +1061,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysql_client_test.1 mysql-5.5-5.5.43/man/mysql_client_test.1 --- mysql-5.5-5.5.35+dfsg/man/mysql_client_test.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysql_client_test.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysql_client_test\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/25/2015 .\" Manual: MySQL Database System .\" Source: MySQL .\" Language: English .\" -.TH "\FBMYSQL_CLIENT_TEST" "1" "11/04/2013" "MySQL" "MySQL Database System" +.TH "\FBMYSQL_CLIENT_TEST" "1" "02/25/2015" "MySQL" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -335,7 +335,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 2006, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 2006, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysql_client_test_embedded.1 mysql-5.5-5.5.43/man/mysql_client_test_embedded.1 --- mysql-5.5-5.5.35+dfsg/man/mysql_client_test_embedded.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysql_client_test_embedded.1 2015-02-27 08:30:42.000000000 +0000 @@ -1 +1 @@ -.so man-gpl-tmp2/mysql_client_test.1 +.so man/mysql_client_test.1 diff -Nru mysql-5.5-5.5.35+dfsg/man/mysql_config.1 mysql-5.5-5.5.43/man/mysql_config.1 --- mysql-5.5-5.5.35+dfsg/man/mysql_config.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysql_config.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysql_config\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQL_CONFIG\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQL_CONFIG\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -231,7 +231,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysql_convert_table_format.1 mysql-5.5-5.5.43/man/mysql_convert_table_format.1 --- mysql-5.5-5.5.35+dfsg/man/mysql_convert_table_format.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysql_convert_table_format.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysql_convert_table_format\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQL_CONVERT_TAB" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQL_CONVERT_TAB" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -44,7 +44,7 @@ and DBD::mysql Perl modules be installed (see -Section\ \&2.14, \(lqPerl Installation Notes\(rq)\&. +Section\ \&2.13, \(lqPerl Installation Notes\(rq)\&. .PP Invoke \fBmysql_convert_table_format\fR @@ -225,7 +225,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysqld.8 mysql-5.5-5.5.43/man/mysqld.8 --- mysql-5.5-5.5.35+dfsg/man/mysqld.8 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysqld.8 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysqld\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQLD\FR" "8" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQLD\FR" "8" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -62,7 +62,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysqld_multi.1 mysql-5.5-5.5.43/man/mysqld_multi.1 --- mysql-5.5-5.5.35+dfsg/man/mysqld_multi.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysqld_multi.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysqld_multi\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQLD_MULTI\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQLD_MULTI\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -49,7 +49,7 @@ in my\&.cnf (or in the file named by the -\fB\-\-config\-file\fR +\fB\-\-defaults\-file\fR option)\&. \fIN\fR can be any positive integer\&. This number is referred to in the following discussion as the option group number, or @@ -59,7 +59,7 @@ [mysqld] group used for starting \fBmysqld\fR\&. (See, for example, -Section\ \&2.11.1.2, \(lqStarting and Stopping MySQL Automatically\(rq\&.) However, when using multiple servers, it is necessary that each one use its own value for options such as the Unix socket file and TCP/IP port number\&. For more information on which options must be unique per server in a multiple\-server environment, see +Section\ \&2.10.3, \(lqStarting and Stopping MySQL Automatically\(rq\&.) However, when using multiple servers, it is necessary that each one use its own value for options such as the Unix socket file and TCP/IP port number\&. For more information on which options must be unique per server in a multiple\-server environment, see Section\ \&5.3, \(lqRunning Multiple MySQL Instances on One Machine\(rq\&. .PP To invoke @@ -701,11 +701,11 @@ .\} .PP See -Section\ \&4.2.3.3, \(lqUsing Option Files\(rq\&. +Section\ \&4.2.6, \(lqUsing Option Files\(rq\&. .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysqld_safe.1 mysql-5.5-5.5.43/man/mysqld_safe.1 --- mysql-5.5-5.5.35+dfsg/man/mysqld_safe.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysqld_safe.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysqld_safe\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQLD_SAFE\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQLD_SAFE\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -70,7 +70,7 @@ if they are specified on the command line, but ignored if they are specified in the [mysqld_safe] group of an option file\&. See -Section\ \&4.2.3.3, \(lqUsing Option Files\(rq\&. +Section\ \&4.2.6, \(lqUsing Option Files\(rq\&. .PP \fBmysqld_safe\fR reads all options from the @@ -100,13 +100,15 @@ \fBmysqld_safe\fR also reads [safe_mysqld] -sections, although you should rename such sections to +sections, although it is preferable to rename +[safe_mysqld] +sections to [mysqld_safe] -in MySQL 5\&.5 installations\&. +sections\&. .PP \fBmysqld_safe\fR supports the following options\&. It also reads option files and supports the options for processing them described at -Section\ \&4.2.3.4, \(lqCommand-Line Options that Affect Option-File Handling\(rq\&. +Section\ \&4.2.7, \(lqCommand-Line Options that Affect Option-File Handling\(rq\&. .sp .RS 4 .ie n \{\ @@ -472,11 +474,26 @@ The number of files that \fBmysqld\fR should be able to open\&. The option value is passed to -\fBulimit \-n\fR\&. Note that you need to start +\fBulimit \-n\fR\&. +.if n \{\ +.sp +.\} +.RS 4 +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fBNote\fR +.ps -1 +.br +You must start \fBmysqld_safe\fR as root -for this to work properly! +for this to function properly\&. +.sp .5v +.RE .RE .sp .RS 4 @@ -587,7 +604,7 @@ syslog is used, the daemon\&.err -syslog priority/facility is used for all log messages\&. +syslog facility/severity is used for all log messages\&. .RE .sp .RS 4 @@ -607,11 +624,11 @@ \fBmysqld_safe\fR and \fBmysqld\fR -are written with a tag of +are written with identifiers of mysqld_safe and -mysqld, respectively\&. To specify a suffix for the tag, use -\fB\-\-syslog\-tag=\fR\fB\fItag\fR\fR, which modifies the tags to be +mysqld, respectively\&. To specify a suffix for the identifiers, use +\fB\-\-syslog\-tag=\fR\fB\fItag\fR\fR, which modifies the identifiers to be mysqld_safe\-\fItag\fR and mysqld\-\fItag\fR\&. @@ -688,7 +705,7 @@ The \fBmysqld_safe\fR script is written so that it normally can start a server that was installed from either a source or a binary distribution of MySQL, even though these types of distributions typically install the server in slightly different locations\&. (See -Section\ \&2.1.5, \(lqInstallation Layouts\(rq\&.) +Section\ \&2.1.4, \(lqInstallation Layouts\(rq\&.) \fBmysqld_safe\fR expects one of the following conditions to be true: .sp @@ -754,7 +771,7 @@ .PP If \fBmysqld_safe\fR -fails, even when invoked from the MySQL installation directory, you can specify the +fails, even when invoked from the MySQL installation directory, specify the \fB\-\-ledir\fR and \fB\-\-datadir\fR @@ -789,11 +806,7 @@ .sp -1 .IP \(bu 2.3 .\} -\fB\-\-syslog\fR: Write error messages to -syslog -on systems that support the -\fBlogger\fR -program\&. +\fB\-\-log\-error=\fR\fB\fIfile_name\fR\fR: Write error messages to the named error file\&. .RE .sp .RS 4 @@ -804,11 +817,11 @@ .sp -1 .IP \(bu 2.3 .\} -\fB\-\-skip\-syslog\fR: Do not write error messages to -syslog\&. Messages are written to the default error log file (\fIhost_name\fR\&.err -in the data directory), or to a named file if the -\fB\-\-log\-error\fR -option is given\&. +\fB\-\-syslog\fR: Write error messages to +syslog +on systems that support the +\fBlogger\fR +program\&. .RE .sp .RS 4 @@ -819,16 +832,20 @@ .sp -1 .IP \(bu 2.3 .\} -\fB\-\-log\-error=\fR\fB\fIfile_name\fR\fR: Write error messages to the named error file\&. +\fB\-\-skip\-syslog\fR: Do not write error messages to +syslog\&. Messages are written to the default error log file (\fIhost_name\fR\&.err +in the data directory), or to a named file if the +\fB\-\-log\-error\fR +option is given\&. .RE .PP If none of these options is given, the default is \fB\-\-skip\-syslog\fR\&. .PP If -\fB\-\-syslog\fR -and \fB\-\-log\-error\fR +and +\fB\-\-syslog\fR are both given, a warning is issued and \fB\-\-log\-error\fR takes precedence\&. @@ -856,7 +873,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysqldump.1 mysql-5.5-5.5.43/man/mysqldump.1 --- mysql-5.5-5.5.35+dfsg/man/mysqldump.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysqldump.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysqldump\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQLDUMP\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQLDUMP\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -75,8 +75,48 @@ tables, you can also use \fBmysqlhotcopy\fR for this purpose\&. - Performance and Scalability Considerations +.if n \{\ +.sp +.\} +.RS 4 +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fBNote\fR +.ps -1 +.br .PP +A dump made using PowerShell on Windows with output redirection creates a file that has UTF\-16 encoding: +.sp +.if n \{\ +.RS 4 +.\} +.nf +mysqldump [options] > dump\&.sql +.fi +.if n \{\ +.RE +.\} +.PP +However, UTF\-16 is not permitted as a connection character set (see +Section\ \&10.1.4, \(lqConnection Character Sets and Collations\(rq), so the dump file will not load correctly\&. To work around this issue, use the +\fB\-\-result\-file\fR +option, which creates the output in ASCII format: +.sp +.if n \{\ +.RS 4 +.\} +.nf +mysqldump [options] \-\-result\-file=dump\&.sql +.fi +.if n \{\ +.RE +.\} +.sp .5v +.RE +Performance and Scalability Considerations.PP mysqldump advantages include the convenience and flexibility of viewing or even editing the output before restoring\&. You can clone databases for development and DBA work, or produce slight variations of an existing database for testing\&. It is not intended as a fast or scalable solution for backing up substantial amounts of data\&. With large data sizes, even if the backup step takes a reasonable time, restoring the data can be very slow because replaying the SQL statements involves disk I/O for insertion, index creation, and so on\&. .PP @@ -105,7 +145,7 @@ backups with minimal disruption; it can also back up tables from MyISAM and other storage engines; and it provides a number of convenient options to accommodate different backup scenarios\&. See -Section\ \&24.2, \(lqMySQL Enterprise Backup\(rq\&. +Section\ \&25.2, \(lqMySQL Enterprise Backup\(rq\&. .RE .sp .RS 4 @@ -150,8 +190,7 @@ For additional information about \fBmysqldump\fR, see Section\ \&7.4, \(lqUsing mysqldump for Backups\(rq\&. - Syntax -.PP +Syntax.PP There are in general three ways to use \fBmysqldump\fR\(emin order to dump a set of one or more tables, a set of one or more complete databases, or an entire MySQL server\(emas shown here: .sp @@ -177,12 +216,12 @@ \fBmysqldump\fR does not dump the INFORMATION_SCHEMA -database by default\&. -\fBmysqldump\fR -dumps -INFORMATION_SCHEMA -only if you name it explicitly on the command line, although currently you must also use the +or +performance_schema +database by default\&. To dump either of these, name it explicitly on the command line and also use the \fB\-\-skip\-lock\-tables\fR +option\&. You can also name them with the +\fB\-\-databases\fR option\&. Before MySQL 5\&.5 \fBmysqldump\fR silently ignores @@ -345,10 +384,8 @@ [mysqldump] and [client] -groups of an option file\&. -\fBmysqldump\fR -also supports the options for processing option files described at -Section\ \&4.2.3.4, \(lqCommand-Line Options that Affect Option-File Handling\(rq\&. +groups of an option file\&. For information about option files used by MySQL programs, see +Section\ \&4.2.6, \(lqUsing Option Files\(rq\&. .sp .RS 4 .ie n \{\ @@ -553,7 +590,7 @@ .\" bind-address option: mysqldump \fB\-\-bind\-address=\fR\fB\fIip_address\fR\fR .sp -On a computer having multiple network interfaces, this option can be used to select which interface is employed when connecting to the MySQL server\&. +On a computer having multiple network interfaces, use this option to select which interface to use for connecting to the MySQL server\&. .sp This option is supported only in the version of \fBmysqldump\fR @@ -738,8 +775,8 @@ Write a debugging log\&. A typical \fIdebug_options\fR string is -\*(Aqd:t:o,\fIfile_name\fR\*(Aq\&. The default value is -\*(Aqd:t:o,/tmp/mysqldump\&.trace\*(Aq\&. +d:t:o,\fIfile_name\fR\&. The default value is +d:t:o,/tmp/mysqldump\&.trace\&. .RE .sp .RS 4 @@ -784,7 +821,7 @@ .\" default-auth option: mysqldump \fB\-\-default\-auth=\fR\fB\fIplugin\fR\fR .sp -The client\-side authentication plugin to use\&. See +A hint about the client\-side authentication plugin to use\&. See Section\ \&6.3.6, \(lqPluggable Authentication\(rq\&. .sp This option was added in MySQL 5\&.5\&.9\&. @@ -808,8 +845,71 @@ Section\ \&10.5, \(lqCharacter Set Configuration\(rq\&. If no character set is specified, \fBmysqldump\fR uses -utf8, and earlier versions use -latin1\&. +utf8\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysqldump: defaults-extra-file option +.\" defaults-extra-file option: mysqldump +\fB\-\-defaults\-extra\-file=\fR\fB\fIfile_name\fR\fR +.sp +Read this option file after the global option file but (on Unix) before the user option file\&. If the file does not exist or is otherwise inaccessible, an error occurs\&. Before MySQL 5\&.5\&.8, +\fIfile_name\fR +must be the full path name to the file\&. As of MySQL 5\&.5\&.8, the name is interpreted relative to the current directory if given as a relative path name\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysqldump: defaults-file option +.\" defaults-file option: mysqldump +\fB\-\-defaults\-file=\fR\fB\fIfile_name\fR\fR +.sp +Use only the given option file\&. If the file does not exist or is otherwise inaccessible, an error occurs\&. Before MySQL 5\&.5\&.8, +\fIfile_name\fR +must be the full path name to the file\&. As of MySQL 5\&.5\&.8, the name is interpreted relative to the current directory if given as a relative path name\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysqldump: defaults-group-suffix option +.\" defaults-group-suffix option: mysqldump +\fB\-\-defaults\-group\-suffix=\fR\fB\fIstr\fR\fR +.sp +Read not only the usual option groups, but also groups with the usual names and a suffix of +\fIstr\fR\&. For example, +\fBmysqldump\fR +normally reads the +[client] +and +[mysqldump] +groups\&. If the +\fB\-\-defaults\-group\-suffix=_other\fR +option is given, +\fBmysqldump\fR +also reads the +[client_other] +and +[mysqldump_other] +groups\&. .RE .sp .RS 4 @@ -928,13 +1028,20 @@ \fB\-\-master\-data\fR except that it is used to dump a replication slave server to produce a dump file that can be used to set up another server as a slave that has the same master as the dumped server\&. It causes the dump output to include a CHANGE MASTER TO -statement that indicates the binary log coordinates (file name and position) of the dumped slave\*(Aqs master (rather than the coordinates of the dumped server, as is done by the +statement that indicates the binary log coordinates (file name and position) of the dumped slave\*(Aqs master\&. These are the master server coordinates from which the slave should start replicating\&. +.sp +\fB\-\-dump\-slave\fR +causes the coordinates from the master to be used rather than those of the dumped server, as is done by the +\fB\-\-master\-data\fR +option\&. In addition, specfiying this option causes the \fB\-\-master\-data\fR -option)\&. These are the master server coordinates from which the slave should start replicating\&. This option was added in MySQL 5\&.5\&.3\&. +option to be overridden, if used, and effectively ignored\&. .sp The option value is handled the same way as for \fB\-\-master\-data\fR -and has the same effect as +(setting no value or 1 causes a +CHANGE MASTER TO +statement to be written to the dump, setting 2 causes the statement to be written but encased in SQL comments) and has the same effect as \fB\-\-master\-data\fR in terms of enabling or disabling other options and in how locking is handled\&. .sp @@ -948,6 +1055,8 @@ and \fB\-\-include\-master\-host\-port\fR options can also be used\&. +.sp +This option was added in MySQL 5\&.5\&.3\&. .RE .sp .RS 4 @@ -963,7 +1072,9 @@ \fB\-\-events\fR, \fB\-E\fR .sp -Include Event Scheduler events for the dumped databases in the output\&. +Include Event Scheduler events for the dumped databases in the output\&. This option requires the +EVENT +privileges for those databases\&. .RE .sp .RS 4 @@ -1329,7 +1440,9 @@ .sp It is also possible to set up a slave by dumping an existing slave of the master\&. In MySQL 5\&.5\&.3 and later, you can create such a dump using the \fB\-\-dump\-slave\fR -option\&. +option, which overrides +\fB\-\-master\-data\fR +and causes it to be ignored if both options are used\&. .sp In MySQL 5\&.2\&.2 and earlier, use the following procedure on the existing slave: .sp @@ -1586,6 +1699,23 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqldump: no-defaults option +.\" no-defaults option: mysqldump +\fB\-\-no\-defaults\fR +.sp +Do not read any option files\&. If program startup fails due to reading unknown options from an option file, +\fB\-\-no\-defaults\fR +can be used to prevent them from being read\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqldump: no-set-names option .\" no-set-names option: mysqldump \fB\-\-no\-set\-names\fR, @@ -1753,6 +1883,21 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqldump: print-defaults option +.\" print-defaults option: mysqldump +\fB\-\-print\-defaults\fR +.sp +Print the program name and all options that it gets from option files\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqldump: protocol option .\" protocol option: mysqldump \fB\-\-protocol={TCP|SOCKET|PIPE|MEMORY}\fR @@ -1909,6 +2054,26 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqldump: shared-memory-base-name option +.\" shared-memory-base-name option: mysqldump +\fB\-\-shared\-memory\-base\-name=\fR\fB\fIname\fR\fR +.sp +On Windows, the shared\-memory name to use, for connections made using shared memory to a local server\&. The default value is +MYSQL\&. The shared\-memory name is case sensitive\&. +.sp +The server must be started with the +\fB\-\-shared\-memory\fR +option to enable shared\-memory connections\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqldump: single-transaction option .\" single-transaction option: mysqldump \fB\-\-single\-transaction\fR @@ -1930,7 +2095,7 @@ MEMORY tables dumped while using this option may still change state\&. .sp -Before MySQL 5\&.5\&.3, while a +While a \fB\-\-single\-transaction\fR dump is in process, to ensure a valid dump file (correct table contents and binary log coordinates), no other connection should use the following statements: ALTER TABLE, @@ -1941,7 +2106,7 @@ SELECT that is performed by \fBmysqldump\fR -to retrieve the table contents to obtain incorrect contents or fail\&. As of MySQL 5\&.5\&.3, metadata locking prevents this situation\&. +to retrieve the table contents to obtain incorrect contents or fail\&. .sp The \fB\-\-single\-transaction\fR @@ -1959,10 +2124,11 @@ NDB backup and restore instead\&. .sp -To dump large tables, you should combine the +To dump large tables, combine the \fB\-\-single\-transaction\fR -option with -\fB\-\-quick\fR\&. +option with the +\fB\-\-quick\fR +option\&. .RE .sp .RS 4 @@ -2031,7 +2197,7 @@ Options that begin with \fB\-\-ssl\fR specify whether to connect to the server using SSL and indicate where to find SSL keys and certificates\&. See -Section\ \&6.3.8.4, \(lqSSL Command Options\(rq\&. +Section\ \&6.3.9.4, \(lqSSL Command Options\(rq\&. .RE .sp .RS 4 @@ -2482,7 +2648,7 @@ .RS 4 .\} .nf -shell> \fBmysqldump \-\-all\-databases \-\-single\-transaction > all_databases\&.sql\fR +shell> \fBmysqldump \-\-all\-databases \-\-master\-data \-\-single\-transaction > all_databases\&.sql\fR .fi .if n \{\ .RE @@ -2537,11 +2703,11 @@ .\" mysqldump: workarounds .PP If you encounter problems backing up views, please read the section that covers restrictions on views which describes a workaround for backing up views when this fails due to insufficient privileges\&. See -Section\ \&E.5, \(lqRestrictions on Views\(rq\&. +Section\ \&D.5, \(lqRestrictions on Views\(rq\&. .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysqldumpslow.1 mysql-5.5-5.5.43/man/mysqldumpslow.1 --- mysql-5.5-5.5.35+dfsg/man/mysqldumpslow.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysqldumpslow.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysqldumpslow\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQLDUMPSLOW\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQLDUMPSLOW\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -323,7 +323,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysql_find_rows.1 mysql-5.5-5.5.43/man/mysql_find_rows.1 --- mysql-5.5-5.5.35+dfsg/man/mysql_find_rows.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysql_find_rows.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysql_find_rows\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQL_FIND_ROWS\F" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQL_FIND_ROWS\F" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -160,7 +160,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysql_fix_extensions.1 mysql-5.5-5.5.43/man/mysql_fix_extensions.1 --- mysql-5.5-5.5.35+dfsg/man/mysql_fix_extensions.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysql_fix_extensions.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysql_fix_extensions\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQL_FIX_EXTENSI" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQL_FIX_EXTENSI" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -70,7 +70,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysqlhotcopy.1 mysql-5.5-5.5.43/man/mysqlhotcopy.1 --- mysql-5.5-5.5.35+dfsg/man/mysqlhotcopy.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysqlhotcopy.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysqlhotcopy\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQLHOTCOPY\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQLHOTCOPY\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -113,8 +113,8 @@ [mysqlhotcopy] and [client] -groups of an option file\&. For information about option files, see -Section\ \&4.2.3.3, \(lqUsing Option Files\(rq\&. +groups of an option file\&. For information about option files used by MySQL programs, see +Section\ \&4.2.6, \(lqUsing Option Files\(rq\&. .sp .RS 4 .ie n \{\ @@ -544,7 +544,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysqlimport.1 mysql-5.5-5.5.43/man/mysqlimport.1 --- mysql-5.5-5.5.35+dfsg/man/mysqlimport.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysqlimport.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysqlimport\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQLIMPORT\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQLIMPORT\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -78,10 +78,8 @@ [mysqlimport] and [client] -groups of an option file\&. -\fBmysqlimport\fR -also supports the options for processing option files described at -Section\ \&4.2.3.4, \(lqCommand-Line Options that Affect Option-File Handling\(rq\&. +groups of an option file\&. For information about option files used by MySQL programs, see +Section\ \&4.2.6, \(lqUsing Option Files\(rq\&. .sp .RS 4 .ie n \{\ @@ -111,7 +109,7 @@ .\" bind-address option: mysqlimport \fB\-\-bind\-address=\fR\fB\fIip_address\fR\fR .sp -On a computer having multiple network interfaces, this option can be used to select which interface is employed when connecting to the MySQL server\&. +On a computer having multiple network interfaces, use this option to select which interface to use for connecting to the MySQL server\&. .sp This option is supported only in the version of \fBmysqlimport\fR @@ -182,8 +180,8 @@ Write a debugging log\&. A typical \fIdebug_options\fR string is -\*(Aqd:t:o,\fIfile_name\fR\*(Aq\&. The default is -\*(Aqd:t:o\*(Aq\&. +d:t:o,\fIfile_name\fR\&. The default is +d:t:o\&. .RE .sp .RS 4 @@ -246,7 +244,7 @@ .\" default-auth option: mysqlimport \fB\-\-default\-auth=\fR\fB\fIplugin\fR\fR .sp -The client\-side authentication plugin to use\&. See +A hint about the client\-side authentication plugin to use\&. See Section\ \&6.3.6, \(lqPluggable Authentication\(rq\&. .sp This option was added in MySQL 5\&.5\&.10\&. @@ -260,6 +258,70 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqlimport: defaults-extra-file option +.\" defaults-extra-file option: mysqlimport +\fB\-\-defaults\-extra\-file=\fR\fB\fIfile_name\fR\fR +.sp +Read this option file after the global option file but (on Unix) before the user option file\&. If the file does not exist or is otherwise inaccessible, an error occurs\&. Before MySQL 5\&.5\&.8, +\fIfile_name\fR +must be the full path name to the file\&. As of MySQL 5\&.5\&.8, the name is interpreted relative to the current directory if given as a relative path name\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysqlimport: defaults-file option +.\" defaults-file option: mysqlimport +\fB\-\-defaults\-file=\fR\fB\fIfile_name\fR\fR +.sp +Use only the given option file\&. If the file does not exist or is otherwise inaccessible, an error occurs\&. Before MySQL 5\&.5\&.8, +\fIfile_name\fR +must be the full path name to the file\&. As of MySQL 5\&.5\&.8, the name is interpreted relative to the current directory if given as a relative path name\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysqlimport: defaults-group-suffix option +.\" defaults-group-suffix option: mysqlimport +\fB\-\-defaults\-group\-suffix=\fR\fB\fIstr\fR\fR +.sp +Read not only the usual option groups, but also groups with the usual names and a suffix of +\fIstr\fR\&. For example, +\fBmysqlimport\fR +normally reads the +[client] +and +[mysqlimport] +groups\&. If the +\fB\-\-defaults\-group\-suffix=_other\fR +option is given, +\fBmysqlimport\fR +also reads the +[client_other] +and +[mysqlimport_other] +groups\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqlimport: delete option .\" delete option: mysqlimport \fB\-\-delete\fR, @@ -445,6 +507,23 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqlimport: no-defaults option +.\" no-defaults option: mysqlimport +\fB\-\-no\-defaults\fR +.sp +Do not read any option files\&. If program startup fails due to reading unknown options from an option file, +\fB\-\-no\-defaults\fR +can be used to prevent them from being read\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqlimport: password option .\" password option: mysqlimport \fB\-\-password[=\fR\fB\fIpassword\fR\fR\fB]\fR, @@ -528,6 +607,21 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqlimport: print-defaults option +.\" print-defaults option: mysqlimport +\fB\-\-print\-defaults\fR +.sp +Print the program name and all options that it gets from option files\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqlimport: protocol option .\" protocol option: mysqlimport \fB\-\-protocol={TCP|SOCKET|PIPE|MEMORY}\fR @@ -566,6 +660,26 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqlimport: shared-memory-base-name option +.\" shared-memory-base-name option: mysqlimport +\fB\-\-shared\-memory\-base\-name=\fR\fB\fIname\fR\fR +.sp +On Windows, the shared\-memory name to use, for connections made using shared memory to a local server\&. The default value is +MYSQL\&. The shared\-memory name is case sensitive\&. +.sp +The server must be started with the +\fB\-\-shared\-memory\fR +option to enable shared\-memory connections\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqlimport: silent option .\" silent option: mysqlimport \fB\-\-silent\fR, @@ -606,7 +720,7 @@ Options that begin with \fB\-\-ssl\fR specify whether to connect to the server using SSL and indicate where to find SSL keys and certificates\&. See -Section\ \&6.3.8.4, \(lqSSL Command Options\(rq\&. +Section\ \&6.3.9.4, \(lqSSL Command Options\(rq\&. .RE .sp .RS 4 @@ -710,7 +824,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysql_install_db.1 mysql-5.5-5.5.43/man/mysql_install_db.1 --- mysql-5.5-5.5.35+dfsg/man/mysql_install_db.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysql_install_db.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysql_install_db\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQL_INSTALL_DB\" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQL_INSTALL_DB\" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -56,13 +56,12 @@ .\} .PP Because the MySQL server, -\fBmysqld\fR, needs to access the data directory when it runs later, you should either run +\fBmysqld\fR, must access the data directory when it runs later, you should either run \fBmysql_install_db\fR from the same system account that will be used for running -\fBmysqld\fR -or run it as +\fBmysqld\fR, or run it as root -and use the +and specify the \fB\-\-user\fR option to indicate the user name that \fBmysqld\fR @@ -85,15 +84,7 @@ .if n \{\ .RE .\} -.PP -\fBmysql_install_db\fR -needs to invoke -\fBmysqld\fR -with the -\fB\-\-bootstrap\fR -and -\fB\-\-skip\-grant\-tables\fR -options\&. +.sp .if n \{\ .sp .\} @@ -128,11 +119,23 @@ can also be specified in the [mysqld] group\&.) Other options are passed to -\fBmysqld\fR\&. For information about option files, see -Section\ \&4.2.3.3, \(lqUsing Option Files\(rq\&. -\fBmysql_install_db\fR -also supports the options for processing option files described at -Section\ \&4.2.3.4, \(lqCommand-Line Options that Affect Option-File Handling\(rq\&. +\fBmysqld\fR\&. For information about option files used by MySQL programs, see +Section\ \&4.2.6, \(lqUsing Option Files\(rq\&. +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysql_install_db: help option +.\" help option: mysql_install_db +\fB\-\-help\fR +.sp +Display a help message and exit\&. +.RE .sp .RS 4 .ie n \{\ @@ -157,12 +160,41 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysql_install_db: builddir option +.\" builddir option: mysql_install_db +\fB\-\-builddir=\fR\fB\fIpath\fR\fR +.sp +For use with +\fB\-\-srcdir\fR +and out\-of\-source builds\&. Set this to the location of the directory where the built files reside\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysql_install_db: cross-bootstrap option +.\" cross-bootstrap option: mysql_install_db +\fB\-\-cross\-bootstrap\fR +.sp +For internal use\&. This option is used for building system tables on one host intended for another\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysql_install_db: datadir option .\" datadir option: mysql_install_db -.\" mysql_install_db: ldata option -.\" ldata option: mysql_install_db -\fB\-\-datadir=\fR\fB\fIpath\fR\fR, -\fB\-\-ldata=\fR\fB\fIpath\fR\fR +\fB\-\-datadir=\fR\fB\fIpath\fR\fR .sp The path to the MySQL data directory\&. .RE @@ -175,13 +207,77 @@ .sp -1 .IP \(bu 2.3 .\} +.\" defaults-extra-file option +\fB\-\-defaults\-extra\-file=\fR\fB\fIfile_name\fR\fR +.sp +Read this option file after the global option file but (on Unix) before the user option file\&. If the file does not exist or is otherwise inaccessible, an error occurs\&. +\fIfile_name\fR +is interpreted relative to the current directory if given as a relative path name rather than a full path name\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" defaults-file option +\fB\-\-defaults\-file=\fR\fB\fIfile_name\fR\fR +.sp +Use only the given option file\&. If the file does not exist or is otherwise inaccessible, an error occurs\&. +\fIfile_name\fR +is interpreted relative to the current directory if given as a relative path name rather than a full path name\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysql_install_db: force option .\" force option: mysql_install_db \fB\-\-force\fR .sp Cause \fBmysql_install_db\fR -to run even if DNS does not work\&. Grant table entries that normally use host names will use IP addresses\&. +to run even if DNS does not work\&. Grant table entries normally created using host names will use IP addresses instead\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysql_install_db: ldata option +.\" ldata option: mysql_install_db +\fB\-\-ldata=\fR\fB\fIpath\fR\fR +.sp +A synonym for +\fB\-\-datadir\fR\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" no-defaults option +\fB\-\-no\-defaults\fR +.sp +Do not read any option files\&. If program startup fails due to reading unknown options from an option file, +\fB\-\-no\-defaults\fR +can be used to prevent them from being read\&. .RE .sp .RS 4 @@ -246,9 +342,9 @@ The system (login) user name to use for running \fBmysqld\fR\&. Files and directories created by \fBmysqld\fR -will be owned by this user\&. You must be +will be owned by this user\&. You must be the system root -to use this option\&. By default, +user to use this option\&. By default, \fBmysqld\fR runs using your current login name and files and directories that it creates will be owned by you\&. .RE @@ -285,7 +381,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysql_plugin.1 mysql-5.5-5.5.43/man/mysql_plugin.1 --- mysql-5.5-5.5.35+dfsg/man/mysql_plugin.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysql_plugin.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysql_plugin\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQL_PLUGIN\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQL_PLUGIN\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -163,8 +163,8 @@ \fB\-\-basedir\fR, \fB\-\-datadir\fR, and \fB\-\-plugin\-dir\fR -options and ignores others\&. For information about option files, see -Section\ \&4.2.3.3, \(lqUsing Option Files\(rq\&. +options and ignores others\&. For information about option files used by MySQL programs, see +Section\ \&4.2.6, \(lqUsing Option Files\(rq\&. .sp .RS 4 .ie n \{\ @@ -370,7 +370,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysql_secure_installation.1 mysql-5.5-5.5.43/man/mysql_secure_installation.1 --- mysql-5.5-5.5.35+dfsg/man/mysql_secure_installation.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysql_secure_installation.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysql_secure_installation\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQL_SECURE_INST" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQL_SECURE_INST" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -90,7 +90,7 @@ .PP \fBmysql_secure_installation\fR helps you implement security recommendations similar to those described at -Section\ \&2.11.2, \(lqSecuring the Initial MySQL Accounts\(rq\&. +Section\ \&2.10.2, \(lqSecuring the Initial MySQL Accounts\(rq\&. .PP Invoke \fBmysql_secure_installation\fR @@ -110,7 +110,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysql.server.1 mysql-5.5-5.5.43/man/mysql.server.1 --- mysql-5.5-5.5.35+dfsg/man/mysql.server.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysql.server.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysql.server\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQL\&.SERVER\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQL\&.SERVER\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -36,7 +36,8 @@ .SH "DESCRIPTION" .PP MySQL distributions on Unix include a script named -\fBmysql\&.server\fR\&. It can be used on systems such as Linux and Solaris that use System V\-style run directories to start and stop system services\&. It is also used by the Mac OS X Startup Item for MySQL\&. +\fBmysql\&.server\fR, which starts the server using +\fBmysqld_safe\fR\&. It can be used on systems such as Linux and Solaris that use System V\-style run directories to start and stop system services\&. It is also used by the OS X Startup Item for MySQL\&. .PP \fBmysql\&.server\fR can be found in the @@ -57,7 +58,7 @@ If you install MySQL from a source distribution or using a binary distribution format that does not install \fBmysql\&.server\fR automatically, you can install it manually\&. Instructions are provided in -Section\ \&2.11.1.2, \(lqStarting and Stopping MySQL Automatically\(rq\&. +Section\ \&2.10.3, \(lqStarting and Stopping MySQL Automatically\(rq\&. .PP \fBmysql\&.server\fR reads options from the @@ -116,6 +117,31 @@ \fB\-\-pid\-file=\fR\fB\fIfile_name\fR\fR .sp The path name of the file in which the server should write its process ID\&. +.sp +If this option is not given, +\fBmysql\&.server\fR +uses a default value of +\fIhost_name\fR\&.pid\&. The PID file value passed to +\fBmysqld_safe\fR +overrides any value specified in the +[mysqld_safe] +option file group\&. Because +\fBmysql\&.server\fR +reads the +[mysqld] +option file group but not the +[mysqld_safe] +group, you can ensure that +\fBmysqld_safe\fR +gets the same value when invoke using +\fBmysql\&.server\fR +as when invoked manually by putting the same +pid\-file +setting in both the +[mysqld_safe] +and +[mysqld] +groups\&. .RE .sp .RS 4 @@ -128,49 +154,16 @@ .\} .\" mysql.server: service-startup-timeout option .\" service-startup-timeout option: mysql.server -\fB\-\-service\-startup\-timeout=\fR\fB\fIfile_name\fR\fR +\fB\-\-service\-startup\-timeout=\fR\fB\fIseconds\fR\fR .sp How long in seconds to wait for confirmation of server startup\&. If the server does not start within this time, \fBmysql\&.server\fR exits with an error\&. The default value is 900\&. A value of 0 means not to wait at all for startup\&. Negative values mean to wait forever (no timeout)\&. .RE -.sp -.RS 4 -.ie n \{\ -\h'-04'\(bu\h'+03'\c -.\} -.el \{\ -.sp -1 -.IP \(bu 2.3 -.\} -.\" mysql.server: use-mysqld_safe option -.\" use-mysqld_safe option: mysql.server -\fB\-\-use\-mysqld_safe\fR -.sp -Use -\fBmysqld_safe\fR -to start the server\&. This is the default\&. -.RE -.sp -.RS 4 -.ie n \{\ -\h'-04'\(bu\h'+03'\c -.\} -.el \{\ -.sp -1 -.IP \(bu 2.3 -.\} -.\" mysql.server: user option -.\" user option: mysql.server -\fB\-\-user=\fR\fB\fIuser_name\fR\fR -.sp -The login user name to use for running -\fBmysqld\fR\&. -.RE .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysql_setpermission.1 mysql-5.5-5.5.43/man/mysql_setpermission.1 --- mysql-5.5-5.5.35+dfsg/man/mysql_setpermission.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysql_setpermission.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysql_setpermission\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQL_SETPERMISSI" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQL_SETPERMISSI" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -43,7 +43,7 @@ and DBD::mysql Perl modules be installed (see -Section\ \&2.14, \(lqPerl Installation Notes\(rq)\&. +Section\ \&2.13, \(lqPerl Installation Notes\(rq)\&. .PP Invoke \fBmysql_setpermission\fR @@ -172,7 +172,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysqlshow.1 mysql-5.5-5.5.43/man/mysqlshow.1 --- mysql-5.5-5.5.35+dfsg/man/mysqlshow.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysqlshow.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysqlshow\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQLSHOW\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQLSHOW\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -125,10 +125,8 @@ [mysqlshow] and [client] -groups of an option file\&. -\fBmysqlshow\fR -also supports the options for processing option files described at -Section\ \&4.2.3.4, \(lqCommand-Line Options that Affect Option-File Handling\(rq\&. +groups of an option file\&. For information about option files used by MySQL programs, see +Section\ \&4.2.6, \(lqUsing Option Files\(rq\&. .sp .RS 4 .ie n \{\ @@ -158,7 +156,7 @@ .\" bind-address option: mysqlshow \fB\-\-bind\-address=\fR\fB\fIip_address\fR\fR .sp -On a computer having multiple network interfaces, this option can be used to select which interface is employed when connecting to the MySQL server\&. +On a computer having multiple network interfaces, use this option to select which interface to use for connecting to the MySQL server\&. .sp This option is supported only in the version of \fBmysqlshow\fR @@ -229,8 +227,8 @@ Write a debugging log\&. A typical \fIdebug_options\fR string is -\*(Aqd:t:o,\fIfile_name\fR\*(Aq\&. The default is -\*(Aqd:t:o\*(Aq\&. +d:t:o,\fIfile_name\fR\&. The default is +d:t:o\&. .RE .sp .RS 4 @@ -293,7 +291,7 @@ .\" default-auth option: mysqlshow \fB\-\-default\-auth=\fR\fB\fIplugin\fR\fR .sp -The client\-side authentication plugin to use\&. See +A hint about the client\-side authentication plugin to use\&. See Section\ \&6.3.6, \(lqPluggable Authentication\(rq\&. .sp This option was added in MySQL 5\&.5\&.10\&. @@ -307,6 +305,70 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqlshow: defaults-extra-file option +.\" defaults-extra-file option: mysqlshow +\fB\-\-defaults\-extra\-file=\fR\fB\fIfile_name\fR\fR +.sp +Read this option file after the global option file but (on Unix) before the user option file\&. If the file does not exist or is otherwise inaccessible, an error occurs\&. Before MySQL 5\&.5\&.8, +\fIfile_name\fR +must be the full path name to the file\&. As of MySQL 5\&.5\&.8, the name is interpreted relative to the current directory if given as a relative path name\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysqlshow: defaults-file option +.\" defaults-file option: mysqlshow +\fB\-\-defaults\-file=\fR\fB\fIfile_name\fR\fR +.sp +Use only the given option file\&. If the file does not exist or is otherwise inaccessible, an error occurs\&. Before MySQL 5\&.5\&.8, +\fIfile_name\fR +must be the full path name to the file\&. As of MySQL 5\&.5\&.8, the name is interpreted relative to the current directory if given as a relative path name\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysqlshow: defaults-group-suffix option +.\" defaults-group-suffix option: mysqlshow +\fB\-\-defaults\-group\-suffix=\fR\fB\fIstr\fR\fR +.sp +Read not only the usual option groups, but also groups with the usual names and a suffix of +\fIstr\fR\&. For example, +\fBmysqlshow\fR +normally reads the +[client] +and +[mysqlshow] +groups\&. If the +\fB\-\-defaults\-group\-suffix=_other\fR +option is given, +\fBmysqlshow\fR +also reads the +[client_other] +and +[mysqlshow_other] +groups\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqlshow: host option .\" host option: mysqlshow \fB\-\-host=\fR\fB\fIhost_name\fR\fR, @@ -339,6 +401,23 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqlshow: no-defaults option +.\" no-defaults option: mysqlshow +\fB\-\-no\-defaults\fR +.sp +Do not read any option files\&. If program startup fails due to reading unknown options from an option file, +\fB\-\-no\-defaults\fR +can be used to prevent them from being read\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqlshow: password option .\" password option: mysqlshow \fB\-\-password[=\fR\fB\fIpassword\fR\fR\fB]\fR, @@ -422,6 +501,21 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqlshow: print-defaults option +.\" print-defaults option: mysqlshow +\fB\-\-print\-defaults\fR +.sp +Print the program name and all options that it gets from option files\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqlshow: protocol option .\" protocol option: mysqlshow \fB\-\-protocol={TCP|SOCKET|PIPE|MEMORY}\fR @@ -438,6 +532,26 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqlshow: shared-memory-base-name option +.\" shared-memory-base-name option: mysqlshow +\fB\-\-shared\-memory\-base\-name=\fR\fB\fIname\fR\fR +.sp +On Windows, the shared\-memory name to use, for connections made using shared memory to a local server\&. The default value is +MYSQL\&. The shared\-memory name is case sensitive\&. +.sp +The server must be started with the +\fB\-\-shared\-memory\fR +option to enable shared\-memory connections\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqlshow: show-table-type option .\" show-table-type option: mysqlshow \fB\-\-show\-table\-type\fR, @@ -482,7 +596,7 @@ Options that begin with \fB\-\-ssl\fR specify whether to connect to the server using SSL and indicate where to find SSL keys and certificates\&. See -Section\ \&6.3.8.4, \(lqSSL Command Options\(rq\&. +Section\ \&6.3.9.4, \(lqSSL Command Options\(rq\&. .RE .sp .RS 4 @@ -551,7 +665,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysqlslap.1 mysql-5.5-5.5.43/man/mysqlslap.1 --- mysql-5.5-5.5.35+dfsg/man/mysqlslap.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysqlslap.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysqlslap\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQLSLAP\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQLSLAP\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -162,10 +162,8 @@ [mysqlslap] and [client] -groups of an option file\&. -\fBmysqlslap\fR -also supports the options for processing option files described at -Section\ \&4.2.3.4, \(lqCommand-Line Options that Affect Option-File Handling\(rq\&. +groups of an option file\&. For information about option files used by MySQL programs, see +Section\ \&4.2.6, \(lqUsing Option Files\(rq\&. .sp .RS 4 .ie n \{\ @@ -466,8 +464,8 @@ Write a debugging log\&. A typical \fIdebug_options\fR string is -\*(Aqd:t:o,\fIfile_name\fR\*(Aq\&. The default is -\*(Aqd:t:o,/tmp/mysqlslap\&.trace\*(Aq\&. +d:t:o,\fIfile_name\fR\&. The default is +d:t:o,/tmp/mysqlslap\&.trace\&. .RE .sp .RS 4 @@ -513,7 +511,7 @@ .\" default-auth option: mysqlslap \fB\-\-default\-auth=\fR\fB\fIplugin\fR\fR .sp -The client\-side authentication plugin to use\&. See +A hint about the client\-side authentication plugin to use\&. See Section\ \&6.3.6, \(lqPluggable Authentication\(rq\&. .sp This option was added in MySQL 5\&.5\&.10\&. @@ -527,6 +525,70 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqlslap: defaults-extra-file option +.\" defaults-extra-file option: mysqlslap +\fB\-\-defaults\-extra\-file=\fR\fB\fIfile_name\fR\fR +.sp +Read this option file after the global option file but (on Unix) before the user option file\&. If the file does not exist or is otherwise inaccessible, an error occurs\&. Before MySQL 5\&.5\&.8, +\fIfile_name\fR +must be the full path name to the file\&. As of MySQL 5\&.5\&.8, the name is interpreted relative to the current directory if given as a relative path name\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysqlslap: defaults-file option +.\" defaults-file option: mysqlslap +\fB\-\-defaults\-file=\fR\fB\fIfile_name\fR\fR +.sp +Use only the given option file\&. If the file does not exist or is otherwise inaccessible, an error occurs\&. Before MySQL 5\&.5\&.8, +\fIfile_name\fR +must be the full path name to the file\&. As of MySQL 5\&.5\&.8, the name is interpreted relative to the current directory if given as a relative path name\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysqlslap: defaults-group-suffix option +.\" defaults-group-suffix option: mysqlslap +\fB\-\-defaults\-group\-suffix=\fR\fB\fIstr\fR\fR +.sp +Read not only the usual option groups, but also groups with the usual names and a suffix of +\fIstr\fR\&. For example, +\fBmysqlslap\fR +normally reads the +[client] +and +[mysqlslap] +groups\&. If the +\fB\-\-defaults\-group\-suffix=_other\fR +option is given, +\fBmysqlslap\fR +also reads the +[client_other] +and +[mysqlslap_other] +groups\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqlslap: delimiter option .\" delimiter option: mysqlslap \fB\-\-delimiter=\fR\fB\fIstr\fR\fR, @@ -567,7 +629,7 @@ Enable the mysql_clear_password cleartext authentication plugin\&. (See -Section\ \&6.3.6.6, \(lqThe Cleartext Client-Side Authentication Plugin\(rq\&.) This option was added in MySQL 5\&.5\&.27\&. +Section\ \&6.3.7.5, \(lqThe Cleartext Client-Side Authentication Plugin\(rq\&.) This option was added in MySQL 5\&.5\&.27\&. .RE .sp .RS 4 @@ -643,6 +705,23 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqlslap: no-defaults option +.\" no-defaults option: mysqlslap +\fB\-\-no\-defaults\fR +.sp +Do not read any option files\&. If program startup fails due to reading unknown options from an option file, +\fB\-\-no\-defaults\fR +can be used to prevent them from being read\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqlslap: number-char-cols option .\" number-char-cols option: mysqlslap \fB\-\-number\-char\-cols=\fR\fB\fIN\fR\fR, @@ -828,21 +907,6 @@ .sp -1 .IP \(bu 2.3 .\} -.\" mysqlslap: shared-memory-base-name option -.\" shared-memory-base-name option: mysqlslap -\fB\-\-shared\-memory\-base\-name=\fR\fB\fIname\fR\fR -.sp -On Windows, the shared\-memory name to use, for connections made using shared memory to a local server\&. This option applies only if the server supports shared\-memory connections\&. -.RE -.sp -.RS 4 -.ie n \{\ -\h'-04'\(bu\h'+03'\c -.\} -.el \{\ -.sp -1 -.IP \(bu 2.3 -.\} .\" mysqlslap: post-system option .\" post-system option: mysqlslap \fB\-\-post\-system=\fR\fB\fIstr\fR\fR @@ -892,6 +956,21 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqlslap: print-defaults option +.\" print-defaults option: mysqlslap +\fB\-\-print\-defaults\fR +.sp +Print the program name and all options that it gets from option files\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqlslap: protocol option .\" protocol option: mysqlslap \fB\-\-protocol={TCP|SOCKET|PIPE|MEMORY}\fR @@ -926,6 +1005,21 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysqlslap: shared-memory-base-name option +.\" shared-memory-base-name option: mysqlslap +\fB\-\-shared\-memory\-base\-name=\fR\fB\fIname\fR\fR +.sp +On Windows, the shared\-memory name to use, for connections made using shared memory to a local server\&. This option applies only if the server supports shared\-memory connections\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysqlslap: silent option .\" silent option: mysqlslap \fB\-\-silent\fR, @@ -966,7 +1060,7 @@ Options that begin with \fB\-\-ssl\fR specify whether to connect to the server using SSL and indicate where to find SSL keys and certificates\&. See -Section\ \&6.3.8.4, \(lqSSL Command Options\(rq\&. +Section\ \&6.3.9.4, \(lqSSL Command Options\(rq\&. .RE .sp .RS 4 @@ -1019,7 +1113,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysql-stress-test.pl.1 mysql-5.5-5.5.43/man/mysql-stress-test.pl.1 --- mysql-5.5-5.5.35+dfsg/man/mysql-stress-test.pl.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysql-stress-test.pl.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysql-stress-test.pl\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/25/2015 .\" Manual: MySQL Database System .\" Source: MySQL .\" Language: English .\" -.TH "\FBMYSQL\-STRESS\-TE" "1" "11/04/2013" "MySQL" "MySQL Database System" +.TH "\FBMYSQL\-STRESS\-TE" "1" "02/25/2015" "MySQL" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -498,7 +498,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 2006, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 2006, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysqltest.1 mysql-5.5-5.5.43/man/mysqltest.1 --- mysql-5.5-5.5.35+dfsg/man/mysqltest.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysqltest.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysqltest\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/25/2015 .\" Manual: MySQL Database System .\" Source: MySQL .\" Language: English .\" -.TH "\FBMYSQLTEST\FR" "1" "11/04/2013" "MySQL" "MySQL Database System" +.TH "\FBMYSQLTEST\FR" "1" "02/25/2015" "MySQL" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -909,7 +909,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 2006, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 2006, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP @@ -921,7 +921,7 @@ .IP " 1." 4 The SHA-256 Authentication Plugin .RS 4 -\%http://dev.mysql.com/doc/refman/5.6/en/sha256-authentication-plugin.html +\%http://dev.mysql.com/doc/refman/5.7/en/sha256-authentication-plugin.html .RE .SH "SEE ALSO" For more information, please refer to the MySQL Reference Manual, diff -Nru mysql-5.5-5.5.35+dfsg/man/mysqltest_embedded.1 mysql-5.5-5.5.43/man/mysqltest_embedded.1 --- mysql-5.5-5.5.35+dfsg/man/mysqltest_embedded.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysqltest_embedded.1 2015-02-27 08:30:42.000000000 +0000 @@ -1 +1 @@ -.so man-gpl-tmp2/mysqltest.1 +.so man/mysqltest.1 diff -Nru mysql-5.5-5.5.35+dfsg/man/mysql-test-run.pl.1 mysql-5.5-5.5.43/man/mysql-test-run.pl.1 --- mysql-5.5-5.5.35+dfsg/man/mysql-test-run.pl.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysql-test-run.pl.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysql-test-run.pl\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/25/2015 .\" Manual: MySQL Database System .\" Source: MySQL .\" Language: English .\" -.TH "\FBMYSQL\-TEST\-RUN\" "1" "11/04/2013" "MySQL" "MySQL Database System" +.TH "\FBMYSQL\-TEST\-RUN\" "1" "02/25/2015" "MySQL" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -1582,7 +1582,7 @@ was added in MySQL 5\&.1\&.45 as a more logical alternative to \fB\-\-build\-thread\fR\&. If both are used, \fB\-\-port\-base\fR -takes presedence\&. +takes precedence\&. .RE .sp .RS 4 @@ -1797,7 +1797,7 @@ .\" skip-ndb option: mysql-test-run.pl \fB\-\-skip\-ndb\fR .sp -Do not start NDB Cluster; skip Cluster test cases\&. From MySQL 5\&.1\&.52, this is the default and so this option does not do anything but is kept for backwards compatibility\&. +Do not start NDB Cluster; skip Cluster test cases\&. From MySQL 5\&.1\&.52, this is the default and so this option does not do anything but is kept for backward compatibility\&. .RE .sp .RS 4 @@ -2551,7 +2551,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 2006, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 2006, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysql_tzinfo_to_sql.1 mysql-5.5-5.5.43/man/mysql_tzinfo_to_sql.1 --- mysql-5.5-5.5.35+dfsg/man/mysql_tzinfo_to_sql.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysql_tzinfo_to_sql.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysql_tzinfo_to_sql\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQL_TZINFO_TO_S" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQL_TZINFO_TO_S" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -42,7 +42,7 @@ mysql database\&. It is used on systems that have a zoneinfo -database (the set of files describing time zones)\&. Examples of such systems are Linux, FreeBSD, Solaris, and Mac OS X\&. One likely location for these files is the +database (the set of files describing time zones)\&. Examples of such systems are Linux, FreeBSD, Solaris, and OS X\&. One likely location for these files is the /usr/share/zoneinfo directory (/usr/share/lib/zoneinfo on Solaris)\&. If your system does not have a zoneinfo database, you can use the downloadable package described in @@ -122,7 +122,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysql_upgrade.1 mysql-5.5-5.5.43/man/mysql_upgrade.1 --- mysql-5.5-5.5.35+dfsg/man/mysql_upgrade.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysql_upgrade.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysql_upgrade\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQL_UPGRADE\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQL_UPGRADE\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -42,14 +42,21 @@ \fBmysql_upgrade\fR also upgrades the system tables so that you can take advantage of new privileges or capabilities that might have been added\&. .PP -\fBmysql_upgrade\fR -should be executed each time you upgrade MySQL\&. -.PP If \fBmysql_upgrade\fR finds that a table has a possible incompatibility, it performs a table check and, if problems are found, attempts a table repair\&. If the table cannot be repaired, see -Section\ \&2.12.4, \(lqRebuilding or Repairing Tables or Indexes\(rq +Section\ \&2.11.4, \(lqRebuilding or Repairing Tables or Indexes\(rq for manual table repair strategies\&. +.PP +You should execute +\fBmysql_upgrade\fR +each time you upgrade MySQL\&. +.PP +If you install MySQL from RPM packages on Linux, you must install the server and client RPMs\&. +\fBmysql_upgrade\fR +is included in the server RPM but requires the client RPM because the latter includes +\fBmysqlcheck\fR\&. (See +Section\ \&2.5.1, \(lqInstalling MySQL on Linux Using RPM Packages\(rq\&.) .if n \{\ .sp .\} @@ -88,12 +95,12 @@ .PP Some upgrade incompatibilities may require special handling before you upgrade your MySQL installation and run \fBmysql_upgrade\fR\&. See -Section\ \&2.12.1, \(lqUpgrading MySQL\(rq, for instructions on determining whether any such incompatibilities apply to your installation and how to handle them\&. +Section\ \&2.11.1, \(lqUpgrading MySQL\(rq, for instructions on determining whether any such incompatibilities apply to your installation and how to handle them\&. .sp .5v .RE .PP To use -\fBmysql_upgrade\fR, make sure that the server is running, and then invoke it like this: +\fBmysql_upgrade\fR, make sure that the server is running\&. Then invoke it like this: .sp .if n \{\ .RS 4 @@ -108,6 +115,26 @@ After running \fBmysql_upgrade\fR, stop the server and restart it so that any changes made to the system tables take effect\&. .PP +If you have multiple MySQL server instances running, invoke +\fBmysql_upgrade\fR +with connection parameters appropriate for connecting to the desired server\&. For example, with servers running on the local host on parts 3306 through 3308, upgrade each of them by connecting to the appropriate port: +.sp +.if n \{\ +.RS 4 +.\} +.nf +shell> \fBmysql_upgrade \-\-protocol=tcp \-P 3306 [\fR\fB\fIother_options\fR\fR\fB]\fR +shell> \fBmysql_upgrade \-\-protocol=tcp \-P 3307 [\fR\fB\fIother_options\fR\fR\fB]\fR +shell> \fBmysql_upgrade \-\-protocol=tcp \-P 3308 [\fR\fB\fIother_options\fR\fR\fB]\fR +.fi +.if n \{\ +.RE +.\} +.PP +For local host connections on Unix, the +\fB\-\-protocol=tcp\fR +option forces a connection using TCP/IP rather than the Unix socket file\&. +.PP \fBmysql_upgrade\fR executes the following commands to check and repair tables and to upgrade the system tables: .sp @@ -115,9 +142,11 @@ .RS 4 .\} .nf -mysqlcheck \-\-all\-databases \-\-check\-upgrade \-\-auto\-repair -mysql < \fIfix_priv_tables\fR -mysqlcheck \-\-all\-databases \-\-check\-upgrade \-\-fix\-db\-names \-\-fix\-table\-names +mysqlcheck \-\-no\-defaults \-\-all\-databases + \-\-fix\-db\-names \-\-fix\-table\-names +mysqlcheck \-\-no\-defaults \-\-check\-upgrade \-\-all\-databases + \-\-auto\-repair +mysql < fix_priv_tables .fi .if n \{\ .RE @@ -133,6 +162,28 @@ .sp -1 .IP \(bu 2.3 .\} +\fBmysql_upgrade\fR +also adds +\fB\-\-write\-binlog\fR +or +\fB\-\-skip\-write\-binlog\fR +to the +\fBmysqlcheck\fR +commands, depending on whether the +\fB\-\-write\-binlog\fR +option was specified on the +\fBmysql_upgrade\fR +command\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} Because \fBmysql_upgrade\fR invokes @@ -189,12 +240,6 @@ \fB\-\-force\fR option\&. .PP -If you install MySQL from RPM packages on Linux, you must install the server and client RPMs\&. -\fBmysql_upgrade\fR -is included in the server RPM but requires the client RPM because the latter includes -\fBmysqlcheck\fR\&. (See -Section\ \&2.5.1, \(lqInstalling MySQL on Linux Using RPM Packages\(rq\&.) -.PP \fBmysql_upgrade\fR does not upgrade the contents of the help tables\&. For upgrade instructions, see Section\ \&5.1.10, \(lqServer-Side Help\(rq\&. @@ -204,13 +249,9 @@ [mysql_upgrade] and [client] -groups of an option file\&. Other options are passed to -\fBmysqlcheck\fR\&. For example, it might be necessary to specify the -\fB\-\-password[=\fR\fB\fIpassword\fR\fR\fB]\fR -option\&. -\fBmysql_upgrade\fR -also supports the options for processing option files described at -Section\ \&4.2.3.4, \(lqCommand-Line Options that Affect Option-File Handling\(rq\&. +groups of an option file\&. Unrecognized options are passed to +\fBmysqlcheck\fR\&. For information about option files, see +Section\ \&4.2.6, \(lqUsing Option Files\(rq\&. .sp .RS 4 .ie n \{\ @@ -237,7 +278,7 @@ .\} .\" mysql_upgrade: basedir option .\" basedir option: mysql_upgrade -\fB\-\-basedir=\fR\fB\fIpath\fR\fR +\fB\-\-basedir=\fR\fB\fIdir_name\fR\fR .sp The path to the MySQL installation directory\&. This option is accepted for backward compatibility but ignored\&. It is removed in MySQL 5\&.7\&. .RE @@ -250,9 +291,40 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysql_upgrade: character-sets-dir option +.\" character-sets-dir option: mysql_upgrade +\fB\-\-character\-sets\-dir=\fR\fB\fIpath\fR\fR +.sp +The directory where character sets are installed\&. See +Section\ \&10.5, \(lqCharacter Set Configuration\(rq\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysql_upgrade: compress option +.\" compress option: mysql_upgrade +\fB\-\-compress\fR +.sp +Compress all information sent between the client and the server if both support compression\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysql_upgrade: datadir option .\" datadir option: mysql_upgrade -\fB\-\-datadir=\fR\fB\fIpath\fR\fR +\fB\-\-datadir=\fR\fB\fIdir_name\fR\fR .sp The path to the data directory\&. This option is accepted for backward compatibility but ignored\&. It is removed in MySQL 5\&.7\&. .RE @@ -265,6 +337,26 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysql_upgrade: debug option +.\" debug option: mysql_upgrade +\fB\-\-debug[=\fR\fB\fIdebug_options\fR\fR\fB]\fR, +\fB\-# [\fR\fB\fIdebug_options\fR\fR\fB]\fR +.sp +Write a debugging log\&. A typical +\fIdebug_options\fR +string is +d:t:o,\fIfile_name\fR\&. The default is +d:t:O,/tmp/mysql_upgrade\&.trace\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysql_upgrade: debug-check option .\" debug-check option: mysql_upgrade \fB\-\-debug\-check\fR @@ -300,7 +392,7 @@ .\" default-auth option: mysql_upgrade \fB\-\-default\-auth=\fR\fB\fIplugin\fR\fR .sp -The client\-side authentication plugin to use\&. See +A hint about the client\-side authentication plugin to use\&. See Section\ \&6.3.6, \(lqPluggable Authentication\(rq\&. .sp This option was added in MySQL 5\&.5\&.10\&. @@ -314,15 +406,95 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysql_upgrade: default-character-set option +.\" default-character-set option: mysql_upgrade +\fB\-\-default\-character\-set=\fR\fB\fIcharset_name\fR\fR +.sp +Use +\fIcharset_name\fR +as the default character set\&. See +Section\ \&10.5, \(lqCharacter Set Configuration\(rq\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysql_upgrade: defaults-extra-file option +.\" defaults-extra-file option: mysql_upgrade +\fB\-\-defaults\-extra\-file=\fR\fB\fIfile_name\fR\fR +.sp +Read this option file after the global option file but (on Unix) before the user option file\&. If the file does not exist or is otherwise inaccessible, an error occurs\&. Before MySQL 5\&.5\&.8, +\fIfile_name\fR +must be the full path name to the file\&. As of MySQL 5\&.5\&.8, the name is interpreted relative to the current directory if given as a relative path name\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysql_upgrade: defaults-file option +.\" defaults-file option: mysql_upgrade +\fB\-\-defaults\-file=\fR\fB\fIfile_name\fR\fR +.sp +Use only the given option file\&. If the file does not exist or is otherwise inaccessible, an error occurs\&. Before MySQL 5\&.5\&.8, +\fIfile_name\fR +must be the full path name to the file\&. As of MySQL 5\&.5\&.8, the name is interpreted relative to the current directory if given as a relative path name\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysql_upgrade: defaults-group-suffix option +.\" defaults-group-suffix option: mysql_upgrade +\fB\-\-defaults\-group\-suffix=\fR\fB\fIstr\fR\fR +.sp +Read not only the usual option groups, but also groups with the usual names and a suffix of +\fIstr\fR\&. For example, +\fBmysql_upgrade\fR +normally reads the +[client] +and +[mysql_upgrade] +groups\&. If the +\fB\-\-defaults\-group\-suffix=_other\fR +option is given, +\fBmysql_upgrade\fR +also reads the +[client_other] +and +[mysql_upgrade_other] +groups\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysql_upgrade: force option .\" force option: mysql_upgrade \fB\-\-force\fR .sp Ignore the mysql_upgrade_info -file and force execution of -\fBmysqlcheck\fR -even if +file and force execution even if \fBmysql_upgrade\fR has already been executed for the current version of MySQL\&. .RE @@ -335,6 +507,84 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysql_upgrade: host option +.\" host option: mysql_upgrade +\fB\-\-host=\fR\fB\fIhost_name\fR\fR, +\fB\-h \fR\fB\fIhost_name\fR\fR +.sp +Connect to the MySQL server on the given host\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysql_upgrade: no-defaults option +.\" no-defaults option: mysql_upgrade +\fB\-\-no\-defaults\fR +.sp +Do not read any option files\&. If program startup fails due to reading unknown options from an option file, +\fB\-\-no\-defaults\fR +can be used to prevent them from being read\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysql_upgrade: password option +.\" password option: mysql_upgrade +\fB\-\-password[=\fR\fB\fIpassword\fR\fR\fB]\fR, +\fB\-p[\fR\fB\fIpassword\fR\fR\fB]\fR +.sp +The password to use when connecting to the server\&. If you use the short option form (\fB\-p\fR), you +\fIcannot\fR +have a space between the option and the password\&. If you omit the +\fIpassword\fR +value following the +\fB\-\-password\fR +or +\fB\-p\fR +option on the command line, +\fBmysql_upgrade\fR +prompts for one\&. +.sp +Specifying a password on the command line should be considered insecure\&. See +Section\ \&6.1.2.1, \(lqEnd-User Guidelines for Password Security\(rq\&. You can use an option file to avoid giving the password on the command line\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysql_upgrade: pipe option +.\" pipe option: mysql_upgrade +\fB\-\-pipe\fR, +\fB\-W\fR +.sp +On Windows, connect to the server using a named pipe\&. This option applies only if the server supports named\-pipe connections\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysql_upgrade: plugin-dir option .\" plugin-dir option: mysql_upgrade \fB\-\-plugin\-dir=\fR\fB\fIpath\fR\fR @@ -357,9 +607,111 @@ .sp -1 .IP \(bu 2.3 .\} +.\" mysql_upgrade: port option +.\" port option: mysql_upgrade +\fB\-\-port=\fR\fB\fIport_num\fR\fR, +\fB\-P \fR\fB\fIport_num\fR\fR +.sp +The TCP/IP port number to use for the connection\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysql_upgrade: print-defaults option +.\" print-defaults option: mysql_upgrade +\fB\-\-print\-defaults\fR +.sp +Print the program name and all options that it gets from option files\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysql_upgrade: protocol option +.\" protocol option: mysql_upgrade +\fB\-\-protocol={TCP|SOCKET|PIPE|MEMORY}\fR +.sp +The connection protocol to use for connecting to the server\&. It is useful when the other connection parameters normally would cause a protocol to be used other than the one you want\&. For details on the permissible values, see +Section\ \&4.2.2, \(lqConnecting to the MySQL Server\(rq\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysql_upgrade: shared-memory-base-name option +.\" shared-memory-base-name option: mysql_upgrade +\fB\-\-shared\-memory\-base\-name=\fR\fB\fIname\fR\fR +.sp +On Windows, the shared\-memory name to use, for connections made using shared memory to a local server\&. The default value is +MYSQL\&. The shared\-memory name is case sensitive\&. +.sp +The server must be started with the +\fB\-\-shared\-memory\fR +option to enable shared\-memory connections\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysql_upgrade: socket option +.\" socket option: mysql_upgrade +\fB\-\-socket=\fR\fB\fIpath\fR\fR, +\fB\-S \fR\fB\fIpath\fR\fR +.sp +For connections to +localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" mysql_upgrade: SSL options +.\" SSL options: mysql_upgrade +\fB\-\-ssl*\fR +.sp +Options that begin with +\fB\-\-ssl\fR +specify whether to connect to the server using SSL and indicate where to find SSL keys and certificates\&. See +Section\ \&6.3.9.4, \(lqSSL Command Options\(rq\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} .\" mysql_upgrade: tmpdir option .\" tmpdir option: mysql_upgrade -\fB\-\-tmpdir=\fR\fB\fIpath\fR\fR, +\fB\-\-tmpdir=\fR\fB\fIdir_name\fR\fR, \fB\-t \fR\fB\fIpath\fR\fR .sp The path name of the directory to use for creating temporary files\&. @@ -456,7 +808,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysql_waitpid.1 mysql-5.5-5.5.43/man/mysql_waitpid.1 --- mysql-5.5-5.5.35+dfsg/man/mysql_waitpid.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysql_waitpid.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysql_waitpid\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQL_WAITPID\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQL_WAITPID\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -129,7 +129,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/mysql_zap.1 mysql-5.5-5.5.43/man/mysql_zap.1 --- mysql-5.5-5.5.35+dfsg/man/mysql_zap.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/mysql_zap.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBmysql_zap\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBMYSQL_ZAP\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBMYSQL_ZAP\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -125,7 +125,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/ndb_blob_tool.1 mysql-5.5-5.5.43/man/ndb_blob_tool.1 --- mysql-5.5-5.5.35+dfsg/man/ndb_blob_tool.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndb_blob_tool.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndb_blob_tool\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDB_BLOB_TOOL\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDB_BLOB_TOOL\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -94,7 +94,7 @@ .nr an-no-space-flag 1 .nr an-break-flag 1 .br -.B Table\ \&17.14.\ \&ndb_blob_tool Options and Variables: MySQL Cluster NDB 7.2 +.B Table\ \&18.73.\ \& This table describes command-line options for the ndb_blob_tool program .TS allbox tab(:); lB lB lB. @@ -103,7 +103,7 @@ T}:T{ Description T}:T{ -Added / Removed +Added or Removed T} .T& l l l @@ -118,7 +118,7 @@ Check for orphan blob parts T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -126,10 +126,10 @@ .PP -d T}:T{ -Database to find the table in\&. +Database to find the table in. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -138,7 +138,7 @@ Delete orphan blob parts T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -147,7 +147,7 @@ Write orphan keys to specified file T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -158,7 +158,7 @@ Verbose output T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} .TE .sp 1 @@ -177,8 +177,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -186,11 +185,8 @@ \-\-check\-orphans T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -220,9 +216,7 @@ .TS allbox tab(:); l l s s -l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -230,16 +224,8 @@ \-\-database=db_name T} T{ -\ \& -T}:T{ -\-d -T} -T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -268,8 +254,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -277,11 +262,8 @@ \-\-delete\-orphans T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -310,8 +292,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -319,11 +300,8 @@ \-\-dump\-file=file T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ file name @@ -353,9 +331,7 @@ .TS allbox tab(:); l l s s -l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -363,16 +339,8 @@ \-\-verbose T} T{ -\ \& -T}:T{ -\-v -T} -T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -386,8 +354,7 @@ .sp 1 Provide extra information in the tool\*(Aqs output regarding its progress\&. .RE - Example -.PP +Example.PP First we create an NDB table in the @@ -479,11 +446,11 @@ column parts are created by NDB for this column\&. See -Section\ \&11.6, \(lqData Type Storage Requirements\(rq, for more information\&. +Section\ \&11.7, \(lqData Type Storage Requirements\(rq, for more information\&. .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/ndb-common-options.1 mysql-5.5-5.5.43/man/ndb-common-options.1 --- mysql-5.5-5.5.35+dfsg/man/ndb-common-options.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndb-common-options.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: Options Common to MySQL Cluster Programs .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "OPTIONS COMMON TO MY" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "OPTIONS COMMON TO MY" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -97,7 +97,7 @@ .nr an-no-space-flag 1 .nr an-break-flag 1 .br -.B Table\ \&17.29.\ \&Common MySQL Cluster Program Options and Variables: MySQL Cluster NDB 7.2 +.B Table\ \&18.88.\ \& This table describes command-line options common to all MySQL Cluster programs .TS allbox tab(:); lB lB lB. @@ -106,7 +106,7 @@ T}:T{ Description T}:T{ -Added / Removed +Added or Removed T} .T& l l l @@ -129,7 +129,7 @@ Display help message and exit T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -139,22 +139,22 @@ .PP -c T}:T{ -Set connection string for connecting to ndb_mgmd\&. Syntax: - [nodeid=;][host=][:]\&. - Overrides entries specified in NDB_CONNECTSTRING or my\&.cnf\&. +Set connection string for connecting to ndb_mgmd. Syntax: + [nodeid=;][host=][:]. + Overrides entries specified in NDB_CONNECTSTRING or my.cnf. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --ndb-mgmd-host=host[:port] T}:T{ -Set the host (and port, if desired) for connecting to the management - server +Set the host (and port, if desired) for connecting to management + server T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -163,7 +163,7 @@ Set node id for this node T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -172,26 +172,26 @@ Select nodes for transactions in a more optimal way T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --character-sets-dir=path T}:T{ -Directory where character sets are +Directory where character sets are installed T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --debug=options T}:T{ -Enable output from debug calls\&. Can be used only for versions compiled - with debugging enabled +Enable output from debug calls. Can be used only for versions + compiled with debugging enabled T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -200,7 +200,7 @@ Write core on errors (defaults to TRUE in debug builds) T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -211,16 +211,16 @@ Output version information and exit T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} .TE .sp 1 .PP For options specific to individual MySQL Cluster programs, see -Section\ \&17.4, \(lqMySQL Cluster Programs\(rq\&. +Section\ \&18.4, \(lqMySQL Cluster Programs\(rq\&. .PP See -Section\ \&17.3.4.2, \(lqMySQL Server Options for MySQL Cluster\(rq, for +Section\ \&18.3.4.2, \(lqMySQL Server Options for MySQL Cluster\(rq, for \fBmysqld\fR options relating to MySQL Cluster\&. .sp @@ -241,7 +241,6 @@ .TS allbox tab(:); l l s s -l l s s l l s s. T{ \fBCommand\-Line Format\fR @@ -253,11 +252,6 @@ T}:T{ \-\-usage T} -T{ -\ \& -T}:T{ -\-? -T} .TE .sp 1 Prints a short list with descriptions of the available command options\&. @@ -277,8 +271,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -286,11 +279,8 @@ \-\-character\-sets\-dir=path T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ file name @@ -322,9 +312,7 @@ allbox tab(:); l l s s l l s s -l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -337,16 +325,8 @@ \-\-connect\-string=connectstring T} T{ -\ \& -T}:T{ -\-c -T} -T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -371,7 +351,7 @@ .\} .sp For more information, see -Section\ \&17.3.2.3, \(lqMySQL Cluster Connection Strings\(rq\&. +Section\ \&18.3.2.3, \(lqMySQL Cluster Connection Strings\(rq\&. .RE .sp .RS 4 @@ -387,8 +367,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -396,11 +375,8 @@ \-\-core\-file T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -440,8 +416,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -449,11 +424,8 @@ \-\-debug=options T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -483,9 +455,7 @@ .TS allbox tab(:); l l s s -l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -493,16 +463,8 @@ \-\-ndb\-mgmd\-host=host[:port] T} T{ -\fBOption\-File Format\fR -T}:T{ -ndb\-mgmd\-host -T} -T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -532,8 +494,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -541,11 +502,8 @@ \-\-ndb\-nodeid=# T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ numeric @@ -559,7 +517,7 @@ .sp 1 Sets this node\*(Aqs MySQL Cluster node ID\&. \fIThe range of permitted values depends on the node\*(Aqs type (data, management, or API) and the MySQL Cluster software version\fR\&. See -Section\ \&17.1.6.2, \(lqLimits and Differences of MySQL Cluster from Standard MySQL Limits\(rq, for more information\&. +Section\ \&18.1.6.2, \(lqLimits and Differences of MySQL Cluster from Standard MySQL Limits\(rq, for more information\&. .RE .sp .RS 4 @@ -575,8 +533,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -584,11 +541,8 @@ \-\-ndb\-optimized\-node\-selection T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -617,29 +571,23 @@ \fB\-V\fR .TS allbox tab(:); -l l s s l l s s. T{ \fBCommand\-Line Format\fR T}:T{ \-\-version T} -T{ -\ \& -T}:T{ -\-V -T} .TE .sp 1 Prints the MySQL Cluster version number of the executable\&. The version number is relevant because not all versions can be used together, and the MySQL Cluster startup process verifies that the versions of the binaries being used can co\-exist in the same cluster\&. This is also important when performing an online (rolling) software upgrade or downgrade of MySQL Cluster\&. .sp See -Section\ \&17.5.5, \(lqPerforming a Rolling Restart of a MySQL Cluster\(rq), for more information\&. +Section\ \&18.5.5, \(lqPerforming a Rolling Restart of a MySQL Cluster\(rq), for more information\&. .RE .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/ndb_config.1 mysql-5.5-5.5.43/man/ndb_config.1 --- mysql-5.5-5.5.35+dfsg/man/ndb_config.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndb_config.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndb_config\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDB_CONFIG\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDB_CONFIG\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -69,7 +69,7 @@ .nr an-no-space-flag 1 .nr an-break-flag 1 .br -.B Table\ \&17.15.\ \&ndb_config Options and Variables: MySQL Cluster NDB 7.2 +.B Table\ \&18.74.\ \& This table describes command-line options for the ndb_config program .TS allbox tab(:); lB lB lB. @@ -78,7 +78,7 @@ T}:T{ Description T}:T{ -Added / Removed +Added or Removed T} .T& l l l @@ -100,20 +100,20 @@ .PP --nodes T}:T{ -Print node information (DB section) only\&. +Print node information (DB section) only. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --connections T}:T{ -Print CONNECTIONS section information only\&. Cannot be used with \-\-nodes - or \-\-system option\&. +Print CONNECTIONS section information only. Cannot be used with + --nodes or --system option. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -124,7 +124,7 @@ One or more query options (attributes) T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -133,7 +133,7 @@ Specify host T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -142,7 +142,7 @@ Specify node type T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -153,7 +153,7 @@ Get configuration of node with this ID T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -164,7 +164,7 @@ Field separator T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -175,76 +175,76 @@ Row separator T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --config-file=path T}:T{ -Set the path to config\&.ini file +Set the path to config.ini file T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --mycnf T}:T{ -Read configuration data from my\&.cnf file +Read configuration data from my.cnf file T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP -c T}:T{ -Short form for \-\-ndb\-connectstring +Short form for --ndb-connectstring T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --configinfo T}:T{ -Dumps information about all NDB configuration parameters in text format - with default, maximum, and minimum values\&. Use with \-\-xml to - obtain XML output\&. +Dumps information about all NDB configuration parameters in text + format with default, maximum, and minimum values. Use with --xml + to obtain XML output. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --configinfo --xml T}:T{ -Use \-\-xml with \-\-configinfo to obtain a dump of all NDB configuration - parameters in XML format with default, maximum, and minimum - values\&. +Use --xml with --configinfo to obtain a dump of all NDB + configuration parameters in XML format with default, maximum, and + minimum values. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --system T}:T{ -Print SYSTEM section information only\&. Cannot be used with \-\-nodes or - \-\-connections option\&. +Print SYSTEM section information only. Cannot be used with --nodes + or --connections option. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --config_from_node=# T}:T{ -Obtain configuration data from the node having this ID (must be a data - node)\&. +Obtain configuration data from the node having this ID (must be a + data node). T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} .TE .sp 1 @@ -265,7 +265,6 @@ .TS allbox tab(:); l l s s -l l s s l l s s. T{ \fBCommand\-Line Format\fR @@ -277,11 +276,6 @@ T}:T{ \-\-usage T} -T{ -\ \& -T}:T{ -\-? -T} .TE .sp 1 Causes @@ -303,7 +297,7 @@ .TS allbox tab(:); l l s s -l l s s +l l l s ^ l l s ^ l l s ^ l l s. @@ -313,11 +307,8 @@ \-\-config_from_node=# T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ numeric @@ -328,9 +319,14 @@ none T} :T{ -\fBRange\fR +\fBMin Value\fR +T}:T{ +1 +T} +:T{ +\fBMax Value\fR T}:T{ -1 \&.\&. 48 +48 T} .TE .sp 1 @@ -355,18 +351,12 @@ \fB\-V\fR .TS allbox tab(:); -l l s s l l s s. T{ \fBCommand\-Line Format\fR T}:T{ \-\-version T} -T{ -\ \& -T}:T{ -\-V -T} .TE .sp 1 Causes @@ -390,9 +380,7 @@ allbox tab(:); l l s s l l s s -l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -405,16 +393,8 @@ \-\-connect\-string=connectstring T} T{ -\ \& -T}:T{ -\-c -T} -T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -427,7 +407,7 @@ .TE .sp 1 Specifies the connection string to use in connecting to the management server\&. The format for the connection string is the same as described in -Section\ \&17.3.2.3, \(lqMySQL Cluster Connection Strings\(rq, and defaults to +Section\ \&18.3.2.3, \(lqMySQL Cluster Connection Strings\(rq, and defaults to localhost:1186\&. .RE .sp @@ -445,8 +425,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -454,11 +433,8 @@ \-\-config\-file=path T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ file name @@ -488,8 +464,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -497,11 +472,8 @@ \-\-mycnf T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -534,9 +506,7 @@ .TS allbox tab(:); l l s s -l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -544,16 +514,8 @@ \-\-query=string T} T{ -\ \& -T}:T{ -\-q -T} -T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -611,8 +573,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -620,11 +581,8 @@ \-\-host=name T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -686,8 +644,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -695,11 +652,8 @@ \-\-ndb\-nodeid=# T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ numeric @@ -730,8 +684,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -739,11 +692,8 @@ \-\-nodes T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -779,8 +729,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -788,11 +737,8 @@ \-\-connections T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -828,8 +774,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -837,11 +782,8 @@ \-\-system T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -880,8 +822,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s ^ lt l s ^ ^ l s @@ -892,11 +833,8 @@ \-\-type=name T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ enumeration @@ -904,6 +842,7 @@ :T{ \fBDefault\fR T}:T{ +[none] T} :T{ \fBValid Values\fR @@ -941,9 +880,7 @@ .TS allbox tab(:); l l s s -l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -951,16 +888,8 @@ \-\-fields=string T} T{ -\ \& -T}:T{ -\-f -T} -T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -1013,9 +942,7 @@ .TS allbox tab(:); l l s s -l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -1023,16 +950,8 @@ \-\-rows=string T} T{ -\ \& -T}:T{ -\-r -T} -T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -1192,8 +1111,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -1201,11 +1119,8 @@ \-\-configinfo \-\-xml T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -1229,7 +1144,7 @@ .\} .nf shell> \fBndb_config \-\-configinfo \-\-xml\fR -
@@ -1383,7 +1298,7 @@ \fB\-\-configinfo\fR serves no purpose\&. .RE - Examples +Examples .sp .RS 4 .ie n \{\ @@ -1520,7 +1435,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/ndb_cpcd.1 mysql-5.5-5.5.43/man/ndb_cpcd.1 --- mysql-5.5-5.5.35+dfsg/man/ndb_cpcd.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndb_cpcd.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndb_cpcd\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDB_CPCD\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDB_CPCD\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -39,7 +39,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/ndbd.8 mysql-5.5-5.5.43/man/ndbd.8 --- mysql-5.5-5.5.35+dfsg/man/ndbd.8 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndbd.8 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndbd\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDBD\FR" "8" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDBD\FR" "8" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -59,7 +59,7 @@ .nr an-no-space-flag 1 .nr an-break-flag 1 .br -.B Table\ \&17.10.\ \&ndbd Options and Variables: MySQL Cluster NDB 7.2 +.B Table\ \&18.69.\ \& This table describes command-line options for the ndbd program .TS allbox tab(:); lB lB lB. @@ -68,7 +68,7 @@ T}:T{ Description T}:T{ -Added / Removed +Added or Removed T} .T& l l l @@ -87,11 +87,11 @@ .PP --initial T}:T{ -Perform initial start of ndbd, including cleaning the file system\&. - Consult the documentation before using this option +Perform initial start of ndbd, including cleaning the file system. + Consult the documentation before using this option T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -99,11 +99,11 @@ .PP -n T}:T{ -Don\*(Aqt start ndbd immediately; ndbd waits for command to start from - ndb_mgmd +Don't start ndbd immediately; ndbd waits for command to start + from ndb_mgmd T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -111,10 +111,10 @@ .PP -d T}:T{ -Start ndbd as daemon (default); override with \-\-nodaemon +Start ndbd as daemon (default); override with --nodaemon T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -123,36 +123,36 @@ Do not start ndbd as daemon; provided for testing purposes T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --foreground T}:T{ Run ndbd in foreground, provided for debugging purposes (implies - \-\-nodaemon) + --nodaemon) T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --nowait-nodes=list T}:T{ -Do not wait for these data nodes to start (takes comma\-separated list of - node IDs)\&. Also requires \-\-ndb\-nodeid to be used\&. +Do not wait for these data nodes to start (takes comma-separated + list of node IDs). Also requires --ndb-nodeid to be used. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --initial-start T}:T{ -Perform partial initial start (requires \-\-nowait\-nodes) +Perform partial initial start (requires --nowait-nodes) T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -161,46 +161,47 @@ Local bind address T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --install[=name] T}:T{ -Used to install the data node process as a Windows service\&. Does not - apply on non\-Windows platforms\&. +Used to install the data node process as a Windows service. Does + not apply on non-Windows platforms. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --remove[=name] T}:T{ -Used to remove a data node process that was previously installed as a - Windows service\&. Does not apply on non\-Windows platforms\&. +Used to remove a data node process that was previously installed + as a Windows service. Does not apply on non-Windows platforms. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --connect-retries=# T}:T{ -Number of times to try contacting the management server; set to \-1 to - keep trying indefinitely +Number of times to try contacting the management server; set to -1 + to keep trying indefinitely T}:T{ .PP -ADDED: NDB 7\&.2\&.9 +ADDED: NDB 7.2.9 T} T{ .PP --connect-delay=# T}:T{ -Time to wait between attempts to contact a management server, in seconds +Time to wait between attempts to contact a management server, in + seconds T}:T{ .PP -ADDED: NDB 7\&.2\&.9 +ADDED: NDB 7.2.9 T} .TE .sp 1 @@ -237,8 +238,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -246,11 +246,8 @@ \-\-bind\-address=name T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -279,9 +276,7 @@ .TS allbox tab(:); l l s s -l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -289,16 +284,8 @@ \-\-daemon T} T{ -\ \& -T}:T{ -\-d -T} -T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -337,8 +324,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -346,11 +332,8 @@ \-\-nodaemon T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -389,8 +372,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -398,11 +380,8 @@ \-\-foreground T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -443,8 +422,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -452,11 +430,8 @@ \-\-initial T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -556,7 +531,7 @@ .IP \(bu 2.3 .\} MySQL Cluster Disk Data files (see -Section\ \&17.5.12, \(lqMySQL Cluster Disk Data Tables\(rq)\&. +Section\ \&18.5.12, \(lqMySQL Cluster Disk Data Tables\(rq)\&. .RE .sp This option also has no effect on recovery of data by a data node that is just starting (or restarting) from data nodes that are already running\&. This recovery of data occurs automatically, and requires no user intervention in a MySQL Cluster that is running normally\&. @@ -581,8 +556,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -590,11 +564,8 @@ \-\-initial\-start T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -660,8 +631,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -669,11 +639,8 @@ \-\-nowait\-nodes=list T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -718,9 +685,7 @@ .TS allbox tab(:); l l s s -l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -728,16 +693,8 @@ \-\-nostart T} T{ -\ \& -T}:T{ -\-n -T} -T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -756,7 +713,7 @@ connects to the management server, obtains configuration data from it, and initializes communication objects\&. However, it does not actually start the execution engine until specifically requested to do so by the management server\&. This can be accomplished by issuing the proper START command in the management client (see -Section\ \&17.5.2, \(lqCommands in the MySQL Cluster Management Client\(rq)\&. +Section\ \&18.5.2, \(lqCommands in the MySQL Cluster Management Client\(rq)\&. .RE .sp .RS 4 @@ -774,7 +731,7 @@ allbox tab(:); l l s s l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -782,11 +739,13 @@ \-\-install[=name] T} T{ -\ \& +\fBPlatform Specific\fR T}:T{ -\fBPermitted Values\fR +Windows T} -:T{ +T{ +\fBPermitted Values\fR +T}:T{ \fBType\fR T}:T{ string @@ -842,7 +801,7 @@ allbox tab(:); l l s s l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -850,11 +809,13 @@ \-\-remove[=name] T} T{ -\ \& +\fBPlatform Specific\fR T}:T{ -\fBPermitted Values\fR +Windows T} -:T{ +T{ +\fBPermitted Values\fR +T}:T{ \fBType\fR T}:T{ string @@ -891,14 +852,14 @@ allbox tab(:); l l s s l l s s -l l s s +l l l s ^ l l s ^ l l s ^ l l s. T{ \fBIntroduced\fR T}:T{ -5\&.5\&.27\-ndb\-7\&.2\&.9 +5\&.5\&.28\-ndb\-7\&.2\&.9 T} T{ \fBCommand\-Line Format\fR @@ -906,11 +867,8 @@ \-\-connect\-retries=# T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ numeric @@ -921,9 +879,14 @@ 12 T} :T{ -\fBRange\fR +\fBMin Value\fR T}:T{ -\-1 \&.\&. 65535 +\-1 +T} +:T{ +\fBMax Value\fR +T}:T{ +65535 T} .TE .sp 1 @@ -949,14 +912,14 @@ allbox tab(:); l l s s l l s s -l l s s +l l l s ^ l l s ^ l l s ^ l l s. T{ \fBIntroduced\fR T}:T{ -5\&.5\&.27\-ndb\-7\&.2\&.9 +5\&.5\&.28\-ndb\-7\&.2\&.9 T} T{ \fBCommand\-Line Format\fR @@ -964,11 +927,8 @@ \-\-connect\-delay=# T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ numeric @@ -979,9 +939,14 @@ 5 T} :T{ -\fBRange\fR +\fBMin Value\fR T}:T{ -0 \&.\&. 3600 +0 +T} +:T{ +\fBMax Value\fR +T}:T{ +3600 T} .TE .sp 1 @@ -1163,9 +1128,10 @@ .\} .PP See -Section\ \&17.3.2.3, \(lqMySQL Cluster Connection Strings\(rq, for additional information about this issue\&. -\fBndbd\fR(8), describes other options for -\fBndbd\fR\&. +Section\ \&18.3.2.3, \(lqMySQL Cluster Connection Strings\(rq, for additional information about this issue\&. +Options Common to MySQL Cluster Programs(1), describes other command\-line options which can be used with +\fBndbd\fR\&. For information about data node configuration parameters, see +Section\ \&18.3.2.6, \(lqDefining MySQL Cluster Data Nodes\(rq\&. .PP When \fBndbd\fR @@ -1189,11 +1155,11 @@ For a machine with many CPUs it is possible to use several \fBndbd\fR processes which belong to different node groups; however, such a configuration is still considered experimental and is not supported for MySQL 5\&.5 in a production setting\&. See -Section\ \&17.1.6, \(lqKnown Limitations of MySQL Cluster\(rq\&. +Section\ \&18.1.6, \(lqKnown Limitations of MySQL Cluster\(rq\&. .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/ndb_delete_all.1 mysql-5.5-5.5.43/man/ndb_delete_all.1 --- mysql-5.5-5.5.35+dfsg/man/ndb_delete_all.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndb_delete_all.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndb_delete_all\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDB_DELETE_ALL\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDB_DELETE_ALL\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -42,7 +42,7 @@ DELETE or even TRUNCATE TABLE\&. - Usage +Usage .sp .if n \{\ .RS 4 @@ -70,7 +70,7 @@ .nr an-no-space-flag 1 .nr an-break-flag 1 .br -.B Table\ \&17.16.\ \&ndb_delete_all Options and Variables: MySQL Cluster NDB 7.2 +.B Table\ \&18.75.\ \& This table describes command-line options for the ndb_delete_all program .TS allbox tab(:); lB lB lB. @@ -79,7 +79,7 @@ T}:T{ Description T}:T{ -Added / Removed +Added or Removed T} .T& l l l @@ -88,14 +88,14 @@ l l l. T{ .PP -\-\-database=dbname, +--database=dbname, .PP -\-d +-d T}:T{ Name of the database in which the table is found T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -103,28 +103,29 @@ .PP -t T}:T{ -Perform the delete in a single transaction (may run out of operations) +Perform the delete in a single transaction (may run out of + operations) T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP -\-\-tupscan +--tupscan T}:T{ Run tup scan T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP -\-\-diskscan +--diskscan T}:T{ Run disk scan T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} .TE .sp 1 @@ -162,7 +163,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/ndb_desc.1 mysql-5.5-5.5.43/man/ndb_desc.1 --- mysql-5.5-5.5.35+dfsg/man/ndb_desc.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndb_desc.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndb_desc\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDB_DESC\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDB_DESC\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -39,7 +39,7 @@ provides a detailed description of one or more NDB tables\&. - Usage +Usage .sp .if n \{\ .RS 4 @@ -63,8 +63,7 @@ .RE .\} .sp - Sample Output -.PP +Sample Output.PP MySQL table creation and population statements: .sp .if n \{\ @@ -239,7 +238,7 @@ .\} .PP (For more information on the statements just shown and the objects created by them, see -Section\ \&17.5.12.1, \(lqMySQL Cluster Disk Data Objects\(rq, as well as +Section\ \&18.5.12.1, \(lqMySQL Cluster Disk Data Objects\(rq, as well as Section\ \&13.1.14, \(lqCREATE LOGFILE GROUP Syntax\(rq, and Section\ \&13.1.18, \(lqCREATE TABLESPACE Syntax\(rq\&.) .PP @@ -334,7 +333,7 @@ .nr an-no-space-flag 1 .nr an-break-flag 1 .br -.B Table\ \&17.17.\ \&ndb_desc Options and Variables: MySQL Cluster NDB 7.2 +.B Table\ \&18.76.\ \& This table describes command-line options for the ndb_desc program .TS allbox tab(:); lB lB lB. @@ -343,7 +342,7 @@ T}:T{ Description T}:T{ -Added / Removed +Added or Removed T} .T& l l l @@ -359,11 +358,11 @@ .PP -b T}:T{ -Include partition information for BLOB tables in output\&. Requires that - the \-p option also be used +Include partition information for BLOB tables in output. Requires + that the -p option also be used T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -374,7 +373,7 @@ Name of database containing table T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -382,11 +381,11 @@ .PP -n T}:T{ -Include partition\-to\-data\-node mappings in output\&. Requires that the \-p - option also be used +Include partition-to-data-node mappings in output. Requires that + the -p option also be used T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -397,7 +396,7 @@ Display information about partitions T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -408,7 +407,7 @@ Number of times to retry the connection (once per second) T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -416,11 +415,11 @@ .PP -t T}:T{ -Specify the table in which to find an index\&. When this option is used, - \-p and \-n have no effect and are ignored\&. +Specify the table in which to find an index. When this option is + used, -p and -n have no effect and are ignored. T}:T{ .PP -ADDED: NDB 7\&.2\&.9 +ADDED: NDB 7.2.9 T} T{ .PP @@ -431,7 +430,7 @@ Use unqualified table names T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} .TE .sp 1 @@ -564,7 +563,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/ndbd_redo_log_reader.1 mysql-5.5-5.5.43/man/ndbd_redo_log_reader.1 --- mysql-5.5-5.5.35+dfsg/man/ndbd_redo_log_reader.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndbd_redo_log_reader.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndbd_redo_log_reader\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDBD_REDO_LOG_REA" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDBD_REDO_LOG_REA" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -55,7 +55,7 @@ .nr an-no-space-flag 1 .nr an-break-flag 1 .br -.B Table\ \&17.22.\ \&ndbd_redo_log_reader Options and Variables: MySQL Cluster NDB 7.2 +.B Table\ \&18.81.\ \& This table describes command-line options for the ndbd_redo_log_reader program .TS allbox tab(:); lB lB lB. @@ -64,7 +64,7 @@ T}:T{ Description T}:T{ -Added / Removed +Added or Removed T} .T& l l l @@ -77,7 +77,7 @@ Do not print records T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -86,7 +86,7 @@ Do not check records for errors T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -95,11 +95,11 @@ Print usage information T}:T{ .PP -ADDED: NDB 7\&.2\&.15 +ADDED: NDB 7.2.15 T} .TE .sp 1 - Usage +Usage .sp .if n \{\ .RS 4 @@ -116,7 +116,7 @@ ndb_\fI#\fR_fs/D\fI#\fR/LCP/\fI#\fR/T\fI#\fRF\fI#\fR\&.Data\&. In each case, the \fI#\fR represents a number (not necessarily the same number)\&. For more information, see -\m[blue]\fBMySQL Cluster Data Node FileSystemDir Files\fR\m[]\&\s-2\u[1]\d\s+2\&. +\m[blue]\fBMySQL Cluster Data Node File System Directory Files\fR\m[]\&\s-2\u[1]\d\s+2\&. .PP The name of the file to be read may be followed by one or more of the options listed here: .sp @@ -131,8 +131,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -140,11 +139,8 @@ \-noprint T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -170,8 +166,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -179,11 +174,8 @@ \-nocheck T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -213,7 +205,7 @@ T{ \fBIntroduced\fR T}:T{ -5\&.5\&.34\-ndb\-7\&.2\&.15 +5\&.5\&.35\-ndb\-7\&.2\&.15 T} T{ \fBCommand\-Line Format\fR @@ -239,7 +231,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP @@ -249,7 +241,7 @@ .sp .SH "NOTES" .IP " 1." 4 -MySQL Cluster Data Node FileSystemDir Files +MySQL Cluster Data Node File System Directory Files .RS 4 \%http://dev.mysql.com/doc/ndbapi/en/ndb-internals-ndbd-filesystemdir-files.html .RE diff -Nru mysql-5.5-5.5.35+dfsg/man/ndb_drop_index.1 mysql-5.5-5.5.43/man/ndb_drop_index.1 --- mysql-5.5-5.5.35+dfsg/man/ndb_drop_index.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndb_drop_index.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndb_drop_index\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDB_DROP_INDEX\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDB_DROP_INDEX\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -40,7 +40,7 @@ NDB table\&. \fIIt is recommended that you use this utility only as an example for writing NDB API applications\fR\(emsee the Warning later in this section for details\&. - Usage +Usage .sp .if n \{\ .RS 4 @@ -68,7 +68,7 @@ .nr an-no-space-flag 1 .nr an-break-flag 1 .br -.B Table\ \&17.18.\ \&ndb_drop_index Options and Variables: MySQL Cluster NDB 7.2 +.B Table\ \&18.77.\ \& This table describes command-line options for the ndb_drop_index program .TS allbox tab(:); lB lB lB. @@ -77,20 +77,20 @@ T}:T{ Description T}:T{ -Added / Removed +Added or Removed T} .T& l l l. T{ .PP -\-\-database=dbname, +--database=dbname, .PP -\-d +-d T}:T{ Name of the database in which the table is found T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} .TE .sp 1 @@ -123,7 +123,7 @@ Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with \-A Welcome to the MySQL monitor\&. Commands end with ; or \eg\&. -Your MySQL connection id is 7 to server version: 5\&.5\&.34\-ndb\-7\&.2\&.15 +Your MySQL connection id is 7 to server version: 5\&.5\&.42\-ndb\-7\&.2\&.20 Type \*(Aqhelp;\*(Aq or \*(Aq\eh\*(Aq for help\&. Type \*(Aq\ec\*(Aq to clear the buffer\&. mysql> \fBSHOW TABLES;\fR +\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ @@ -154,7 +154,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/ndb_drop_table.1 mysql-5.5-5.5.43/man/ndb_drop_table.1 --- mysql-5.5-5.5.35+dfsg/man/ndb_drop_table.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndb_drop_table.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndb_drop_table\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDB_DROP_TABLE\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDB_DROP_TABLE\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -45,7 +45,7 @@ statement on an NDB table\&. - Usage +Usage .sp .if n \{\ .RS 4 @@ -66,7 +66,7 @@ .nr an-no-space-flag 1 .nr an-break-flag 1 .br -.B Table\ \&17.19.\ \&ndb_drop_table Options and Variables: MySQL Cluster NDB 7.2 +.B Table\ \&18.78.\ \& This table describes command-line options for the ndb_drop_table program .TS allbox tab(:); lB lB lB. @@ -75,27 +75,27 @@ T}:T{ Description T}:T{ -Added / Removed +Added or Removed T} .T& l l l. T{ .PP -\-\-database=dbname, +--database=dbname, .PP -\-d +-d T}:T{ Name of the database in which the table is found T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} .TE .sp 1 .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/ndb_error_reporter.1 mysql-5.5-5.5.43/man/ndb_error_reporter.1 --- mysql-5.5-5.5.35+dfsg/man/ndb_error_reporter.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndb_error_reporter.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndb_error_reporter\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDB_ERROR_REPORTE" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDB_ERROR_REPORTE" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -58,7 +58,7 @@ .nr an-no-space-flag 1 .nr an-break-flag 1 .br -.B Table\ \&17.20.\ \&ndb_error_reporter Options and Variables: MySQL Cluster NDB 7.2 +.B Table\ \&18.79.\ \& This table describes command-line options for the ndb_error_reporter program .TS allbox tab(:); lB lB lB. @@ -67,7 +67,7 @@ T}:T{ Description T}:T{ -Added / Removed +Added or Removed T} .T& l l l @@ -78,42 +78,43 @@ .PP --connection-timeout=timeout T}:T{ -Number of seconds to wait when connecting to nodes before timing out\&. +Number of seconds to wait when connecting to nodes before timing + out. T}:T{ .PP -ADDED: NDB 7\&.2\&.14 +ADDED: NDB 7.2.14 T} T{ .PP --dry-scp T}:T{ -Disable scp with remote hosts; used only for testing\&. +Disable scp with remote hosts; used only for testing. T}:T{ .PP -ADDED: NDB 7\&.2\&.14 +ADDED: NDB 7.2.14 T} T{ .PP --fs T}:T{ -Include file system data in error report; can use a large amount of disk - space +Include file system data in error report; can use a large amount + of disk space T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --skip-nodegroup=nodegroup_id T}:T{ -Skip all nodes in the node group having this ID\&. +Skip all nodes in the node group having this ID. T}:T{ .PP -ADDED: NDB 7\&.2\&.14 +ADDED: NDB 7.2.14 T} .TE .sp 1 - Usage +Usage .sp .if n \{\ .RS 4 @@ -151,13 +152,12 @@ allbox tab(:); l l s s l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBIntroduced\fR T}:T{ -5\&.5\&.33\-ndb\-7\&.2\&.14 +5\&.5\&.34\-ndb\-7\&.2\&.14 T} T{ \fBCommand\-Line Format\fR @@ -165,11 +165,8 @@ \-\-connection\-timeout=timeout T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ integer @@ -198,13 +195,12 @@ allbox tab(:); l l s s l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBIntroduced\fR T}:T{ -5\&.5\&.33\-ndb\-7\&.2\&.14 +5\&.5\&.34\-ndb\-7\&.2\&.14 T} T{ \fBCommand\-Line Format\fR @@ -212,11 +208,8 @@ \-\-dry\-scp T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -246,8 +239,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -255,11 +247,8 @@ \-\-fs T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -292,13 +281,12 @@ allbox tab(:); l l s s l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBIntroduced\fR T}:T{ -5\&.5\&.33\-ndb\-7\&.2\&.14 +5\&.5\&.34\-ndb\-7\&.2\&.14 T} T{ \fBCommand\-Line Format\fR @@ -306,11 +294,8 @@ \-\-connection\-timeout=timeout T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ integer @@ -327,7 +312,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/ndb_index_stat.1 mysql-5.5-5.5.43/man/ndb_index_stat.1 --- mysql-5.5-5.5.35+dfsg/man/ndb_index_stat.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndb_index_stat.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndb_index_stat\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDB_INDEX_STAT\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDB_INDEX_STAT\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -36,9 +36,10 @@ .SH "DESCRIPTION" .PP \fBndb_index_stat\fR -\&.\&.\&. - Usage -.PP +provides per\-fragment statistical information about indexes on +NDB +tables\&. This includes cache version and age, number of index entries per partition, and memory consumption by indexes\&. +Usage.PP To obtain basic index statistics about a given NDB table, invoke @@ -66,22 +67,71 @@ in the test database: +.\" ndb_index_stat: interpreting output +.\" ndb_index_stat: example .sp .if n \{\ .RS 4 .\} .nf shell> \fBndb_index_stat \-d test mytable\fR -table:mytable index:PRIMARY fragCount:4 -sampleVersion:2 loadTime:1336751773 sampleCount:0 keyBytes:0 -query cache: valid:1 sampleCount:0 totalBytes:0 -times in ms: save: 12\&.380 sort: 0\&.001 +table:City index:PRIMARY fragCount:2 +sampleVersion:3 loadTime:1399585986 sampleCount:1994 keyBytes:7976 +query cache: valid:1 sampleCount:1994 totalBytes:27916 +times in ms: save: 7\&.133 sort: 1\&.974 sort per sample: 0\&.000 NDBT_ProgramExit: 0 \- OK .fi .if n \{\ .RE .\} .PP +sampleVersion +is the version number of the cache from which the statistics data is taken\&. Running +\fBndb_index_stat\fR +with the +\fB\-\-update\fR +option causes sampleVersion to be incremented\&. +.PP +loadTime +shows when the cache was last updated\&. This is expressed as seconds since the Unix Epoch\&. +.PP +sampleCount +is the number of index entries found per partition\&. You can estimate the total number of entries by multiplying this by the number of fragments (shown as +fragCount)\&. +.PP +sampleCount +can be compared with the cardinality of +SHOW INDEX +or +INFORMATION_SCHEMA\&.STATISTICS, although the latter two provide a view of the table as a whole, while +\fBndb_index_stat\fR +provides a per\-fragment average\&. +.PP +keyBytes +is the number of bytes used by the index\&. In this example, the primary key is an integer, which requires four bytes for each index, so +keyBytes +can be calculated in this case as shown here: +.sp +.if n \{\ +.RS 4 +.\} +.nf + keyBytes = sampleCount * (4 bytes per index) = 1994 * 4 = 7976 +.fi +.if n \{\ +.RE +.\} +.PP +This information can also be obtained using the corresponding column definitions from +INFORMATION_SCHEMA\&.COLUMNS +(this requires a MySQL Server and a MySQL client application)\&. +.PP +totalBytes +is the total memory consumed by all indexes on the table, in bytes\&. +.PP +Timings shown in the preceding examples are specific to each invocation of +\fBndb_index_stat\fR\&. +.PP The \fB\-\-verbose\fR option provides some additional output, as shown here: @@ -108,8 +158,7 @@ .RE .\} .sp - Options -.PP +Options.PP The following table includes options that are specific to the MySQL Cluster \fBndb_index_stat\fR utility\&. Additional descriptions are listed following the table\&. For options common to most MySQL Cluster programs (including @@ -120,7 +169,7 @@ .nr an-no-space-flag 1 .nr an-break-flag 1 .br -.B Table\ \&17.21.\ \&ndb_index_stat Options and Variables: MySQL Cluster NDB 7.2 +.B Table\ \&18.80.\ \& This table describes command-line options for the ndb_index_stat program .TS allbox tab(:); lB lB lB. @@ -129,7 +178,7 @@ T}:T{ Description T}:T{ -Added / Removed +Added or Removed T} .T& l l l @@ -148,146 +197,146 @@ l l l. T{ .PP -\-\-database=name, +--database=name, .PP -\-d +-d T}:T{ -Name of the database containing the table\&. +Name of the database containing the table. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP -\-\-delete +--delete T}:T{ -Delete index statistics for the given table, stopping any auto\-update - previously configured\&. +Delete index statistics for the given table, stopping any + auto-update previously configured. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP -\-\-update +--update T}:T{ -Update index statistics for the given table, restarting any auto\-update - previously configured\&. +Update index statistics for the given table, restarting any + auto-update previously configured. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP -\-\-dump +--dump T}:T{ -Print the query cache\&. +Print the query cache. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP -\-\-query=# +--query=# T}:T{ -Perform a number of random range queries on first key attr (must be int - unsigned)\&. +Perform a number of random range queries on first key attr (must + be int unsigned). T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP -\-\-sys\-drop +--sys-drop T}:T{ -Drop any statistics tables and events in NDB kernel (all statistics are - lost) +Drop any statistics tables and events in NDB kernel (all + statistics are lost) T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP -\-\-sys\-create +--sys-create T}:T{ -Create all statistics tables and events in NDB kernel, if none of them - already exist +Create all statistics tables and events in NDB kernel, if none of + them already exist T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP -\-\-sys\-create\-if\-not\-exist +--sys-create-if-not-exist T}:T{ Create any statistics tables and events in NDB kernel that do not - already exist\&. + already exist. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP -\-\-sys\-create\-if\-not\-valid +--sys-create-if-not-valid T}:T{ -Create any statistics tables or events that do not already exist in the - NDB kernel\&. after dropping any that are invalid\&. +Create any statistics tables or events that do not already exist + in the NDB kernel. after dropping any that are invalid. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP -\-\-sys\-check +--sys-check T}:T{ -Verify that NDB system index statistics and event tables exist\&. +Verify that NDB system index statistics and event tables exist. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP -\-\-sys\-skip\-tables +--sys-skip-tables T}:T{ -Do not apply sys\-* options to tables\&. +Do not apply sys-* options to tables. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP -\-\-sys\-skip\-events +--sys-skip-events T}:T{ -Do not apply sys\-* options to events\&. +Do not apply sys-* options to events. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP -\-\-verbose, +--verbose, .PP -\-v +-v T}:T{ Turn on verbose output T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP -\-\-loops=# +--loops=# T}:T{ -Set the number of times to perform a given command\&. Default is 0\&. +Set the number of times to perform a given command. Default is 0. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} .TE .sp 1 .PP -\fBndb_index_stat statistics options\fR. The following options are used to generate index statistics\&. They work with a given table and database\&. They cannot be mixed with -ndb_index_stat system options\&. +\fBndb_index_stat statistics options\fR. The following options are used to generate index statistics\&. They work with a given table and database\&. They cannot be mixed with system options (see +ndb_index_stat system options)\&. .sp .RS 4 .ie n \{\ @@ -304,8 +353,7 @@ .TS allbox tab(:); l l s s -l l s s -l l s s +l l l s ^ l l s ^ l l s ^ l l s. @@ -315,16 +363,8 @@ \-\-database=name T} T{ -\ \& -T}:T{ -\-d -T} -T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -335,9 +375,12 @@ [none] T} :T{ -\fBRange\fR +\fBMin Value\fR +T}:T{ +T} +:T{ +\fBMax Value\fR T}:T{ -\&.\&. T} .TE .sp 1 @@ -357,7 +400,7 @@ .TS allbox tab(:); l l s s -l l s s +l l l s ^ l l s ^ l l s ^ l l s. @@ -367,11 +410,8 @@ \-\-delete T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -379,12 +419,15 @@ :T{ \fBDefault\fR T}:T{ -true +false +T} +:T{ +\fBMin Value\fR +T}:T{ T} :T{ -\fBRange\fR +\fBMax Value\fR T}:T{ -\&.\&. T} .TE .sp 1 @@ -404,7 +447,7 @@ .TS allbox tab(:); l l s s -l l s s +l l l s ^ l l s ^ l l s ^ l l s. @@ -414,11 +457,8 @@ \-\-update T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -426,16 +466,19 @@ :T{ \fBDefault\fR T}:T{ -true +false +T} +:T{ +\fBMin Value\fR +T}:T{ T} :T{ -\fBRange\fR +\fBMax Value\fR T}:T{ -\&.\&. T} .TE .sp 1 -Update the index statistics for the given table, and restart any auto\-update that previously configured\&. +Update the index statistics for the given table, and restart any auto\-update that was previously configured\&. .RE .sp .RS 4 @@ -451,7 +494,7 @@ .TS allbox tab(:); l l s s -l l s s +l l l s ^ l l s ^ l l s ^ l l s. @@ -461,11 +504,8 @@ \-\-dump T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -473,12 +513,15 @@ :T{ \fBDefault\fR T}:T{ -true +false T} :T{ -\fBRange\fR +\fBMin Value\fR +T}:T{ +T} +:T{ +\fBMax Value\fR T}:T{ -\&.\&. T} .TE .sp 1 @@ -498,7 +541,7 @@ .TS allbox tab(:); l l s s -l l s s +l l l s ^ l l s ^ l l s ^ l l s. @@ -508,11 +551,8 @@ \-\-query=# T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ numeric @@ -523,17 +563,22 @@ 0 T} :T{ -\fBRange\fR +\fBMin Value\fR T}:T{ -0 \&.\&. MAX_INT +0 +T} +:T{ +\fBMax Value\fR +T}:T{ +MAX_INT T} .TE .sp 1 Perform random range queries on first key attribute (must be int unsigned)\&. .RE .PP -\fBndb_index_stat system options\fR. The following options are used to generate and update the statistics tables in the NDB kernel\&. They cannot be mixed with -ndb_index_stat statistics options\&. +\fBndb_index_stat system options\fR. The following options are used to generate and update the statistics tables in the NDB kernel\&. None of these options can be mixed with statistics options (see +ndb_index_stat statistics options)\&. .sp .RS 4 .ie n \{\ @@ -548,7 +593,7 @@ .TS allbox tab(:); l l s s -l l s s +l l l s ^ l l s ^ l l s ^ l l s. @@ -558,11 +603,8 @@ \-\-sys\-drop T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -570,12 +612,15 @@ :T{ \fBDefault\fR T}:T{ -true +false +T} +:T{ +\fBMin Value\fR +T}:T{ T} :T{ -\fBRange\fR +\fBMax Value\fR T}:T{ -\&.\&. T} .TE .sp 1 @@ -596,7 +641,7 @@ .TS allbox tab(:); l l s s -l l s s +l l l s ^ l l s ^ l l s ^ l l s. @@ -606,11 +651,8 @@ \-\-sys\-create T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -618,12 +660,15 @@ :T{ \fBDefault\fR T}:T{ -true +false T} :T{ -\fBRange\fR +\fBMin Value\fR +T}:T{ +T} +:T{ +\fBMax Value\fR T}:T{ -\&.\&. T} .TE .sp 1 @@ -643,7 +688,7 @@ .TS allbox tab(:); l l s s -l l s s +l l l s ^ l l s ^ l l s ^ l l s. @@ -653,11 +698,8 @@ \-\-sys\-create\-if\-not\-exist T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -665,12 +707,15 @@ :T{ \fBDefault\fR T}:T{ -true +false +T} +:T{ +\fBMin Value\fR +T}:T{ T} :T{ -\fBRange\fR +\fBMax Value\fR T}:T{ -\&.\&. T} .TE .sp 1 @@ -690,7 +735,7 @@ .TS allbox tab(:); l l s s -l l s s +l l l s ^ l l s ^ l l s ^ l l s. @@ -700,11 +745,8 @@ \-\-sys\-create\-if\-not\-valid T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -712,12 +754,15 @@ :T{ \fBDefault\fR T}:T{ -true +false T} :T{ -\fBRange\fR +\fBMin Value\fR +T}:T{ +T} +:T{ +\fBMax Value\fR T}:T{ -\&.\&. T} .TE .sp 1 @@ -737,7 +782,7 @@ .TS allbox tab(:); l l s s -l l s s +l l l s ^ l l s ^ l l s ^ l l s. @@ -747,11 +792,8 @@ \-\-sys\-check T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -759,12 +801,15 @@ :T{ \fBDefault\fR T}:T{ -true +false T} :T{ -\fBRange\fR +\fBMin Value\fR +T}:T{ +T} +:T{ +\fBMax Value\fR T}:T{ -\&.\&. T} .TE .sp 1 @@ -784,7 +829,7 @@ .TS allbox tab(:); l l s s -l l s s +l l l s ^ l l s ^ l l s ^ l l s. @@ -794,11 +839,8 @@ \-\-sys\-skip\-tables T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -806,12 +848,15 @@ :T{ \fBDefault\fR T}:T{ -true +false +T} +:T{ +\fBMin Value\fR +T}:T{ T} :T{ -\fBRange\fR +\fBMax Value\fR T}:T{ -\&.\&. T} .TE .sp 1 @@ -833,7 +878,7 @@ .TS allbox tab(:); l l s s -l l s s +l l l s ^ l l s ^ l l s ^ l l s. @@ -843,11 +888,8 @@ \-\-sys\-skip\-events T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -855,12 +897,15 @@ :T{ \fBDefault\fR T}:T{ -true +false T} :T{ -\fBRange\fR +\fBMin Value\fR +T}:T{ +T} +:T{ +\fBMax Value\fR T}:T{ -\&.\&. T} .TE .sp 1 @@ -882,8 +927,7 @@ .TS allbox tab(:); l l s s -l l s s -l l s s +l l l s ^ l l s ^ l l s ^ l l s. @@ -893,16 +937,8 @@ \-\-verbose T} T{ -\ \& -T}:T{ -\-v -T} -T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -910,12 +946,15 @@ :T{ \fBDefault\fR T}:T{ -true +false +T} +:T{ +\fBMin Value\fR +T}:T{ T} :T{ -\fBRange\fR +\fBMax Value\fR T}:T{ -\&.\&. T} .TE .sp 1 @@ -935,7 +974,7 @@ .TS allbox tab(:); l l s s -l l s s +l l l s ^ l l s ^ l l s ^ l l s. @@ -945,11 +984,8 @@ \-\-loops=# T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ numeric @@ -960,9 +996,14 @@ 0 T} :T{ -\fBRange\fR +\fBMin Value\fR +T}:T{ +0 +T} +:T{ +\fBMax Value\fR T}:T{ -0 \&.\&. MAX_INT +MAX_INT T} .TE .sp 1 @@ -971,7 +1012,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/ndbinfo_select_all.1 mysql-5.5-5.5.43/man/ndbinfo_select_all.1 --- mysql-5.5-5.5.35+dfsg/man/ndbinfo_select_all.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndbinfo_select_all.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndbinfo_select_all\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDBINFO_SELECT_AL" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDBINFO_SELECT_AL" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -121,7 +121,7 @@ .nr an-no-space-flag 1 .nr an-break-flag 1 .br -.B Table\ \&17.11.\ \&ndbinfo_select_all Options and Variables: MySQL Cluster NDB 7.2 +.B Table\ \&18.70.\ \& This table describes command-line options for the ndbinfo_select_all program .TS allbox tab(:); lB lB lB. @@ -130,7 +130,7 @@ T}:T{ Description T}:T{ -Added / Removed +Added or Removed T} .T& l l l @@ -141,10 +141,10 @@ .PP --delay=# T}:T{ -Set the delay in seconds between loops\&. Default is 5\&. +Set the delay in seconds between loops. Default is 5. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -152,10 +152,10 @@ .PP -l T}:T{ -Set the number of times to perform the select\&. Default is 1\&. +Set the number of times to perform the select. Default is 1. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -163,10 +163,10 @@ .PP -d T}:T{ -Name of the database where the table located\&. +Name of the database where the table located. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -174,10 +174,10 @@ .PP -p T}:T{ -Set the degree of parallelism\&. +Set the degree of parallelism. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} .TE .sp 1 @@ -195,7 +195,7 @@ .TS allbox tab(:); l l s s -l l s s +l l l s ^ l l s ^ l l s ^ l l s. @@ -205,11 +205,8 @@ \-\-delay=# T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ numeric @@ -220,9 +217,14 @@ 5 T} :T{ -\fBRange\fR +\fBMin Value\fR T}:T{ -0 \&.\&. MAX_INT +0 +T} +:T{ +\fBMax Value\fR +T}:T{ +MAX_INT T} .TE .sp 1 @@ -246,8 +248,7 @@ .TS allbox tab(:); l l s s -l l s s -l l s s +l l l s ^ l l s ^ l l s ^ l l s. @@ -257,16 +258,8 @@ \-\-loops=# T} T{ -\ \& -T}:T{ -\-l -T} -T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ numeric @@ -277,9 +270,14 @@ 1 T} :T{ -\fBRange\fR +\fBMin Value\fR +T}:T{ +0 +T} +:T{ +\fBMax Value\fR T}:T{ -0 \&.\&. MAX_INT +MAX_INT T} .TE .sp 1 @@ -290,7 +288,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/ndb_mgm.1 mysql-5.5-5.5.43/man/ndb_mgm.1 --- mysql-5.5-5.5.35+dfsg/man/ndb_mgm.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndb_mgm.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndb_mgm\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDB_MGM\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDB_MGM\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -87,7 +87,7 @@ .nr an-no-space-flag 1 .nr an-break-flag 1 .br -.B Table\ \&17.13.\ \&ndb_mgm Options and Variables: MySQL Cluster NDB 7.2 +.B Table\ \&18.72.\ \& This table describes command-line options for the ndb_mgm program .TS allbox tab(:); lB lB lB. @@ -96,7 +96,7 @@ T}:T{ Description T}:T{ -Added / Removed +Added or Removed T} .T& l l l @@ -110,7 +110,7 @@ Specify number of tries for connecting to ndb_mgmd (0 = infinite) T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -121,7 +121,7 @@ Execute command and exit T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} .TE .sp 1 @@ -140,18 +140,12 @@ \fB\-e \fR\fBcommand\fR .TS allbox tab(:); -l l s s l l s s. T{ \fBCommand\-Line Format\fR T}:T{ \-\-execute=name T} -T{ -\ \& -T}:T{ -\-e -T} .TE .sp 1 This option can be used to send a command to the MySQL Cluster management client from the system shell\&. For example, either of the following is equivalent to executing @@ -176,7 +170,7 @@ option works with the \fBmysql\fR command\-line client\&. See -Section\ \&4.2.3.1, \(lqUsing Options on the Command Line\(rq\&. +Section\ \&4.2.4, \(lqUsing Options on the Command Line\(rq\&. .if n \{\ .sp .\} @@ -208,9 +202,7 @@ .TS allbox tab(:); l l s s -l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -218,16 +210,8 @@ \-\-try\-reconnect=# T} T{ -\ \& -T}:T{ -\-t -T} -T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -247,11 +231,11 @@ Additional information about using \fBndb_mgm\fR can be found in -Section\ \&17.5.2, \(lqCommands in the MySQL Cluster Management Client\(rq\&. +Section\ \&18.5.2, \(lqCommands in the MySQL Cluster Management Client\(rq\&. .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/ndb_mgmd.8 mysql-5.5-5.5.43/man/ndb_mgmd.8 --- mysql-5.5-5.5.35+dfsg/man/ndb_mgmd.8 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndb_mgmd.8 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndb_mgmd\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDB_MGMD\FR" "8" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDB_MGMD\FR" "8" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -54,7 +54,7 @@ .nr an-no-space-flag 1 .nr an-break-flag 1 .br -.B Table\ \&17.12.\ \&ndb_mgmd Options and Variables: MySQL Cluster NDB 7.2 +.B Table\ \&18.71.\ \& This table describes command-line options for the ndb_mgmd program .TS allbox tab(:); lB lB lB. @@ -63,7 +63,7 @@ T}:T{ Description T}:T{ -Added / Removed +Added or Removed T} .T& l l l @@ -86,16 +86,14 @@ .PP --config-file=file, .PP --f, -.PP --c +-f T}:T{ -Specify the cluster configuration file; in NDB\-6\&.4\&.0 and later, needs - \-\-reload or \-\-initial to override configuration cache if - present +Specify the cluster configuration file; in NDB-6.4.0 and later, + needs --reload or --initial to override configuration cache if + present T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -103,10 +101,11 @@ .PP --config-dir=directory T}:T{ -Specify the cluster management server\*(Aqs configuration cache directory +Specify the cluster management server's configuration cache + directory T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -115,7 +114,7 @@ Local bind address T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -126,7 +125,7 @@ Print full configuration and exit T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -137,7 +136,7 @@ Run ndb_mgmd in daemon mode (default) T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -146,27 +145,27 @@ Do not run ndb_mgmd as a daemon T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --interactive T}:T{ Run ndb_mgmd in interactive mode (not officially supported in - production; for testing purposes only) + production; for testing purposes only) T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --log-name=name T}:T{ -A name to use when writing messages applying to this node in the cluster - log\&. +A name to use when writing messages applying to this node in the + cluster log. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -175,77 +174,77 @@ Do not provide any node id checks T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --mycnf T}:T{ -Read cluster configuration data from the my\&.cnf file +Read cluster configuration data from the my.cnf file T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --reload T}:T{ -Causes the management server to compare the configuration file with its - configuration cache +Causes the management server to compare the configuration file + with its configuration cache T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --initial T}:T{ -Causes the management server reload its configuration data from the - configuration file, bypassing the configuration cache +Causes the management server reload its configuration data from + the configuration file, bypassing the configuration cache T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --nowait-nodes=list T}:T{ -Do not wait for these management nodes when starting this management - server\&. Also requires \-\-ndb\-nodeid to be used\&. +Do not wait for these management nodes when starting this + management server. Also requires --ndb-nodeid to be used. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --config-cache[=TRUE|FALSE] T}:T{ -Enable the management server configuration cache; TRUE by default\&. +Enable the management server configuration cache; TRUE by default. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --install[=name] T}:T{ -Used to install the management server process as a Windows service\&. Does - not apply on non\-Windows platforms\&. +Used to install the management server process as a Windows + service. Does not apply on non-Windows platforms. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --remove[=name] T}:T{ -Used to remove a management server process that was previously installed - as a Windows service, optionally specifying the name of the - service to be removed\&. Does not apply on non\-Windows - platforms\&. +Used to remove a management server process that was previously + installed as a Windows service, optionally specifying the name of + the service to be removed. Does not apply on non-Windows + platforms. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} .TE .sp 1 @@ -263,8 +262,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -272,11 +270,8 @@ \-\-bind\-address=ip_address T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -309,8 +304,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -318,11 +312,8 @@ \-\-no\-nodeid\-checks T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -351,8 +342,7 @@ allbox tab(:); l l s s l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -365,11 +355,8 @@ \-\-config\-dir=directory T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ file name @@ -399,8 +386,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -408,11 +394,8 @@ \-\-config\-cache[=TRUE|FALSE] T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -431,7 +414,7 @@ ON), can be used to disable the management server\*(Aqs configuration cache, so that it reads its configuration from config\&.ini every time it starts (see -Section\ \&17.3.2, \(lqMySQL Cluster Configuration Files\(rq)\&. You can do this by starting the +Section\ \&18.3.2, \(lqMySQL Cluster Configuration Files\(rq)\&. You can do this by starting the \fBndb_mgmd\fR process with any one of the following options: .sp @@ -557,12 +540,7 @@ .TS allbox tab(:); l l s s -l l s s -l l s s -^ l l s -^ l l s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -570,31 +548,8 @@ \-\-config\-file=file T} T{ -\ \& -T}:T{ -\-f -T} -T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ -\fBType\fR -T}:T{ -file name -T} -:T{ -\fBDefault\fR T}:T{ -\&./config\&.ini -T} -T{ -\ \& -T}:T{ -\fBPermitted Values\fR -T} -:T{ \fBType\fR T}:T{ file name @@ -622,7 +577,7 @@ \fBndb_mgmd\fR was started with \fB\-\-config\-cache=OFF\fR\&. See -Section\ \&17.3.2, \(lqMySQL Cluster Configuration Files\(rq, for more information\&. +Section\ \&18.3.2, \(lqMySQL Cluster Configuration Files\(rq, for more information\&. .sp Formerly, using this option together with \fB\-\-initial\fR @@ -643,8 +598,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -652,11 +606,8 @@ \-\-mycnf T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -688,9 +639,7 @@ .TS allbox tab(:); l l s s -l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -698,16 +647,8 @@ \-\-daemon T} T{ -\ \& -T}:T{ -\-d -T} -T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -741,8 +682,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -750,11 +690,8 @@ \-\-interactive T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -786,8 +723,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -795,11 +731,8 @@ \-\-initial T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -812,7 +745,7 @@ .TE .sp 1 Configuration data is cached internally, rather than being read from the cluster global configuration file each time the management server is started (see -Section\ \&17.3.2, \(lqMySQL Cluster Configuration Files\(rq)\&. Using the +Section\ \&18.3.2, \(lqMySQL Cluster Configuration Files\(rq)\&. Using the \fB\-\-initial\fR option overrides this behavior, by forcing the management server to delete any existing cache files, and then to re\-read the configuration data from the cluster configuration file and to build a new cache\&. .sp @@ -835,7 +768,7 @@ ignores \fB\-\-initial\fR unless it is the only management server running\&. This behavior also has implications when performing a rolling restart of a MySQL Cluster with multiple management nodes\&. See -Section\ \&17.5.5, \(lqPerforming a Rolling Restart of a MySQL Cluster\(rq, for more information\&. +Section\ \&18.5.5, \(lqPerforming a Rolling Restart of a MySQL Cluster\(rq, for more information\&. .sp Formerly, using this option together with the \fB\-\-config\-file\fR @@ -855,8 +788,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -864,11 +796,8 @@ \-\-log\-name=name T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -896,8 +825,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -905,11 +833,8 @@ \-\-nodaemon T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -945,9 +870,7 @@ .TS allbox tab(:); l l s s -l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -955,16 +878,8 @@ \-\-print\-full\-config T} T{ -\ \& -T}:T{ -\-P -T} -T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -996,8 +911,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -1005,11 +919,8 @@ \-\-reload T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -1022,7 +933,7 @@ .TE .sp 1 In MySQL Cluster NDB 7\&.2, configuration data is stored internally rather than being read from the cluster global configuration file each time the management server is started (see -Section\ \&17.3.2, \(lqMySQL Cluster Configuration Files\(rq)\&. Using this option forces the management server to check its internal data store against the cluster configuration file and to reload the configuration if it finds that the configuration file does not match the cache\&. Existing configuration cache files are preserved, but not used\&. +Section\ \&18.3.2, \(lqMySQL Cluster Configuration Files\(rq)\&. Using this option forces the management server to check its internal data store against the cluster configuration file and to reload the configuration if it finds that the configuration file does not match the cache\&. Existing configuration cache files are preserved, but not used\&. .sp This differs in two ways from the \fB\-\-initial\fR @@ -1041,7 +952,7 @@ ignores \fB\-\-reload\fR unless it is the only management server running\&. This behavior also has implications when performing a rolling restart of a MySQL Cluster with multiple management nodes\&. See -Section\ \&17.5.5, \(lqPerforming a Rolling Restart of a MySQL Cluster\(rq, for more information\&. +Section\ \&18.5.5, \(lqPerforming a Rolling Restart of a MySQL Cluster\(rq, for more information\&. .RE .sp .RS 4 @@ -1057,7 +968,7 @@ .TS allbox tab(:); l l s s -l l s s +l l l s ^ l l s ^ l l s ^ l l s. @@ -1067,11 +978,8 @@ \-\-nowait\-nodes=list T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ numeric @@ -1081,9 +989,14 @@ T}:T{ T} :T{ -\fBRange\fR +\fBMin Value\fR T}:T{ -1 \&.\&. 255 +1 +T} +:T{ +\fBMax Value\fR +T}:T{ +255 T} .TE .sp 1 @@ -1166,7 +1079,7 @@ The same is true with regard to the connection string used with any \fBmysqld\fR processes that you wish to start as MySQL Cluster SQL nodes connected to this cluster\&. See -Section\ \&17.3.2.3, \(lqMySQL Cluster Connection Strings\(rq, for more information\&. +Section\ \&18.3.2.3, \(lqMySQL Cluster Connection Strings\(rq, for more information\&. .sp When used with \fBndb_mgmd\fR, this option affects the behavior of the management node with regard to other management nodes only\&. Do not confuse it with the @@ -1200,7 +1113,7 @@ It is not strictly necessary to specify a connection string when starting the management server\&. However, if you are using more than one management server, a connection string should be provided and each node in the cluster should specify its node ID explicitly\&. .PP See -Section\ \&17.3.2.3, \(lqMySQL Cluster Connection Strings\(rq, for information about using connection strings\&. +Section\ \&18.3.2.3, \(lqMySQL Cluster Connection Strings\(rq, for information about using connection strings\&. \fBndb_mgmd\fR(8), describes other options for \fBndb_mgmd\fR\&. .PP @@ -1227,7 +1140,7 @@ .\" config.ini (MySQL Cluster) config\&.ini is the configuration file for the cluster as a whole\&. This file is created by the user and read by the management server\&. -Section\ \&17.3, \(lqConfiguration of MySQL Cluster NDB 7.2\(rq, discusses how to set up this file\&. +Section\ \&18.3, \(lqConfiguration of MySQL Cluster\(rq, discusses how to set up this file\&. .RE .sp .RS 4 @@ -1240,7 +1153,7 @@ .\} ndb_\fInode_id\fR_cluster\&.log is the cluster events log file\&. Examples of such events include checkpoint startup and completion, node startup events, node failures, and levels of memory usage\&. A complete listing of cluster events with descriptions may be found in -Section\ \&17.5, \(lqManagement of MySQL Cluster\(rq\&. +Section\ \&18.5, \(lqManagement of MySQL Cluster\(rq\&. .sp When the size of the cluster log reaches one million bytes, the file is renamed to ndb_\fInode_id\fR_cluster\&.log\&.\fIseq_id\fR, where @@ -1291,7 +1204,7 @@ allbox tab(:); l l s s l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -1299,11 +1212,13 @@ \-\-install[=name] T} T{ -\ \& +\fBPlatform Specific\fR T}:T{ -\fBPermitted Values\fR +Windows T} -:T{ +T{ +\fBPermitted Values\fR +T}:T{ \fBType\fR T}:T{ string @@ -1354,7 +1269,7 @@ allbox tab(:); l l s s l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -1362,11 +1277,13 @@ \-\-remove[=name] T} T{ -\ \& +\fBPlatform Specific\fR T}:T{ -\fBPermitted Values\fR +Windows T} -:T{ +T{ +\fBPermitted Values\fR +T}:T{ \fBType\fR T}:T{ string @@ -1390,7 +1307,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/ndbmtd.8 mysql-5.5-5.5.43/man/ndbmtd.8 --- mysql-5.5-5.5.35+dfsg/man/ndbmtd.8 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndbmtd.8 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndbmtd\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDBMTD\FR" "8" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDBMTD\FR" "8" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -59,7 +59,7 @@ also apply to \fBndbmtd\fR\&. For more information about these options and parameters, see \fBndbd\fR(8), and -Section\ \&17.3.2.6, \(lqDefining MySQL Cluster Data Nodes\(rq, respectively\&. +Section\ \&18.3.2.6, \(lqDefining MySQL Cluster Data Nodes\(rq, respectively\&. .PP \fBndbmtd\fR is also file system\-compatible with @@ -203,7 +203,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/ndb_print_backup_file.1 mysql-5.5-5.5.43/man/ndb_print_backup_file.1 --- mysql-5.5-5.5.35+dfsg/man/ndb_print_backup_file.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndb_print_backup_file.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndb_print_backup_file\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDB_PRINT_BACKUP_" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDB_PRINT_BACKUP_" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -37,7 +37,7 @@ .PP \fBndb_print_backup_file\fR obtains diagnostic information from a cluster backup file\&. - Usage +Usage .sp .if n \{\ .RS 4 @@ -57,7 +57,7 @@ BACKUP\-\fI#\fR, where \fI#\fR is the sequence number for the backup\&. For more information about cluster backup files and their contents, see -Section\ \&17.5.3.1, \(lqMySQL Cluster Backup Concepts\(rq\&. +Section\ \&18.5.3.1, \(lqMySQL Cluster Backup Concepts\(rq\&. .PP Like \fBndb_print_schema_file\fR @@ -68,13 +68,12 @@ utilities that are intended to be run on a management server host or to connect to a management server) \fBndb_print_backup_file\fR must be run on a cluster data node, since it accesses the data node file system directly\&. Because it does not make use of the management server, this utility can be used when the management server is not running, and even when the cluster has been completely shut down\&. - Additional Options -.PP +Additional Options.PP None\&. .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/ndb_print_file.1 mysql-5.5-5.5.43/man/ndb_print_file.1 --- mysql-5.5-5.5.35+dfsg/man/ndb_print_file.1 1970-01-01 00:00:00.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndb_print_file.1 2015-02-27 08:30:42.000000000 +0000 @@ -0,0 +1,123 @@ +'\" t +.\" Title: \fBndb_print_file\fR +.\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 +.\" Manual: MySQL Database System +.\" Source: MySQL 5.5 +.\" Language: English +.\" +.TH "\FBNDB_PRINT_FILE\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" +.\" ----------------------------------------------------------------- +.\" * Define some portability stuff +.\" ----------------------------------------------------------------- +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.\" http://bugs.debian.org/507673 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" ----------------------------------------------------------------- +.\" * set default formatting +.\" ----------------------------------------------------------------- +.\" disable hyphenation +.nh +.\" disable justification (adjust text to left margin only) +.ad l +.\" ----------------------------------------------------------------- +.\" * MAIN CONTENT STARTS HERE * +.\" ----------------------------------------------------------------- +.\" ndb_print_file +.SH "NAME" +ndb_print_file \- print NDB Disk Data file contents +.SH "SYNOPSIS" +.HP \w'\fBndb_print_file\ [\-v]\ [\-q]\ \fR\fB\fIfile_name\fR\fR\fB+\fR\ 'u +\fBndb_print_file [\-v] [\-q] \fR\fB\fIfile_name\fR\fR\fB+\fR +.SH "DESCRIPTION" +.PP +\fBndb_print_file\fR +obtains information from a MySQL Cluster Disk Data file\&. +Usage +.sp +.if n \{\ +.RS 4 +.\} +.nf +ndb_print_file [\-v] [\-q] \fIfile_name\fR+ +.fi +.if n \{\ +.RE +.\} +.PP +\fIfile_name\fR +is the name of a MySQL Cluster Disk Data file\&. Multiple filenames are accepted, separated by spaces\&. +.PP +Like +\fBndb_print_schema_file\fR +and +\fBndb_print_sys_file\fR +(and unlike most of the other +NDB +utilities that are intended to be run on a management server host or to connect to a management server) +\fBndb_print_file\fR +must be run on a MySQL Cluster data node, since it accesses the data node file system directly\&. Because it does not make use of the management server, this utility can be used when the management server is not running, and even when the cluster has been completely shut down\&. +Additional Options.PP +\fBndb_print_file\fR +supports the following options: +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-v\fR: Make output verbose\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-q\fR: Suppress output (quiet mode)\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +\fB\-\-help\fR, +\fB\-h\fR, +\fB\-?\fR: Suppress output (quiet mode)\&. +.sp +This option did not work correctly prior to MySQL Cluster NDB 7\&.2\&.18\&. (Bug #17069285) +.RE +.PP +For more information, see +Section\ \&18.5.12, \(lqMySQL Cluster Disk Data Tables\(rq\&. +.SH "COPYRIGHT" +.br +.PP +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. +.PP +This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. +.PP +This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. +.PP +You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA or see http://www.gnu.org/licenses/. +.sp +.SH "SEE ALSO" +For more information, please refer to the MySQL Reference Manual, +which may already be installed locally and which is also available +online at http://dev.mysql.com/doc/. +.SH AUTHOR +Oracle Corporation (http://dev.mysql.com/). diff -Nru mysql-5.5-5.5.35+dfsg/man/ndb_print_schema_file.1 mysql-5.5-5.5.43/man/ndb_print_schema_file.1 --- mysql-5.5-5.5.35+dfsg/man/ndb_print_schema_file.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndb_print_schema_file.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndb_print_schema_file\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDB_PRINT_SCHEMA_" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDB_PRINT_SCHEMA_" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -37,7 +37,7 @@ .PP \fBndb_print_schema_file\fR obtains diagnostic information from a cluster schema file\&. - Usage +Usage .sp .if n \{\ .RS 4 @@ -51,7 +51,7 @@ .PP \fIfile_name\fR is the name of a cluster schema file\&. For more information about cluster schema files, see -\m[blue]\fBMySQL Cluster Data Node FileSystemDir Files\fR\m[]\&\s-2\u[1]\d\s+2\&. +\m[blue]\fBMySQL Cluster Data Node File System Directory Files\fR\m[]\&\s-2\u[1]\d\s+2\&. .PP Like \fBndb_print_backup_file\fR @@ -62,13 +62,12 @@ utilities that are intended to be run on a management server host or to connect to a management server) \fBndb_schema_backup_file\fR must be run on a cluster data node, since it accesses the data node file system directly\&. Because it does not make use of the management server, this utility can be used when the management server is not running, and even when the cluster has been completely shut down\&. - Additional Options -.PP +Additional Options.PP None\&. .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP @@ -78,7 +77,7 @@ .sp .SH "NOTES" .IP " 1." 4 -MySQL Cluster Data Node FileSystemDir Files +MySQL Cluster Data Node File System Directory Files .RS 4 \%http://dev.mysql.com/doc/ndbapi/en/ndb-internals-ndbd-filesystemdir-files.html .RE diff -Nru mysql-5.5-5.5.35+dfsg/man/ndb_print_sys_file.1 mysql-5.5-5.5.43/man/ndb_print_sys_file.1 --- mysql-5.5-5.5.35+dfsg/man/ndb_print_sys_file.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndb_print_sys_file.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndb_print_sys_file\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDB_PRINT_SYS_FIL" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDB_PRINT_SYS_FIL" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -37,7 +37,7 @@ .PP \fBndb_print_sys_file\fR obtains diagnostic information from a MySQL Cluster system file\&. - Usage +Usage .sp .if n \{\ .RS 4 @@ -54,7 +54,7 @@ ndb_\fI#\fR_fs/D\fI#\fR/DBDIH/P\fI#\fR\&.sysfile\&. In each case, the \fI#\fR represents a number (not necessarily the same number)\&. For more information, see -\m[blue]\fBMySQL Cluster Data Node FileSystemDir Files\fR\m[]\&\s-2\u[1]\d\s+2\&. +\m[blue]\fBMySQL Cluster Data Node File System Directory Files\fR\m[]\&\s-2\u[1]\d\s+2\&. .PP Like \fBndb_print_backup_file\fR @@ -65,13 +65,12 @@ utilities that are intended to be run on a management server host or to connect to a management server) \fBndb_print_backup_file\fR must be run on a cluster data node, since it accesses the data node file system directly\&. Because it does not make use of the management server, this utility can be used when the management server is not running, and even when the cluster has been completely shut down\&. - Additional Options -.PP +Additional Options.PP None\&. .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP @@ -81,7 +80,7 @@ .sp .SH "NOTES" .IP " 1." 4 -MySQL Cluster Data Node FileSystemDir Files +MySQL Cluster Data Node File System Directory Files .RS 4 \%http://dev.mysql.com/doc/ndbapi/en/ndb-internals-ndbd-filesystemdir-files.html .RE diff -Nru mysql-5.5-5.5.35+dfsg/man/ndb_restore.1 mysql-5.5-5.5.43/man/ndb_restore.1 --- mysql-5.5-5.5.35+dfsg/man/ndb_restore.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndb_restore.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndb_restore\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDB_RESTORE\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDB_RESTORE\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -48,7 +48,7 @@ must be executed once for each of the backup files that were created by the START BACKUP command used to create the backup (see -Section\ \&17.5.3.2, \(lqUsing The MySQL Cluster Management Client to Create a Backup\(rq)\&. This is equal to the number of data nodes in the cluster at the time that the backup was created\&. +Section\ \&18.5.3.2, \(lqUsing The MySQL Cluster Management Client to Create a Backup\(rq)\&. This is equal to the number of data nodes in the cluster at the time that the backup was created\&. .\" single user mode (MySQL Cluster): and ndb_restore .if n \{\ .sp @@ -65,7 +65,7 @@ .PP Before using \fBndb_restore\fR, it is recommended that the cluster be running in single user mode, unless you are restoring multiple data nodes in parallel\&. See -Section\ \&17.5.8, \(lqMySQL Cluster Single User Mode\(rq, for more information\&. +Section\ \&18.5.8, \(lqMySQL Cluster Single User Mode\(rq, for more information\&. .sp .5v .RE .PP @@ -78,7 +78,7 @@ .nr an-no-space-flag 1 .nr an-break-flag 1 .br -.B Table\ \&17.23.\ \&ndb_restore Options and Variables: MySQL Cluster NDB 7.2 +.B Table\ \&18.82.\ \& This table describes command-line options for the ndb_restore program .TS allbox tab(:); lB lB lB. @@ -87,7 +87,7 @@ T}:T{ Description T}:T{ -Added / Removed +Added or Removed T} .T& l l l @@ -130,6 +130,8 @@ l l l l l l l l l +l l l +l l l l l l. T{ .PP @@ -137,10 +139,10 @@ .PP -c T}:T{ -Alias for \-\-connectstring\&. +Alias for --connectstring. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -148,10 +150,10 @@ .PP -n T}:T{ -Back up files from node with this ID +Restore backup files to node with this ID T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -162,7 +164,7 @@ Restore from the backup with the given ID T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -173,7 +175,7 @@ Restore table data and logs into NDB Cluster using the NDB API T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -184,7 +186,7 @@ Restore metadata to NDB Cluster using the NDB API T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -192,11 +194,11 @@ .PP -u T}:T{ -Do not upgrade array type for varsize attributes which do not already - resize VAR data, and do not change column attributes +Do not upgrade array type for varsize attributes which do not + already resize VAR data, and do not change column attributes T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -207,7 +209,7 @@ Allow attributes to be promoted when restoring data from backup T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -215,11 +217,11 @@ .PP -P T}:T{ -Allow preservation of trailing spaces (including padding) when promoting - fixed\-width string types to variable\-width types +Allow preservation of trailing spaces (including padding) when + promoting fixed-width string types to variable-width types T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -230,7 +232,7 @@ Do not restore objects relating to Disk Data T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -238,12 +240,12 @@ .PP -e T}:T{ -Restore epoch info into the status table\&. Convenient on a MySQL Cluster - replication slave for starting replication\&. The row in - mysql\&.ndb_apply_status with id 0 will be updated/inserted\&. +Restore epoch info into the status table. Convenient on a MySQL + Cluster replication slave for starting replication. The row in + mysql.ndb_apply_status with id 0 will be updated/inserted. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -254,7 +256,7 @@ Skip table structure check during restoring of data T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -265,17 +267,17 @@ Number of parallel transactions to use while restoring data T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --print T}:T{ -Print metadata, data and log to stdout (equivalent to \-\-print_meta - \-\-print_data \-\-print_log) +Print metadata, data and log to stdout (equivalent to --print_meta + --print_data --print_log) T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -284,7 +286,7 @@ Print metadata to stdout T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -293,7 +295,7 @@ Print data to stdout T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -302,7 +304,7 @@ Print to stdout T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -311,7 +313,7 @@ Path to backup files directory T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -319,11 +321,11 @@ .PP -f T}:T{ -Do not ignore system table during restore\&. Experimental only; not for - production use +Do not ignore system table during restore. Experimental only; not + for production use T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -331,11 +333,11 @@ .PP -z T}:T{ -Nodegroup map for NDBCLUSTER storage engine\&. Syntax: list of - (source_nodegroup, destination_nodegroup) +Nodegroup map for NDBCLUSTER storage engine. Syntax: list of + (source_nodegroup, destination_nodegroup) T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -344,7 +346,7 @@ Fields are enclosed with the indicated character T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -353,7 +355,7 @@ Fields are terminated by the indicated character T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -362,7 +364,7 @@ Fields are optionally enclosed with the indicated character T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -371,7 +373,7 @@ Lines are terminated by the indicated character T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -380,7 +382,7 @@ Print binary types in hexadecimal format T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -388,19 +390,19 @@ .PP -T T}:T{ -Creates a tab\-separated \&.txt file for each table in the given path +Creates a tab-separated .txt file for each table in the given path T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --append T}:T{ -Append data to a tab\-delimited file +Append data to a tab-delimited file T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -409,17 +411,17 @@ Print status of restoration each given number of seconds T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --no-binlog T}:T{ If a mysqld is connected and using binary logging, do not log the - restored data + restored data T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -428,97 +430,110 @@ Level of verbosity in output T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --include-databases=db-list T}:T{ -List of one or more databases to restore (excludes those not named) +List of one or more databases to restore (excludes those not + named) T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --exclude-databases=db-list T}:T{ -List of one or more databases to exclude (includes those not named) +List of one or more databases to exclude (includes those not + named) T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --include-tables=table-list T}:T{ -List of one or more tables to restore (excludes those in same database - that are not named); each table reference must include the - database name +List of one or more tables to restore (excludes those in same + database that are not named); each table reference must include + the database name T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --exclude-tables=table-list T}:T{ -List of one or more tables to exclude (includes those in same database - that are not not named); each table reference must include - the database name +List of one or more tables to exclude (includes those in the same + database that are not named); each table reference must include + the database name T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --exclude-missing-columns T}:T{ -Causes columns from the backup version of a table that are missing from - the version of the table in the database to be ignored\&. +Causes columns from the backup version of a table that are missing + from the version of the table in the database to be ignored. +T}:T{ +.PP +All MySQL 5.5 based releases +T} +T{ +.PP +--exclude-missing-tables +T}:T{ +Causes tables from the backup that are missing from the database + to be ignored. T}:T{ .PP -All MySQL 5\&.5 based releases +ADDED: NDB 7.2.18 T} T{ .PP --disable-indexes T}:T{ -Causes indexes from a backup to be ignored; may decrease time needed to - restore data\&. +Causes indexes from a backup to be ignored; may decrease time + needed to restore data. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --rebuild-indexes T}:T{ -Causes multi\-threaded ordered index rebuilding of indexes found in the - backup\&. +Causes multi-threaded rebuilding of ordered indexes found in the + backup. Number of threads used is determined by setting + BuildIndexThreads parameter. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --skip-broken-objects T}:T{ -Causes missing blob tables in the backup file to be ignored\&. +Causes missing blob tables in the backup file to be ignored. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --skip-unknown-objects T}:T{ -Causes schema objects not recognized by ndb_restore to be ignored when - restoring a backup made from a newer MySQL Cluster version - to an older version\&. +Causes schema objects not recognized by ndb_restore to be ignored + when restoring a backup made from a newer MySQL Cluster version to + an older version. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -527,7 +542,7 @@ Restores to a database with a different name than the original T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -535,23 +550,35 @@ .PP -L T}:T{ -Allow lossy conversions of column values (type demotions or changes in - sign) when restoring data from backup +Allow lossy conversions of column values (type demotions or + changes in sign) when restoring data from backup T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --restore-privilege-tables T}:T{ -Restore MySQL privilege tables that were previously moved to NDB\&. +Restore MySQL privilege tables that were previously moved to NDB. +T}:T{ +.PP +All MySQL 5.5 based releases +T} +T{ +.PP +--exclude-intermediate-sql-tables[=TRUE|FALSE] +T}:T{ +If TRUE (the default), do not restore any intermediate tables + (having names prefixed with '#sql-') that were left over from + copying ALTER TABLE operations. T}:T{ .PP -All MySQL 5\&.5 based releases +ADDED: NDB 7.2.17 T} .TE .sp 1 +.\" ndb_restore: typical and required options .PP Typical options for this utility are shown here: .sp @@ -566,13 +593,25 @@ .RE .\} .PP +Normally, when restoring from a MySQL Cluster backup, +\fBndb_restore\fR +requires at a minimum the +\fB\-\-nodeid\fR +(short form: +\fB\-n\fR), +\fB\-\-backupid\fR +(short form: +\fB\-b\fR), and +\fB\-\-backup_path\fR +options\&. +.PP .\" restore_connect option (ndb_restore) The \fB\-c\fR option is used to specify a connection string which tells ndb_restore where to locate the cluster management server\&. (See -Section\ \&17.3.2.3, \(lqMySQL Cluster Connection Strings\(rq, for information on connection strings\&.) If this option is not used, then +Section\ \&18.3.2.3, \(lqMySQL Cluster Connection Strings\(rq, for information on connection strings\&.) If this option is not used, then \fBndb_restore\fR attempts to connect to a management server on localhost:1186\&. This utility acts as a cluster API node, and so requires a free connection @@ -590,7 +629,7 @@ section in config\&.ini that is not being used for a MySQL server or other application for this reason (see -Section\ \&17.3.2.7, \(lqDefining SQL and Other API Nodes in a MySQL Cluster\(rq)\&. +Section\ \&18.3.2.7, \(lqDefining SQL and Other API Nodes in a MySQL Cluster\(rq)\&. .PP You can verify that \fBndb_restore\fR @@ -610,9 +649,12 @@ .RE .\} .PP -.\" restore_nodeid option (ndb_restore) +.\" nodeid option (ndb_restore) +The +\fB\-\-nodeid\fR +or \fB\-n\fR -is used to specify the node ID of the data node on which the backups were taken\&. +is used to specify the node ID of the data node on which the backup should be restored\&. .PP The first time you run the \fBndb_restore\fR @@ -713,7 +755,7 @@ INT or BIGINT\&. See -Section\ \&16.4.1.9.2, \(lqReplication of Columns Having Different Data Types\(rq, for a table of type conversions currently supported by attribute promotion\&. +Section\ \&17.4.1.9.2, \(lqReplication of Columns Having Different Data Types\(rq, for a table of type conversions currently supported by attribute promotion\&. .PP Attribute promotion by \fBndb_restore\fR @@ -750,6 +792,50 @@ \fB\-A\fR) when restoring the table data\&. Attribute promotion does not occur if this option is not used; instead, the restore operation fails with an error\&. .RE .PP +Prior to MySQL Cluster NDB 7\&.2\&.14, conversions between character data types and +TEXT +or +BLOB +were not handled correctly (Bug #17325051)\&. +.PP +Prior to MySQL Cluster NDB 7\&.2\&.18, demotion of +TEXT +to +TINYTEXT +was not handled correctly (Bug #18875137)\&. +.PP +When converting between character data types and +TEXT +or +BLOB, only conversions between character types (CHAR +and +VARCHAR) and binary types (BINARY +and +VARBINARY) can be performed at the same time\&. For example, you cannot promote an +INT +column to +BIGINT +while promoting a +VARCHAR +column to +TEXT +in the same invocation of +\fBndb_restore\fR\&. +.PP +Converting between +TEXT +columns using different character sets is not supported\&. Beginning with MySQL Cluster NDB 7\&.2\&.18, it is expressly disallowed (Bug #18875137)\&. +.PP +When performing conversions of character or binary types to +TEXT +or +BLOB +with +\fBndb_restore\fR, you may notice that it creates and uses one or more staging tables named +\fItable_name\fR$ST\fInode_id\fR\&. These tables are not needed afterwards, and are normally deleted by +\fBndb_restore\fR +following a successful restoration\&. +.PP .\" ndb_restore: lossy-conversions option .\" lossy-conversions option (ndb_restore) \fB\-\-lossy\-conversions\fR, @@ -757,9 +843,7 @@ .TS allbox tab(:); l l s s -l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -767,16 +851,8 @@ \-\-lossy\-conversions T} T{ -\ \& -T}:T{ -\-L -T} -T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ boolean @@ -794,7 +870,7 @@ option\&. Using \fB\-\-lossy\-conversions\fR allows lossy conversions of column values (type demotions or changes in sign) when restoring data from backup\&. With some exceptions, the rules governing demotion are the same as for MySQL replication; see -Section\ \&16.4.1.9.2, \(lqReplication of Columns Having Different Data Types\(rq, for information about specific type conversions currently supported by attribute demotion\&. +Section\ \&17.4.1.9.2, \(lqReplication of Columns Having Different Data Types\(rq, for information about specific type conversions currently supported by attribute demotion\&. .PP \fBndb_restore\fR reports any truncation of data that it performs during lossy conversions once per attribute and column\&. @@ -848,7 +924,7 @@ option is used to specify the ID or sequence number of the backup, and is the same number shown by the management client in the Backup \fIbackup_id\fR completed message displayed upon completion of a backup\&. (See -Section\ \&17.5.3.2, \(lqUsing The MySQL Cluster Management Client to Create a Backup\(rq\&.) +Section\ \&18.5.3.2, \(lqUsing The MySQL Cluster Management Client to Create a Backup\(rq\&.) .if n \{\ .sp .\} @@ -876,7 +952,7 @@ in the id column is updated if it already exists; such a row is inserted if it does not already exist\&. (See -Section\ \&17.6.9, \(lqMySQL Cluster Backups With MySQL Cluster Replication\(rq\&.) +Section\ \&18.6.9, \(lqMySQL Cluster Backups With MySQL Cluster Replication\(rq\&.) .PP .\" restore_data option (ndb_restore) \fB\-\-restore_data\fR @@ -908,7 +984,7 @@ This works only if the privilege tables were converted to NDB before the backup was taken\&. For more information, see -Section\ \&17.5.14, \(lqDistributed MySQL Privileges for MySQL Cluster\(rq\&. +Section\ \&18.5.14, \(lqDistributed MySQL Privileges for MySQL Cluster\(rq\&. .PP .\" backup_path option (ndb_restore) .\" ndb_restore: backup_path option @@ -937,7 +1013,7 @@ must be run twice\(emonce for each database node in the cluster where the backup was taken\&. However, \fBndb_restore\fR cannot always restore backups made from a cluster running one version of MySQL to a cluster running a different MySQL version\&. See -Section\ \&17.2.7, \(lqUpgrading and Downgrading MySQL Cluster NDB 7.2\(rq, for more information\&. +Section\ \&18.2.7, \(lqUpgrading and Downgrading MySQL Cluster NDB 7.2\(rq, for more information\&. .if n \{\ .sp .\} @@ -1000,7 +1076,7 @@ TEXT and BLOB -column values are always truncated to the first 256 bytes in the output; this cannot currently be overridden when using +column values are always truncated\&. In MySQL Cluster NDB 7\&.2\&.18 and earlier, such values are truncated to the first 240 bytes in the output; in MySQL Cluster NDB 7\&.2\&.19 and later, they are truncated to 256 bytes\&. (Bug #14571512, Bug #65467) This cannot currently be overridden when using \fB\-\-print_data\fR\&. .PP Several additional options are available for use with the @@ -1023,18 +1099,12 @@ \fB\-T\fR .TS allbox tab(:); -l l s s l l s s. T{ \fBCommand\-Line Format\fR T}:T{ \-\-tab=path T} -T{ -\ \& -T}:T{ -\-T -T} .TE .sp 1 This option causes @@ -1059,8 +1129,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -1068,11 +1137,8 @@ \-\-fields\-enclosed\-by=char T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -1100,8 +1166,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -1109,11 +1174,8 @@ \-\-fields\-optionally\-enclosed\-by T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -1146,8 +1208,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -1155,11 +1216,8 @@ \-\-fields\-terminated\-by=char T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -1212,8 +1270,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -1221,11 +1278,8 @@ \-\-fields\-terminated\-by=char T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -1379,7 +1433,7 @@ This option stops \fBndb_restore\fR from restoring any MySQL Cluster Disk Data objects, such as tablespaces and log file groups; see -Section\ \&17.5.12, \(lqMySQL Cluster Disk Data Tables\(rq, for more information about these\&. +Section\ \&18.5.12, \(lqMySQL Cluster Disk Data Tables\(rq, for more information about these\&. .PP .\" ndb_restore: parallelism option .\" parallelism option (ndb_restore) @@ -1446,8 +1500,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -1455,11 +1508,8 @@ \-\-include\-databases=db\-list T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -1477,8 +1527,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -1486,11 +1535,8 @@ \-\-include\-tables=table\-list T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -1603,8 +1649,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -1612,11 +1657,8 @@ \-\-exclude\-databases=db\-list T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -1634,8 +1676,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -1643,11 +1684,8 @@ \-\-exclude\-tables=table\-list T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -1869,6 +1907,30 @@ \fBndb_restore\fR ignores any columns missing from tables being restored as compared to the versions of those tables found in the backup\&. This option applies to all tables being restored\&. If you wish to apply this option only to selected tables or databases, you can use it in combination with one or more of the options described in the previous paragraph to do so, then restore data to the remaining tables using a complementary set of these options\&. .PP +.\" ndb_restore: exclude-missing-tables option +.\" exclude-missing-tables option (ndb_restore) +\fB\-\-exclude\-missing\-tables\fR +.TS +allbox tab(:); +l l s s +l l s s. +T{ +\fBIntroduced\fR +T}:T{ +5\&.5\&.40\-ndb\-7\&.2\&.18 +T} +T{ +\fBCommand\-Line Format\fR +T}:T{ +\-\-exclude\-missing\-tables +T} +.TE +.sp 1 +.PP +Beginning with MySQL Cluster NDB 7\&.2\&.17, it is also possible to restore only selected tables columns using this option, which causes +\fBndb_restore\fR +to ignore any tables from the backup that are not found in the target database\&. +.PP .\" ndb_restore: disable-indexes option .\" disable-indexes option (ndb_restore) \fB\-\-disable\-indexes\fR @@ -1904,7 +1966,27 @@ \fBndb_restore\fR to cause multi\-threaded rebuilding of the ordered indexes while restoring a native NDB -backup\&. +backup\&. The number of threads used for building ordered indexes by +\fBndb_restore\fR +with this option is controlled by the +BuildIndexThreads +data node configuration parameter (MySQL Cluster NDB 6\&.3\&.30 and later; MySQL Cluster NDB 7\&.0\&.11 and later)\&. +.\" indexes: and ndb_restore +.PP +It is necessary to use this option only for the first run of +\fBndb_restore\fR; this causes all ordered indexes to be rebuilt without using +\fB\-\-rebuild\-indexes\fR +again when restoring subsequent nodes\&. You should use this option prior to inserting new rows into the database; otherwise, it is possible for a row to be inserted that later causes a unique constraint violation when trying to rebuild the indexes\&. +.PP +Rebuilding of unique indexes uses disk write bandwidth for redo logging and local checkpointing\&. An insufficient amount of this bandwith can lead to redo buffer overload or log overload errors\&. In such cases you can run +\fBndb_restore\fR +\fB\-\-rebuild\-indexes\fR +again; the process resumes at the point where the error occurred\&. You can also do this when you have encountered temporarary errors\&. You can repeat execution of +\fBndb_restore\fR +\fB\-\-rebuild\-indexes\fR +indefinitely; you may be able to stop such errors by reducing the value of +DiskCheckpointSpeed +to provide additional disk bandwidth to redo logging\&. .PP .\" ndb_restore: skip-broken-objects option .\" skip-broken-objects option (ndb_restore) @@ -1954,8 +2036,7 @@ .TS allbox tab(:); l l s s -l l s s -^ l l s +l l l s ^ l l s. T{ \fBCommand\-Line Format\fR @@ -1963,11 +2044,8 @@ \-\-rewrite\-database=olddb,newdb T} T{ -\ \& -T}:T{ \fBPermitted Values\fR -T} -:T{ +T}:T{ \fBType\fR T}:T{ string @@ -2045,6 +2123,58 @@ .sp .5v .RE .PP +.\" ndb_restore: exclude-intermediate-sql-tables option +.\" exclude-intermediate-sql-tables option (ndb_restore) +\fB\-\-exclude\-intermediate\-sql\-tables[=TRUE|FALSE]\fR +.TS +allbox tab(:); +l l s s +l l s s +l l l s +^ l l s. +T{ +\fBIntroduced\fR +T}:T{ +5\&.5\&.37\-ndb\-7\&.2\&.17 +T} +T{ +\fBCommand\-Line Format\fR +T}:T{ +\-\-exclude\-intermediate\-sql\-tables[=TRUE|FALSE] +T} +T{ +\fBPermitted Values\fR +T}:T{ +\fBType\fR +T}:T{ +boolean +T} +:T{ +\fBDefault\fR +T}:T{ +TRUE +T} +.TE +.sp 1 +.PP +When performing copying +ALTER TABLE +operations, +\fBmysqld\fR +creates intermediate tables (whose names are prefixed with +#sql\-)\&. When +TRUE, the +\fB\-\-exclude\-intermediate\-sql\-tables\fR +option keeps +\fBndb_restore\fR +from restoring such tables that may have been left over from such operations\&. This option is +TRUE +by default\&. +.PP +The +\fB\-\-exclude\-intermediate\-sql\-tables\fR +option was introduced in MySQL Cluster NDB 7\&.2\&.17\&. (Bug #17882305) +.PP \fBError reporting\fR. .\" ndb_restore: errors \fBndb_restore\fR reports both temporary and permanent errors\&. In the case of temporary errors, it may able to recover from them, and reports @@ -2074,7 +2204,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/ndb_select_all.1 mysql-5.5-5.5.43/man/ndb_select_all.1 --- mysql-5.5-5.5.35+dfsg/man/ndb_select_all.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndb_select_all.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndb_select_all\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDB_SELECT_ALL\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDB_SELECT_ALL\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -40,7 +40,7 @@ NDB table to stdout\&. - Usage +Usage .sp .if n \{\ .RS 4 @@ -61,7 +61,7 @@ .nr an-no-space-flag 1 .nr an-break-flag 1 .br -.B Table\ \&17.24.\ \&ndb_select_all Options and Variables: MySQL Cluster NDB 7.2 +.B Table\ \&18.83.\ \& This table describes command-line options for the ndb_select_all program .TS allbox tab(:); lB lB lB. @@ -70,7 +70,7 @@ T}:T{ Description T}:T{ -Added / Removed +Added or Removed T} .T& l l l @@ -85,6 +85,7 @@ l l l l l l l l l +l l l l l l. T{ .PP @@ -95,7 +96,7 @@ Name of the database in which the table is found T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -106,7 +107,7 @@ Degree of parallelism T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -117,7 +118,7 @@ Lock type T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -128,7 +129,7 @@ Sort resultset according to index whose name is supplied T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -139,7 +140,7 @@ Sort resultset in descending order (requires order flag) T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -150,7 +151,7 @@ Print header (set to 0|FALSE to disable headers in output) T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -161,7 +162,7 @@ Output numbers in hexadecimal format T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -172,17 +173,17 @@ Set a column delimiter T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --disk T}:T{ Print disk references (useful only for Disk Data tables having - nonindexed columns) + nonindexed columns) T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -191,7 +192,7 @@ Print rowid T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -200,7 +201,16 @@ Include GCI in output T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases +T} +T{ +.PP +--gci64 +T}:T{ +Include GCI and row epoch in output +T}:T{ +.PP +All MySQL 5.5 based releases T} T{ .PP @@ -211,7 +221,7 @@ Scan in tup order T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -220,7 +230,7 @@ Do not print table column data T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} .TE .sp 1 @@ -441,9 +451,28 @@ .\" gci option: ndb_select_all \fB\-\-gci\fR .sp -Adds a column to the output showing the global checkpoint at which each row was last updated\&. See -Section\ \&17.1, \(lqMySQL Cluster Overview\(rq, and -Section\ \&17.5.6.2, \(lqMySQL Cluster Log Events\(rq, for more information about checkpoints\&. +Adds a +GCI +column to the output showing the global checkpoint at which each row was last updated\&. See +Section\ \&18.1, \(lqMySQL Cluster Overview\(rq, and +Section\ \&18.5.6.2, \(lqMySQL Cluster Log Events\(rq, for more information about checkpoints\&. +.RE +.sp +.RS 4 +.ie n \{\ +\h'-04'\(bu\h'+03'\c +.\} +.el \{\ +.sp -1 +.IP \(bu 2.3 +.\} +.\" ndb_select_all: gci64 option +.\" gci64 option: ndb_select_all +\fB\-\-gci64\fR +.sp +Adds a +ROW$GCI64 +column to the output showing the global checkpoint at which each row was last updated, as well as the number of the epoch in which this update occurred\&. .RE .sp .RS 4 @@ -476,8 +505,7 @@ .sp Causes any table data to be omitted\&. .RE - Sample Output -.PP +Sample Output.PP Output from a MySQL SELECT statement: @@ -574,7 +602,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/ndb_select_count.1 mysql-5.5-5.5.43/man/ndb_select_count.1 --- mysql-5.5-5.5.35+dfsg/man/ndb_select_count.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndb_select_count.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndb_select_count\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDB_SELECT_COUNT\" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDB_SELECT_COUNT\" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -40,7 +40,7 @@ NDB tables\&. With a single table, the result is equivalent to that obtained by using the MySQL statement SELECT COUNT(*) FROM \fItbl_name\fR\&. - Usage +Usage .sp .if n \{\ .RS 4 @@ -61,7 +61,7 @@ .nr an-no-space-flag 1 .nr an-break-flag 1 .br -.B Table\ \&17.25.\ \&ndb_select_count Options and Variables: MySQL Cluster NDB 7.2 +.B Table\ \&18.84.\ \& This table describes command-line options for the ndb_select_count program .TS allbox tab(:); lB lB lB. @@ -70,7 +70,7 @@ T}:T{ Description T}:T{ -Added / Removed +Added or Removed T} .T& l l l @@ -78,43 +78,43 @@ l l l. T{ .PP -\-\-database=dbname, +--database=dbname, .PP -\-d +-d T}:T{ Name of the database in which the table is found T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP -\-\-parallelism=#, +--parallelism=#, .PP -\-p +-p T}:T{ Degree of parallelism T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP -\-\-lock=#, +--lock=#, .PP -\-l +-l T}:T{ Lock type T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} .TE .sp 1 .PP You can obtain row counts from multiple tables in the same database by listing the table names separated by spaces when invoking this command, as shown under \fBSample Output\fR\&. - Sample Output +Sample Output .sp .if n \{\ .RS 4 @@ -131,7 +131,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/ndb_show_tables.1 mysql-5.5-5.5.43/man/ndb_show_tables.1 --- mysql-5.5-5.5.35+dfsg/man/ndb_show_tables.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndb_show_tables.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndb_show_tables\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDB_SHOW_TABLES\F" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDB_SHOW_TABLES\F" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -52,7 +52,7 @@ .nr an-no-space-flag 1 .nr an-break-flag 1 .br -.B Table\ \&17.26.\ \&ndb_show_tables Options and Variables: MySQL Cluster NDB 7.2 +.B Table\ \&18.85.\ \& This table describes command-line options for the ndb_show_tables program .TS allbox tab(:); lB lB lB. @@ -61,7 +61,7 @@ T}:T{ Description T}:T{ -Added / Removed +Added or Removed T} .T& l l l @@ -79,7 +79,7 @@ Specifies the database in which the table is found T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -90,7 +90,7 @@ Number of times to repeat output T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -101,7 +101,7 @@ Limit output to objects of this type T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -112,7 +112,7 @@ Do not qualify table names T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -123,7 +123,7 @@ Return output suitable for MySQL LOAD DATA INFILE statement T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -132,11 +132,11 @@ Show table temporary flag T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} .TE .sp 1 - Usage +Usage .sp .if n \{\ .RS 4 @@ -307,7 +307,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/ndb_size.pl.1 mysql-5.5-5.5.43/man/ndb_size.pl.1 --- mysql-5.5-5.5.35+dfsg/man/ndb_size.pl.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndb_size.pl.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndb_size.pl\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDB_SIZE\&.PL\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDB_SIZE\&.PL\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -38,7 +38,7 @@ This is a Perl script that can be used to estimate the amount of space that would be required by a MySQL database if it were converted to use the NDBCLUSTER storage engine\&. Unlike the other utilities discussed in this section, it does not require access to a MySQL Cluster (in fact, there is no reason for it to do so)\&. However, it does need to access the MySQL server on which the database to be tested resides\&. - Requirements +Requirements .sp .RS 4 .ie n \{\ @@ -102,7 +102,7 @@ .nr an-no-space-flag 1 .nr an-break-flag 1 .br -.B Table\ \&17.27.\ \&ndb_size\&.pl Options and Variables: MySQL Cluster NDB 7.2 +.B Table\ \&18.86.\ \& This table describes command-line options for the ndb_size.pl program .TS allbox tab(:); lB lB lB. @@ -111,7 +111,7 @@ T}:T{ Description T}:T{ -Added / Removed +Added or Removed T} .T& l l l @@ -129,11 +129,11 @@ .PP --database=dbname T}:T{ -The database or databases to examine; accepts a comma\-delimited list; - the default is ALL (use all databases found on the server) +The database or databases to examine; accepts a comma-delimited + list; the default is ALL (use all databases found on the server) T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -142,7 +142,7 @@ Specify host and optional port as host[:port] T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -151,7 +151,7 @@ Specify a socket to connect to T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -160,7 +160,7 @@ Specify a MySQL user name T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -169,7 +169,7 @@ Specify a MySQL user password T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -178,25 +178,25 @@ Set output format (text or HTML) T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --excludetables=tbl_list T}:T{ -Skip any tables in a comma\-separated list of tables +Skip any tables in a comma-separated list of tables T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --excludedbs=db_list T}:T{ -Skip any databases in a comma\-separated list of databases +Skip any databases in a comma-separated list of databases T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -205,17 +205,17 @@ Saves all queries to the database into the file specified T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --loadqueries=file T}:T{ Loads all queries from the file specified; does not connect to a - database + database T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -224,11 +224,11 @@ Designates a table to handle unique index size calculations T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} .TE .sp 1 - Usage +Usage .sp .if n \{\ .RS 4 @@ -397,7 +397,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/ndb_waiter.1 mysql-5.5-5.5.43/man/ndb_waiter.1 --- mysql-5.5-5.5.35+dfsg/man/ndb_waiter.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/ndb_waiter.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBndb_waiter\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBNDB_WAITER\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBNDB_WAITER\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -142,7 +142,7 @@ .nr an-no-space-flag 1 .nr an-break-flag 1 .br -.B Table\ \&17.28.\ \&ndb_waiter Options and Variables: MySQL Cluster NDB 7.2 +.B Table\ \&18.87.\ \& This table describes command-line options for the ndb_waiter program .TS allbox tab(:); lB lB lB. @@ -151,7 +151,7 @@ T}:T{ Description T}:T{ -Added / Removed +Added or Removed T} .T& l l l @@ -169,7 +169,7 @@ Wait for cluster to reach NO CONTACT state T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -178,7 +178,7 @@ Wait for cluster to reach NOT STARTED state T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -187,7 +187,7 @@ Wait for cluster to enter single user mode T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -195,20 +195,20 @@ .PP -t T}:T{ -Wait this many seconds, then exit whether or not cluster has reached - desired state; default is 2 minutes (120 seconds) +Wait this many seconds, then exit whether or not cluster has + reached desired state; default is 2 minutes (120 seconds) T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP --nowait-nodes=list T}:T{ -List of nodes not to be waited for\&. +List of nodes not to be waited for. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} T{ .PP @@ -216,14 +216,14 @@ .PP -w T}:T{ -List of nodes to be waited for\&. +List of nodes to be waited for. T}:T{ .PP -All MySQL 5\&.5 based releases +All MySQL 5.5 based releases T} .TE .sp 1 - Usage +Usage .sp .if n \{\ .RS 4 @@ -234,7 +234,7 @@ .if n \{\ .RE .\} - Additional Options +Additional Options .sp .RS 4 .ie n \{\ @@ -481,7 +481,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/perror.1 mysql-5.5-5.5.43/man/perror.1 --- mysql-5.5-5.5.35+dfsg/man/perror.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/perror.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBperror\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBPERROR\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBPERROR\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -102,7 +102,7 @@ .RE .\} .PP -Note that the meaning of system error messages may be dependent on your operating system\&. A given error code may mean different things on different operating systems\&. +The meaning of system error messages may be dependent on your operating system\&. A given error code may mean different things on different operating systems\&. .PP \fBperror\fR supports the following options\&. @@ -190,7 +190,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/replace.1 mysql-5.5-5.5.43/man/replace.1 --- mysql-5.5-5.5.35+dfsg/man/replace.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/replace.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBreplace\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBREPLACE\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBREPLACE\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -169,7 +169,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/resolveip.1 mysql-5.5-5.5.43/man/resolveip.1 --- mysql-5.5-5.5.35+dfsg/man/resolveip.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/resolveip.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBresolveip\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBRESOLVEIP\FR" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBRESOLVEIP\FR" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -108,7 +108,7 @@ .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/man/resolve_stack_dump.1 mysql-5.5-5.5.43/man/resolve_stack_dump.1 --- mysql-5.5-5.5.35+dfsg/man/resolve_stack_dump.1 2013-11-05 07:19:32.000000000 +0000 +++ mysql-5.5-5.5.43/man/resolve_stack_dump.1 2015-02-27 08:30:42.000000000 +0000 @@ -1,13 +1,13 @@ '\" t .\" Title: \fBresolve_stack_dump\fR .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.77.1 -.\" Date: 11/04/2013 +.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Date: 02/26/2015 .\" Manual: MySQL Database System .\" Source: MySQL 5.5 .\" Language: English .\" -.TH "\FBRESOLVE_STACK_DUM" "1" "11/04/2013" "MySQL 5\&.5" "MySQL Database System" +.TH "\FBRESOLVE_STACK_DUM" "1" "02/26/2015" "MySQL 5\&.5" "MySQL Database System" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -125,11 +125,11 @@ .RE .PP For more information, see -Section\ \&23.4.1.5, \(lqUsing a Stack Trace\(rq\&. +Section\ \&24.4.1.5, \(lqUsing a Stack Trace\(rq\&. .SH "COPYRIGHT" .br .PP -Copyright \(co 1997, 2013, Oracle and/or its affiliates. All rights reserved. +Copyright \(co 1997, 2015, Oracle and/or its affiliates. All rights reserved. .PP This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. .PP diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/CMakeLists.txt mysql-5.5-5.5.43/mysql-test/CMakeLists.txt --- mysql-5.5-5.5.35+dfsg/mysql-test/CMakeLists.txt 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/CMakeLists.txt 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,4 @@ -# Copyright (c) 2009, 2012, Oracle and/or its affiliates. All rights reserved. +# Copyright (c) 2009, 2013, Oracle and/or its affiliates. All rights reserved. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/collections/default.experimental mysql-5.5-5.5.43/mysql-test/collections/default.experimental --- mysql-5.5-5.5.35+dfsg/mysql-test/collections/default.experimental 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/collections/default.experimental 2015-02-27 08:30:35.000000000 +0000 @@ -13,7 +13,6 @@ main.sp @solaris # Bug#11753919 2010-01-20 alik Several test cases fail on Solaris with error Thread stack overrun main.wait_timeout @solaris # Bug#11758972 2010-04-26 alik wait_timeout fails on OpenSolaris -rpl.rpl_innodb_bug28430 # Bug#11754425 rpl.rpl_row_sp011 @solaris # Bug#11753919 2011-07-25 sven Several test cases fail on Solaris with error Thread stack overrun rpl.rpl_spec_variables @solaris # Bug #17337114 2013-08-20 Luis Soares failing on pb2 with timeout for 'CHECK WARNINGS' diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/collections/default.release.done mysql-5.5-5.5.43/mysql-test/collections/default.release.done --- mysql-5.5-5.5.35+dfsg/mysql-test/collections/default.release.done 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/collections/default.release.done 2015-02-27 08:30:35.000000000 +0000 @@ -1 +1 @@ -/export/home/pb2/build/sb_0-10701388-1383635700.2/mysql-5.5.35-release-export-5938259_gpl/mysql-test/collections/default.release.in +/export/home/pb2/build/sb_0-14562198-1425025410.01/mysql-5.5.43-release-export-7658734_gpl/mysql-test/collections/default.release.in diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/collections/default.weekly mysql-5.5-5.5.43/mysql-test/collections/default.weekly --- mysql-5.5-5.5.35+dfsg/mysql-test/collections/default.weekly 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/collections/default.weekly 2015-02-27 08:30:35.000000000 +0000 @@ -5,3 +5,6 @@ perl mysql-test-run.pl --timer --force --debug-server --parallel=auto --comment=eits-tests-innodb-engine --experimental=collections/default.experimental --vardir=var-stmt-eits-tests-innodb-engine --suite=engines/iuds,engines/funcs --suite-timeout=500 --max-test-fail=0 --retry-failure=0 --mysqld=--default-storage-engine=innodb --mysqld=--innodb --skip-test-list=collections/disabled-weekly.list perl mysql-test-run.pl --timer --force --debug-server --parallel=auto --comment=eits-rpl-binlog-row-tests-innodb-engine --experimental=collections/default.experimental --vardir=var-binlog-row-eits-tests-innodb-engine --suite=engines/iuds,engines/funcs --suite-timeout=500 --max-test-fail=0 --retry-failure=0 --mysqld=--default-storage-engine=innodb --mysqld=--innodb --do-test=rpl --mysqld=--binlog-format=row --skip-test-list=collections/disabled-weekly.list perl mysql-test-run.pl --timer --force --debug-server --parallel=auto --comment=eits-rpl-binlog-mixed-tests-innodb-engine --experimental=collections/default.experimental --vardir=var-binlog-mixed-eits-tests-innodb-engine --suite=engines/iuds,engines/funcs --suite-timeout=500 --max-test-fail=0 --retry-failure=0 --mysqld=--default-storage-engine=innodb --mysqld=--innodb --do-test=rpl --mysqld=--binlog-format=mixed --skip-test-list=collections/disabled-weekly.list + +# Run innodb compression tests +perl mysql-test-run.pl --force --debug-server --comment=innodb_compression --vardir=var-innodb-zip --big-test --testcase-timeout=60 --parallel=auto --experimental=collections/default.experimental --suite=innodb_zip diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/extra/binlog_tests/database.test mysql-5.5-5.5.43/mysql-test/extra/binlog_tests/database.test --- mysql-5.5-5.5.35+dfsg/mysql-test/extra/binlog_tests/database.test 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/extra/binlog_tests/database.test 2015-02-27 08:30:35.000000000 +0000 @@ -31,12 +31,47 @@ FLUSH STATUS; +--echo +--echo # 'DROP TABLE IF EXISTS ' is binlogged +--echo # when 'DROP DATABASE' fails and at least one table is deleted +--echo # from the database. +RESET MASTER; +CREATE DATABASE testing_1; +USE testing_1; +CREATE TABLE t1(c1 INT); +CREATE TABLE t2(c1 INT); + +let $prefix= `SELECT UUID()`; +--echo # Create a file in the database directory +--replace_result $prefix FAKE_FILE +eval SELECT 'hello' INTO OUTFILE 'fake_file.$prefix'; + +--echo +--echo # 'DROP DATABASE' will fail if there is any other file in the the +--echo # database directory + +# Use '/' instead of '\' in the error message. On windows platform, dir is +# formed with '\'. +--replace_regex /\\testing_1\\*/\/testing_1\// +--error 1010 +DROP DATABASE testing_1; +let $wait_binlog_event= DROP TABLE IF EXIST; +source include/wait_for_binlog_event.inc; +let $MYSQLD_DATADIR= `SELECT @@datadir`; + +--echo +--echo # Remove the fake file. +--remove_file $MYSQLD_DATADIR/testing_1/fake_file.$prefix +--echo # Now we can drop the database. +DROP DATABASE testing_1; + --echo # --echo # Bug#11765416 58381: FAILED DROP DATABASE CAN BREAK STATEMENT --echo # BASED REPLICATION --echo # +USE test; --disable_warnings DROP DATABASE IF EXISTS db1; DROP TABLE IF EXISTS t3; diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/extra/rpl_tests/rpl_stop_slave.test mysql-5.5-5.5.43/mysql-test/extra/rpl_tests/rpl_stop_slave.test --- mysql-5.5-5.5.35+dfsg/mysql-test/extra/rpl_tests/rpl_stop_slave.test 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/extra/rpl_tests/rpl_stop_slave.test 2015-02-27 08:30:35.000000000 +0000 @@ -42,6 +42,10 @@ connection slave1; --echo # To resume slave SQL thread SET DEBUG_SYNC= 'now SIGNAL signal.continue'; +# wait for the sql thread to come out of the +# waiting phase before resetting the signals +--let $wait_condition= select count(*)=0 from information_schema.processlist where state LIKE '%debug sync point%' and info LIKE '%INSERT INTO t1 VALUES (1)%' +--source include/wait_condition.inc SET DEBUG_SYNC= 'RESET'; --echo diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/include/ctype_filesort2.inc mysql-5.5-5.5.43/mysql-test/include/ctype_filesort2.inc --- mysql-5.5-5.5.35+dfsg/mysql-test/include/ctype_filesort2.inc 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/include/ctype_filesort2.inc 2015-02-27 08:30:35.000000000 +0000 @@ -14,3 +14,12 @@ ALTER TABLE t1 ADD KEY(a); SELECT HEX(a), HEX(CONVERT(a USING utf8mb4)) FROM t1 ORDER BY a; DROP TABLE IF EXISTS t1; +--echo # +--echo # BUG#16691598 - ORDER BY LOWER(COLUMN) PRODUCES +--echo # OUT-OF-ORDER RESULTS +--echo # +CREATE TABLE t1 SELECT ('a a') as n; +INSERT INTO t1 VALUES('a b'); +SELECT * FROM t1 ORDER BY LOWER(n) ASC; +SELECT * FROM t1 ORDER BY LOWER(n) DESC; +DROP TABLE t1; diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/include/default_my.cnf mysql-5.5-5.5.43/mysql-test/include/default_my.cnf --- mysql-5.5-5.5.35+dfsg/mysql-test/include/default_my.cnf 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/include/default_my.cnf 2015-02-27 08:30:35.000000000 +0000 @@ -1,4 +1,5 @@ # Copyright (c) 2007 MySQL AB, 2009, 2010 Sun Microsystems, Inc. +# Use is subject to license terms # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/include/have_perfschema.inc mysql-5.5-5.5.43/mysql-test/include/have_perfschema.inc --- mysql-5.5-5.5.35+dfsg/mysql-test/include/have_perfschema.inc 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/include/have_perfschema.inc 2015-02-27 08:30:35.000000000 +0000 @@ -1,4 +1,5 @@ # Copyright (C) 2010 Sun Microsystems, Inc. +# Use is subject to license terms # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/include/mtr_check.sql mysql-5.5-5.5.43/mysql-test/include/mtr_check.sql --- mysql-5.5-5.5.35+dfsg/mysql-test/include/mtr_check.sql 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/include/mtr_check.sql 2015-02-27 08:30:35.000000000 +0000 @@ -1,4 +1,4 @@ --- Copyright (c) 2008, 2011, Oracle and/or its affiliates. All rights reserved. +-- Copyright (c) 2008, 2013, Oracle and/or its affiliates. All rights reserved. -- -- This program is free software; you can redistribute it and/or modify -- it under the terms of the GNU General Public License as published by @@ -52,6 +52,16 @@ WHERE table_schema='mysql' AND table_name != 'ndb_apply_status' ORDER BY columns_in_mysql; + -- Dump all events, there should be none + SELECT * FROM INFORMATION_SCHEMA.EVENTS; + -- Dump all triggers except mtr internals, there should be none + SELECT * FROM INFORMATION_SCHEMA.TRIGGERS + WHERE TRIGGER_NAME NOT IN ('gs_insert', 'ts_insert'); + -- Dump all created procedures, there should be none + SELECT * FROM INFORMATION_SCHEMA.ROUTINES; + + SHOW STATUS LIKE 'slave_open_temp_tables'; + -- Checksum system tables to make sure they have been properly -- restored after test checksum table @@ -72,8 +82,6 @@ mysql.time_zone_transition_type, mysql.user; - show status like 'slave_open_temp_tables'; - END|| -- diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/include/stop_dump_threads.inc mysql-5.5-5.5.43/mysql-test/include/stop_dump_threads.inc --- mysql-5.5-5.5.35+dfsg/mysql-test/include/stop_dump_threads.inc 1970-01-01 00:00:00.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/include/stop_dump_threads.inc 2015-02-27 08:30:35.000000000 +0000 @@ -0,0 +1,32 @@ +# ==== Purpose ==== +# +# Stop all dump threads on the server of the current connection. +# +# ==== Usage ==== +# +# --source include/stop_dump_threads.inc + +--let $include_filename= stop_dump_threads.inc +--source include/begin_include_file.inc + + +--let $_sdt_show_rpl_debug_info_old= $show_rpl_debug_info +--let $show_rpl_debug_info= 1 +--disable_query_log +--disable_result_log + +--let $_sdt_dump_thread_id= `SELECT ID FROM INFORMATION_SCHEMA.PROCESSLIST WHERE COMMAND = 'Binlog dump'` + +while ($_sdt_dump_thread_id != '') +{ + eval KILL $_sdt_dump_thread_id; + --let $wait_condition= SELECT COUNT(*) = 0 FROM INFORMATION_SCHEMA.PROCESSLIST WHERE ID = $_sdt_dump_thread_id + --source include/wait_condition.inc + + --let $_sdt_dump_thread_id= `SELECT ID FROM INFORMATION_SCHEMA.PROCESSLIST WHERE COMMAND = 'Binlog dump'` +} + +--let $show_rpl_debug_info= $_sdt_show_rpl_debug_info_old + +--let $include_filename= stop_dump_threads.inc +--source include/end_include_file.inc diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/include/uninstall_semisync.inc mysql-5.5-5.5.43/mysql-test/include/uninstall_semisync.inc --- mysql-5.5-5.5.35+dfsg/mysql-test/include/uninstall_semisync.inc 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/include/uninstall_semisync.inc 2015-02-27 08:30:35.000000000 +0000 @@ -13,6 +13,11 @@ UNINSTALL PLUGIN rpl_semi_sync_slave; --connection master +# After BUG#17638477 fix, uninstallation of rpl_semi_sync_master +# is not allowed when there are semi sync slaves. Hence kill +# all dump threads before uninstalling it. +SET GLOBAL rpl_semi_sync_master_enabled = OFF; +--source include/stop_dump_threads.inc UNINSTALL PLUGIN rpl_semi_sync_master; --enable_warnings diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/lib/mtr_match.pm mysql-5.5-5.5.43/mysql-test/lib/mtr_match.pm --- mysql-5.5-5.5.35+dfsg/mysql-test/lib/mtr_match.pm 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/lib/mtr_match.pm 2015-02-27 08:30:35.000000000 +0000 @@ -1,5 +1,6 @@ # -*- cperl -*- # Copyright (C) 2004-2008 MySQL AB +# Use is subject to license terms # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/lib/My/SafeProcess/safe_process.cc mysql-5.5-5.5.43/mysql-test/lib/My/SafeProcess/safe_process.cc --- mysql-5.5-5.5.35+dfsg/mysql-test/lib/My/SafeProcess/safe_process.cc 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/lib/My/SafeProcess/safe_process.cc 2015-02-27 08:30:35.000000000 +0000 @@ -1,4 +1,4 @@ -/* Copyright (c) 2008, 2011, Oracle and/or its affiliates. All rights reserved. +/* Copyright (c) 2008, 2012, Oracle and/or its affiliates. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/lib/My/SysInfo.pm mysql-5.5-5.5.43/mysql-test/lib/My/SysInfo.pm --- mysql-5.5-5.5.35+dfsg/mysql-test/lib/My/SysInfo.pm 2013-11-05 07:19:26.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/lib/My/SysInfo.pm 2015-02-27 08:30:35.000000000 +0000 @@ -1,6 +1,5 @@ # -*- cperl -*- -# Copyright (c) 2013 MySQL AB, 2008 Sun Microsystems, Inc. -# Use is subject to license terms. +# Copyright (c) 2008, 2013, Oracle and/or its affiliates. All rights reserved. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/mysql-test-run.pl mysql-5.5-5.5.43/mysql-test/mysql-test-run.pl --- mysql-5.5-5.5.35+dfsg/mysql-test/mysql-test-run.pl 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/mysql-test-run.pl 2015-02-27 08:30:34.000000000 +0000 @@ -1,7 +1,7 @@ #!/usr/bin/perl # -*- cperl -*- -# Copyright (c) 2004, 2013, Oracle and/or its affiliates. All rights reserved. +# Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -163,7 +163,7 @@ # If you add a new suite, please check TEST_DIRS in Makefile.am. # -my $DEFAULT_SUITES= "main,sys_vars,binlog,federated,rpl,innodb,perfschema"; +my $DEFAULT_SUITES= "main,sys_vars,binlog,federated,rpl,innodb,innodb_zip,perfschema"; my $opt_suites; our $opt_verbose= 0; # Verbose output, enable with --verbose @@ -232,6 +232,7 @@ our $opt_client_ddd; my $opt_boot_ddd; our $opt_manual_gdb; +our $opt_manual_lldb; our $opt_manual_dbx; our $opt_manual_ddd; our $opt_manual_debug; @@ -417,7 +418,6 @@ ); mtr_error("Could not create testcase server port: $!") unless $server; my $server_port = $server->sockport(); - mtr_report("Using server port $server_port"); if ($opt_resfile) { resfile_init("$opt_vardir/mtr-results.txt"); @@ -475,15 +475,17 @@ # Send Ctrl-C to any children still running kill("INT", keys(%children)); - # Wait for childs to exit - foreach my $pid (keys %children) - { - my $ret_pid= waitpid($pid, 0); - if ($ret_pid != $pid){ - mtr_report("Unknown process $ret_pid exited"); - } - else { - delete $children{$ret_pid}; + if (!IS_WINDOWS) { + # Wait for children to exit + foreach my $pid (keys %children) + { + my $ret_pid= waitpid($pid, 0); + if ($ret_pid != $pid){ + mtr_report("Unknown process $ret_pid exited"); + } + else { + delete $children{$ret_pid}; + } } } @@ -1085,6 +1087,7 @@ 'gdb' => \$opt_gdb, 'client-gdb' => \$opt_client_gdb, 'manual-gdb' => \$opt_manual_gdb, + 'manual-lldb' => \$opt_manual_lldb, 'boot-gdb' => \$opt_boot_gdb, 'manual-debug' => \$opt_manual_debug, 'ddd' => \$opt_ddd, @@ -1535,8 +1538,9 @@ $opt_debugger= undef; } - if ( $opt_gdb || $opt_ddd || $opt_manual_gdb || $opt_manual_ddd || - $opt_manual_debug || $opt_debugger || $opt_dbx || $opt_manual_dbx) + if ( $opt_gdb || $opt_ddd || $opt_manual_gdb || $opt_manual_lldb || + $opt_manual_ddd || $opt_manual_debug || $opt_debugger || $opt_dbx || + $opt_manual_dbx) { mtr_error("You need to use the client debug options for the", "embedded server. Ex: --client-gdb"); @@ -1562,9 +1566,9 @@ # -------------------------------------------------------------------------- # Check debug related options # -------------------------------------------------------------------------- - if ( $opt_gdb || $opt_client_gdb || $opt_ddd || $opt_client_ddd || - $opt_manual_gdb || $opt_manual_ddd || $opt_manual_debug || - $opt_dbx || $opt_client_dbx || $opt_manual_dbx || + if ( $opt_gdb || $opt_client_gdb || $opt_ddd || $opt_client_ddd || + $opt_manual_gdb || $opt_manual_lldb || $opt_manual_ddd || + $opt_manual_debug || $opt_dbx || $opt_client_dbx || $opt_manual_dbx || $opt_debugger || $opt_client_debugger ) { # Indicate that we are using debugger @@ -2457,6 +2461,14 @@ "$path_client_bindir/perror"); $ENV{'MY_PERROR'}= native_path($exe_perror); + # ---------------------------------------------------- + # replace + # ---------------------------------------------------- + my $exe_replace= mtr_exe_exists(vs_config_dirs('extra', 'replace'), + "$basedir/extra/replace", + "$path_client_bindir/replace"); + $ENV{'REPLACE'}= native_path($exe_replace); + # Create an environment variable to make it possible # to detect that valgrind is being used from test cases $ENV{'VALGRIND_TEST'}= $opt_valgrind; @@ -4984,6 +4996,10 @@ { gdb_arguments(\$args, \$exe, $mysqld->name()); } + elsif ( $opt_manual_lldb ) + { + lldb_arguments(\$args, \$exe, $mysqld->name()); + } elsif ( $opt_ddd || $opt_manual_ddd ) { ddd_arguments(\$args, \$exe, $mysqld->name()); @@ -5676,6 +5692,24 @@ return $proc; } +sub create_debug_statement { + my $args= shift; + my $input= shift; + + # Put $args into a single string + my $str= join(" ", @$$args); + my $runline= $input ? "run $str < $input" : "run $str"; + + # add quotes to escape ; in plugin_load option + my $pos1 = index($runline, "--plugin_load="); + if ( $pos1 != -1 ) { + my $pos2 = index($runline, " ",$pos1); + substr($runline,$pos1+14,0) = "\""; + substr($runline,$pos2+1,0) = "\""; + } + + return $runline; +} # # Modify the exe and args so that program is run in gdb in xterm @@ -5691,9 +5725,7 @@ # Remove the old gdbinit file unlink($gdb_init_file); - # Put $args into a single string - my $str= join(" ", @$$args); - my $runline= $input ? "run $str < $input" : "run $str"; + my $runline=create_debug_statement($args,$input); # write init file for mysqld or client mtr_tofile($gdb_init_file, @@ -5729,6 +5761,32 @@ $$exe= "xterm"; } + # +# Modify the exe and args so that program is run in lldb +# +sub lldb_arguments { + my $args= shift; + my $exe= shift; + my $type= shift; + my $input= shift; + + my $lldb_init_file= "$opt_vardir/tmp/lldbinit.$type"; + unlink($lldb_init_file); + + my $runline=create_debug_statement($args,$input); + + # write init file for mysqld or client + mtr_tofile($lldb_init_file, + "b main\n" . + $runline); + + print "\nTo start lldb for $type, type in another window:\n"; + print "cd $glob_mysql_test_dir && lldb -s $lldb_init_file $$exe\n"; + + # Indicate the exe should not be started + $$exe= undef; + return; +} # # Modify the exe and args so that program is run in ddd @@ -5744,9 +5802,7 @@ # Remove the old gdbinit file unlink($gdb_init_file); - # Put $args into a single string - my $str= join(" ", @$$args); - my $runline= $input ? "run $str < $input" : "run $str"; + my $runline=create_debug_statement($args,$input); # write init file for mysqld or client mtr_tofile($gdb_init_file, @@ -6189,6 +6245,8 @@ test(s) manual-dbx Let user manually start mysqld in dbx, before running test(s) + manual-lldb Let user manually start mysqld in lldb, before running + test(s) strace-client Create strace output for mysqltest client, strace-server Create strace output for mysqltest server, max-save-core Limit the number of core files saved (to avoid filling diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/purify.supp mysql-5.5-5.5.43/mysql-test/purify.supp --- mysql-5.5-5.5.35+dfsg/mysql-test/purify.supp 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/purify.supp 2015-02-27 08:30:34.000000000 +0000 @@ -1,4 +1,5 @@ # Copyright (C) 2005, 2007 MySQL AB +# Use is subject to license terms # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU Library General Public diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/create.result mysql-5.5-5.5.43/mysql-test/r/create.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/create.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/create.result 2015-02-27 08:30:35.000000000 +0000 @@ -291,7 +291,7 @@ Note 1050 Table 't1' already exists show status like "Opened_tables"; Variable_name Value -Opened_tables 2 +Opened_tables 1 select * from t1; a b 1 1 diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/ctype_cp932.result mysql-5.5-5.5.43/mysql-test/r/ctype_cp932.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/ctype_cp932.result 1970-01-01 00:00:00.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/ctype_cp932.result 2015-02-27 08:30:35.000000000 +0000 @@ -0,0 +1,35 @@ +# +# Bug #11755818 LIKE DOESN'T MATCH WHEN CP932_BIN/SJIS_BIN COLLATIONS ARE +# USED. +# +SET @old_character_set_client= @@character_set_client; +SET @old_character_set_connection= @@character_set_connection; +SET @old_character_set_results= @@character_set_results; +SET character_set_client= 'utf8'; +SET character_set_connection= 'utf8'; +SET character_set_results= 'utf8'; +CREATE TABLE t1 (a VARCHAR(10) COLLATE cp932_bin); +INSERT INTO t1 VALUES('カカ'); +SELECT * FROM t1 WHERE a LIKE '%カ'; +a +カカ +SELECT * FROM t1 WHERE a LIKE '_カ'; +a +カカ +SELECT * FROM t1 WHERE a LIKE '%_カ'; +a +カカ +ALTER TABLE t1 MODIFY a VARCHAR(100) COLLATE sjis_bin; +SELECT * FROM t1 WHERE a LIKE '%カ'; +a +カカ +SELECT * FROM t1 WHERE a LIKE '_カ'; +a +カカ +SELECT * FROM t1 WHERE a LIKE '%_カ'; +a +カカ +DROP TABLE t1; +SET @@character_set_client= @old_character_set_client; +SET @@character_set_connection= @old_character_set_connection; +SET @@character_set_results= @old_character_set_results; diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/ctype_utf16.result mysql-5.5-5.5.43/mysql-test/r/ctype_utf16.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/ctype_utf16.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/ctype_utf16.result 2015-02-27 08:30:35.000000000 +0000 @@ -636,6 +636,21 @@ D800DF84 F0908E84 DBC0DC00 F4808080 DROP TABLE IF EXISTS t1; +# +# BUG#16691598 - ORDER BY LOWER(COLUMN) PRODUCES +# OUT-OF-ORDER RESULTS +# +CREATE TABLE t1 SELECT ('a a') as n; +INSERT INTO t1 VALUES('a b'); +SELECT * FROM t1 ORDER BY LOWER(n) ASC; +n +a a +a b +SELECT * FROM t1 ORDER BY LOWER(n) DESC; +n +a b +a a +DROP TABLE t1; select @@collation_connection; @@collation_connection utf16_bin diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/ctype_utf32.result mysql-5.5-5.5.43/mysql-test/r/ctype_utf32.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/ctype_utf32.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/ctype_utf32.result 2015-02-27 08:30:35.000000000 +0000 @@ -635,6 +635,21 @@ 00010384 F0908E84 00100000 F4808080 DROP TABLE IF EXISTS t1; +# +# BUG#16691598 - ORDER BY LOWER(COLUMN) PRODUCES +# OUT-OF-ORDER RESULTS +# +CREATE TABLE t1 SELECT ('a a') as n; +INSERT INTO t1 VALUES('a b'); +SELECT * FROM t1 ORDER BY LOWER(n) ASC; +n +a a +a b +SELECT * FROM t1 ORDER BY LOWER(n) DESC; +n +a b +a a +DROP TABLE t1; select @@collation_connection; @@collation_connection utf32_bin diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/ctype_utf8mb4.result mysql-5.5-5.5.43/mysql-test/r/ctype_utf8mb4.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/ctype_utf8mb4.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/ctype_utf8mb4.result 2015-02-27 08:30:35.000000000 +0000 @@ -1012,6 +1012,21 @@ F0908E84 F0908E84 F4808080 F4808080 DROP TABLE IF EXISTS t1; +# +# BUG#16691598 - ORDER BY LOWER(COLUMN) PRODUCES +# OUT-OF-ORDER RESULTS +# +CREATE TABLE t1 SELECT ('a a') as n; +INSERT INTO t1 VALUES('a b'); +SELECT * FROM t1 ORDER BY LOWER(n) ASC; +n +a a +a b +SELECT * FROM t1 ORDER BY LOWER(n) DESC; +n +a b +a a +DROP TABLE t1; select @@collation_connection; @@collation_connection utf8mb4_bin diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/distinct.result mysql-5.5-5.5.43/mysql-test/r/distinct.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/distinct.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/distinct.result 2015-02-27 08:30:35.000000000 +0000 @@ -804,4 +804,44 @@ 11112222 33334444 DROP TABLE t1; +# +# Bug#16539979 BASIC SELECT COUNT(DISTINCT ID) IS BROKEN. +# Bug#17867117 ERROR RESULT WHEN "COUNT + DISTINCT + CASE WHEN" NEED MERGE_WALK +# +SET @tmp_table_size_save= @@tmp_table_size; +SET @@tmp_table_size= 1024; +CREATE TABLE t1 (a INT); +INSERT INTO t1 VALUES (1),(2),(3),(4),(5),(6),(7),(8); +INSERT INTO t1 SELECT a+8 FROM t1; +INSERT INTO t1 SELECT a+16 FROM t1; +INSERT INTO t1 SELECT a+32 FROM t1; +INSERT INTO t1 SELECT a+64 FROM t1; +INSERT INTO t1 VALUE(NULL); +SELECT COUNT(DISTINCT a) FROM t1; +COUNT(DISTINCT a) +128 +SELECT COUNT(DISTINCT (a+0)) FROM t1; +COUNT(DISTINCT (a+0)) +128 +DROP TABLE t1; +create table tb( +id int auto_increment primary key, +v varchar(32)) +engine=myisam charset=gbk; +insert into tb(v) values("aaa"); +insert into tb(v) (select v from tb); +insert into tb(v) (select v from tb); +insert into tb(v) (select v from tb); +insert into tb(v) (select v from tb); +insert into tb(v) (select v from tb); +insert into tb(v) (select v from tb); +update tb set v=concat(v, id); +select count(distinct case when id<=64 then id end) from tb; +count(distinct case when id<=64 then id end) +64 +select count(distinct case when id<=63 then id end) from tb; +count(distinct case when id<=63 then id end) +63 +drop table tb; +SET @@tmp_table_size= @tmp_table_size_save; End of 5.5 tests diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/error_simulation.result mysql-5.5-5.5.43/mysql-test/r/error_simulation.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/error_simulation.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/error_simulation.result 2015-02-27 08:30:35.000000000 +0000 @@ -98,3 +98,22 @@ # # End of 5.1 tests # +# +# BUG#11747548:DETECT ORPHAN TEMP-POOL FILES, AND HANDLE GRACEFULLY. +# +#Set up. +CREATE TABLE pid_table(pid_no INT); +CREATE TABLE t1 (a BLOB); +INSERT INTO t1 VALUES (1), (2); +#Create MYD and MYI files for intrinsic temp table. +LOAD DATA LOCAL INFILE 'pid_file' INTO TABLE pid_table; +#Reports an error since the temp file already exists. +SELECT a FROM t1 ORDER BY rand(1); +ERROR HY000: Can't create or write to file +#With patch, the query executes successfully. +SELECT a FROM t1 ORDER BY rand(1); +a +1 +2 +#cleanup +DROP TABLE t1, pid_table; diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/events_trans.result mysql-5.5-5.5.43/mysql-test/r/events_trans.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/events_trans.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/events_trans.result 2015-02-27 08:30:35.000000000 +0000 @@ -135,3 +135,4 @@ a ROLLBACK WORK TO SAVEPOINT A; DROP TABLE t1, t2; +DROP EVENT e1; diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/file_contents.result mysql-5.5-5.5.43/mysql-test/r/file_contents.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/file_contents.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/file_contents.result 2015-02-27 08:30:35.000000000 +0000 @@ -1,6 +1,6 @@ Checking 'INFO_SRC' and 'INFO_BIN' -INFO_SRC: Found MySQL version number / Found BZR revision id +INFO_SRC: Found MySQL version number / Found GIT revision id INFO_BIN: Found 'Compiler ... used' line / Found 'Feature flags' line End of tests diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/gis.result mysql-5.5-5.5.43/mysql-test/r/gis.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/gis.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/gis.result 2015-02-27 08:30:35.000000000 +0000 @@ -1113,4 +1113,25 @@ (SELECT 1 FROM g1 WHERE a = geomfromtext('') OR a) ; 1 DROP TABLE g1; +# +# Bug#16451878 GEOMETRY QUERY CRASHES SERVER +# +# should not crash +SELECT ASTEXT(0x0100000000030000000100000000000010); +ASTEXT(0x0100000000030000000100000000000010) +NULL +#should not crash +SELECT ENVELOPE(0x0100000000030000000100000000000010); +ENVELOPE(0x0100000000030000000100000000000010) +NULL +#should not crash +SELECT +GEOMETRYN(0x0100000000070000000100000001030000000200000000000000ffff0000, 1); +GEOMETRYN(0x0100000000070000000100000001030000000200000000000000ffff0000, 1) +NULL +#should not crash +SELECT +GEOMETRYN(0x0100000000070000000100000001030000000200000000000000ffffff0f, 1); +GEOMETRYN(0x0100000000070000000100000001030000000200000000000000ffffff0f, 1) +NULL End of 5.5 tests diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/group_min_max_innodb.result mysql-5.5-5.5.43/mysql-test/r/group_min_max_innodb.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/group_min_max_innodb.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/group_min_max_innodb.result 2015-02-27 08:30:35.000000000 +0000 @@ -118,3 +118,171 @@ 1 DROP TABLE t1; End of 5.5 tests +# +# Bug#17909656 - WRONG RESULTS FOR A SIMPLE QUERY WITH GROUP BY +# +CREATE TABLE t0 ( +i1 INTEGER NOT NULL +); +INSERT INTO t0 VALUES (1),(2),(3),(4),(5),(6),(7),(8),(9),(10), +(11),(12),(13),(14),(15),(16),(17),(18),(19),(20), +(21),(22),(23),(24),(25),(26),(27),(28),(29),(30); +CREATE TABLE t1 ( +c1 CHAR(1) NOT NULL, +i1 INTEGER NOT NULL, +i2 INTEGER NOT NULL, +UNIQUE KEY k1 (c1,i2) +) ENGINE=InnoDB; +INSERT INTO t1 SELECT 'A',i1,i1 FROM t0; +INSERT INTO t1 SELECT 'B',i1,i1 FROM t0; +INSERT INTO t1 SELECT 'C',i1,i1 FROM t0; +INSERT INTO t1 SELECT 'D',i1,i1 FROM t0; +INSERT INTO t1 SELECT 'E',i1,i1 FROM t0; +INSERT INTO t1 SELECT 'F',i1,i1 FROM t0; +CREATE TABLE t2 ( +c1 CHAR(1) NOT NULL, +i1 INTEGER NOT NULL, +i2 INTEGER NOT NULL, +UNIQUE KEY k2 (c1,i1,i2) +) ENGINE=InnoDB; +INSERT INTO t2 SELECT 'A',i1,i1 FROM t0; +INSERT INTO t2 SELECT 'B',i1,i1 FROM t0; +INSERT INTO t2 SELECT 'C',i1,i1 FROM t0; +INSERT INTO t2 SELECT 'D',i1,i1 FROM t0; +INSERT INTO t2 SELECT 'E',i1,i1 FROM t0; +INSERT INTO t2 SELECT 'F',i1,i1 FROM t0; +ANALYZE TABLE t1; +ANALYZE TABLE t2; +EXPLAIN SELECT c1, max(i2) FROM t1 WHERE (c1 = 'C' AND i2 = 17) OR ( c1 = 'F') +GROUP BY c1; +id select_type table type possible_keys key key_len ref rows Extra +1 SIMPLE t1 range k1 k1 5 NULL 31 Using where; Using index +SELECT c1, max(i2) FROM t1 WHERE (c1 = 'C' AND i2 = 17) OR ( c1 = 'F') +GROUP BY c1; +c1 max(i2) +C 17 +F 30 +EXPLAIN SELECT c1, max(i2) FROM t1 WHERE (c1 = 'C' OR ( c1 = 'F' AND i2 = 17)) +GROUP BY c1; +id select_type table type possible_keys key key_len ref rows Extra +1 SIMPLE t1 range k1 k1 5 NULL 31 Using where; Using index +SELECT c1, max(i2) FROM t1 WHERE (c1 = 'C' OR ( c1 = 'F' AND i2 = 17)) +GROUP BY c1; +c1 max(i2) +C 30 +F 17 +EXPLAIN SELECT c1, max(i2) FROM t1 WHERE (c1 = 'C' OR c1 = 'F' ) AND ( i2 = 17 ) +GROUP BY c1; +id select_type table type possible_keys key key_len ref rows Extra +1 SIMPLE t1 range k1 k1 5 NULL 1 Using where; Using index for group-by +SELECT c1, max(i2) FROM t1 WHERE (c1 = 'C' OR c1 = 'F' ) AND ( i2 = 17 ) +GROUP BY c1; +c1 max(i2) +C 17 +F 17 +EXPLAIN SELECT c1, max(i2) FROM t1 +WHERE ((c1 = 'C' AND (i2 = 40 OR i2 = 30)) OR ( c1 = 'F' AND (i2 = 40 ))) +GROUP BY c1; +id select_type table type possible_keys key key_len ref rows Extra +1 SIMPLE t1 range k1 k1 5 NULL 3 Using where; Using index +SELECT c1, max(i2) FROM t1 +WHERE ((c1 = 'C' AND (i2 = 40 OR i2 = 30)) OR ( c1 = 'F' AND (i2 = 40 ))) +GROUP BY c1; +c1 max(i2) +C 30 +EXPLAIN SELECT c1, i1, max(i2) FROM t2 +WHERE (c1 = 'C' OR ( c1 = 'F' AND i1 < 35)) AND ( i2 = 17 ) +GROUP BY c1,i1; +id select_type table type possible_keys key key_len ref rows Extra +1 SIMPLE t2 range k2 k2 9 NULL 59 Using where; Using index for group-by +SELECT c1, i1, max(i2) FROM t2 +WHERE (c1 = 'C' OR ( c1 = 'F' AND i1 < 35)) AND ( i2 = 17 ) +GROUP BY c1,i1; +c1 i1 max(i2) +C 17 17 +F 17 17 +EXPLAIN SELECT c1, i1, max(i2) FROM t2 +WHERE (((c1 = 'C' AND i1 < 40) OR ( c1 = 'F' AND i1 < 35)) AND ( i2 = 17 )) +GROUP BY c1,i1; +id select_type table type possible_keys key key_len ref rows Extra +1 SIMPLE t2 range k2 k2 9 NULL 58 Using where; Using index for group-by +SELECT c1, i1, max(i2) FROM t2 +WHERE (((c1 = 'C' AND i1 < 40) OR ( c1 = 'F' AND i1 < 35)) AND ( i2 = 17 )) +GROUP BY c1,i1; +c1 i1 max(i2) +C 17 17 +F 17 17 +EXPLAIN SELECT c1, i1, max(i2) FROM t2 +WHERE ((c1 = 'C' AND i1 < 40) OR ( c1 = 'F' AND i1 < 35) OR ( i2 = 17 )) +GROUP BY c1,i1; +id select_type table type possible_keys key key_len ref rows Extra +1 SIMPLE t2 range k2 k2 5 NULL 181 Using where; Using index for group-by +SELECT c1, i1, max(i2) FROM t2 +WHERE ((c1 = 'C' AND i1 < 40) OR ( c1 = 'F' AND i1 < 35) OR ( i2 = 17 )) +GROUP BY c1,i1; +c1 i1 max(i2) +A 17 17 +B 17 17 +C 1 1 +C 2 2 +C 3 3 +C 4 4 +C 5 5 +C 6 6 +C 7 7 +C 8 8 +C 9 9 +C 10 10 +C 11 11 +C 12 12 +C 13 13 +C 14 14 +C 15 15 +C 16 16 +C 17 17 +C 18 18 +C 19 19 +C 20 20 +C 21 21 +C 22 22 +C 23 23 +C 24 24 +C 25 25 +C 26 26 +C 27 27 +C 28 28 +C 29 29 +C 30 30 +D 17 17 +E 17 17 +F 1 1 +F 2 2 +F 3 3 +F 4 4 +F 5 5 +F 6 6 +F 7 7 +F 8 8 +F 9 9 +F 10 10 +F 11 11 +F 12 12 +F 13 13 +F 14 14 +F 15 15 +F 16 16 +F 17 17 +F 18 18 +F 19 19 +F 20 20 +F 21 21 +F 22 22 +F 23 23 +F 24 24 +F 25 25 +F 26 26 +F 27 27 +F 28 28 +F 29 29 +F 30 30 +DROP TABLE t0,t1,t2; diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/group_min_max.result mysql-5.5-5.5.43/mysql-test/r/group_min_max.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/group_min_max.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/group_min_max.result 2015-02-27 08:30:35.000000000 +0000 @@ -3001,7 +3001,7 @@ 0 NULL EXPLAIN SELECT SUM(DISTINCT a), MAX(b) FROM t2 GROUP BY a; id select_type table type possible_keys key key_len ref rows Extra -1 SIMPLE t2 range NULL a 5 NULL 9 Using index for group-by +1 SIMPLE t2 index NULL a 15 NULL 16 Using index SELECT SUM(DISTINCT a), MAX(b) FROM t2 GROUP BY a; SUM(DISTINCT a) MAX(b) 1 8 @@ -3029,7 +3029,7 @@ 168 EXPLAIN SELECT (SUM(DISTINCT a) + MAX(b)) FROM t2 GROUP BY a; id select_type table type possible_keys key key_len ref rows Extra -1 SIMPLE t2 range NULL a 5 NULL 9 Using index for group-by +1 SIMPLE t2 index NULL a 15 NULL 16 Using index SELECT (SUM(DISTINCT a) + MAX(b)) FROM t2 GROUP BY a; (SUM(DISTINCT a) + MAX(b)) 9 @@ -3057,3 +3057,55 @@ 1 SIMPLE t1 range NULL PRIMARY 5 NULL 9 Using index for group-by (scanning) drop table t1; # End of test#50539. +# +# Bug#17217128 - BAD INTERACTION BETWEEN MIN/MAX AND +# "HAVING SUM(DISTINCT)": WRONG RESULTS. +# +CREATE TABLE t (a INT, b INT, KEY(a,b)); +INSERT INTO t VALUES (1,1), (2,2), (3,3), (4,4), (1,0), (3,2), (4,5); +ANALYZE TABLE t; +Table Op Msg_type Msg_text +test.t analyze status OK +SELECT a, SUM(DISTINCT a), MIN(b) FROM t GROUP BY a; +a SUM(DISTINCT a) MIN(b) +1 1 0 +2 2 2 +3 3 2 +4 4 4 +EXPLAIN SELECT a, SUM(DISTINCT a), MIN(b) FROM t GROUP BY a; +id select_type table type possible_keys key key_len ref rows Extra +1 SIMPLE t index NULL a 10 NULL 7 Using index +SELECT a, SUM(DISTINCT a), MAX(b) FROM t GROUP BY a; +a SUM(DISTINCT a) MAX(b) +1 1 1 +2 2 2 +3 3 3 +4 4 5 +EXPLAIN SELECT a, SUM(DISTINCT a), MAX(b) FROM t GROUP BY a; +id select_type table type possible_keys key key_len ref rows Extra +1 SIMPLE t index NULL a 10 NULL 7 Using index +SELECT a, MAX(b) FROM t GROUP BY a HAVING SUM(DISTINCT a); +a MAX(b) +1 1 +2 2 +3 3 +4 5 +EXPLAIN SELECT a, MAX(b) FROM t GROUP BY a HAVING SUM(DISTINCT a); +id select_type table type possible_keys key key_len ref rows Extra +1 SIMPLE t index NULL a 10 NULL 7 Using index +SELECT SUM(DISTINCT a), MIN(b), MAX(b) FROM t; +SUM(DISTINCT a) MIN(b) MAX(b) +10 0 5 +EXPLAIN SELECT SUM(DISTINCT a), MIN(b), MAX(b) FROM t; +id select_type table type possible_keys key key_len ref rows Extra +1 SIMPLE t index NULL a 10 NULL 7 Using index +SELECT a, SUM(DISTINCT a), MIN(b), MAX(b) FROM t GROUP BY a; +a SUM(DISTINCT a) MIN(b) MAX(b) +1 1 0 1 +2 2 2 2 +3 3 2 3 +4 4 4 5 +EXPLAIN SELECT a, SUM(DISTINCT a), MIN(b), MAX(b) FROM t GROUP BY a; +id select_type table type possible_keys key key_len ref rows Extra +1 SIMPLE t index NULL a 10 NULL 7 Using index +DROP TABLE t; diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/have_cp1251.require mysql-5.5-5.5.43/mysql-test/r/have_cp1251.require --- mysql-5.5-5.5.35+dfsg/mysql-test/r/have_cp1251.require 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/have_cp1251.require 2015-02-27 08:30:35.000000000 +0000 @@ -1,2 +1,2 @@ Collation Charset Id Default Compiled Sortlen -cp1251_general_ci cp1251 51 Yes 0 +cp1251_general_ci cp1251 51 Yes Yes 1 diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/have_cp866.require mysql-5.5-5.5.43/mysql-test/r/have_cp866.require --- mysql-5.5-5.5.35+dfsg/mysql-test/r/have_cp866.require 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/have_cp866.require 2015-02-27 08:30:35.000000000 +0000 @@ -1,2 +1,2 @@ Collation Charset Id Default Compiled Sortlen -cp866_general_ci cp866 36 Yes 0 +cp866_general_ci cp866 36 Yes Yes 1 diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/have_koi8r.require mysql-5.5-5.5.43/mysql-test/r/have_koi8r.require --- mysql-5.5-5.5.35+dfsg/mysql-test/r/have_koi8r.require 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/have_koi8r.require 2015-02-27 08:30:35.000000000 +0000 @@ -1,2 +1,2 @@ Collation Charset Id Default Compiled Sortlen -koi8r_general_ci koi8r 7 Yes 0 +koi8r_general_ci koi8r 7 Yes Yes 1 diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/information_schema.result mysql-5.5-5.5.43/mysql-test/r/information_schema.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/information_schema.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/information_schema.result 2015-02-27 08:30:35.000000000 +0000 @@ -1965,5 +1965,20 @@ # Clean-up. drop database mysqltest; # +# Test for bug #16869534 - "QUERYING SUBSET OF COLUMNS DOESN'T USE TABLE +# CACHE; OPENED_TABLES INCREASES" +# +SELECT * FROM INFORMATION_SCHEMA.TABLES; +SELECT VARIABLE_VALUE INTO @val1 FROM INFORMATION_SCHEMA.GLOBAL_STATUS WHERE +VARIABLE_NAME LIKE 'Opened_tables'; +SELECT ENGINE FROM INFORMATION_SCHEMA.TABLES; +# The below SELECT query should give same output as above SELECT query. +SELECT VARIABLE_VALUE INTO @val2 FROM INFORMATION_SCHEMA.GLOBAL_STATUS WHERE +VARIABLE_NAME LIKE 'Opened_tables'; +# The below select should return '1' +SELECT @val1 = @val2; +@val1 = @val2 +1 +# # End of 5.5 tests # diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/loaddata.result mysql-5.5-5.5.43/mysql-test/r/loaddata.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/loaddata.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/loaddata.result 2015-02-27 08:30:35.000000000 +0000 @@ -520,3 +520,15 @@ ERROR 22003: Cannot get geometry object from data you send to the GEOMETRY field drop table t1; End of 5.1 tests +# +# Bug#11759519 INFINITE HANG WITH 100% CPU USAGE WITH LOAD DATA LOCAL AND IMPORT ERRORS +# +SET @old_mode= @@sql_mode; +CREATE TABLE t1 (fld1 INT); +SET sql_mode='strict_all_tables'; +# Without fix, load data hangs forever. +LOAD DATA LOCAL INFILE 'MYSQLTEST_VARDIR/mysql' REPLACE INTO TABLE t1 +FIELDS TERMINATED BY 't' LINES TERMINATED BY ''; +Got one of the listed errors +SET @@sql_mode= @old_mode; +DROP TABLE t1; diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/lock_sync.result mysql-5.5-5.5.43/mysql-test/r/lock_sync.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/lock_sync.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/lock_sync.result 2015-02-27 08:30:35.000000000 +0000 @@ -773,3 +773,54 @@ SET DEBUG_SYNC= 'RESET'; DROP VIEW v1; DROP TABLE t1; +# +# Bug#19070633 - POSSIBLE ACCESS TO FREED MEMORY IN IS_FREE_LOCK() AND IS_USED_LOCK(). +# +# Verifying issue for IS_FREE_LOCK() function. +SELECT GET_LOCK("lock_19070633", 600); +GET_LOCK("lock_19070633", 600) +1 +connect con1, localhost, root,,; +# Waiting after getting user level lock info and releasing mutex. +SET DEBUG_SYNC= 'after_getting_user_level_lock_info SIGNAL parked WAIT_FOR go'; +# Sending: SELECT IS_FREE_LOCK("lock_19070633"); +SELECT IS_FREE_LOCK("lock_19070633"); +connection default; +SET DEBUG_SYNC= 'now WAIT_FOR parked'; +SELECT RELEASE_LOCK("lock_19070633"); +RELEASE_LOCK("lock_19070633") +1 +# Signaling connection con1 after releasing the lock. +# Without fix, accessing user level lock info in con1 would result in +# crash or valgrind issue invalid read is reported. +SET DEBUG_SYNC= 'now SIGNAL go'; +connection con1; +# Reaping: SELECT IS_FREE_LOCK("lock_19070633"); +IS_FREE_LOCK("lock_19070633") +0 +connection default; +# Verifying issue for IS_USED_LOCK() function. +SELECT GET_LOCK("lock_19070633", 600); +GET_LOCK("lock_19070633", 600) +1 +connection con1; +# Waiting after getting user level lock info and releasing mutex. +SET DEBUG_SYNC= 'after_getting_user_level_lock_info SIGNAL parked WAIT_FOR go'; +# Sending: SELECT IS_USED_LOCK("lock_19070633"); +SELECT IS_USED_LOCK("lock_19070633"); +connection default; +SET DEBUG_SYNC= 'now WAIT_FOR parked'; +SELECT RELEASE_LOCK("lock_19070633"); +RELEASE_LOCK("lock_19070633") +1 +# Signaling connection con1 after releasing the lock. +# Without fix, accessing user level lock info in con1 would result in +# crash or valgrind issue invalid read is reported. +SET DEBUG_SYNC= 'now SIGNAL go'; +connection con1; +# Reaping: SELECT IS_USED_LOCK("lock_19070633"); +IS_USED_LOCK("lock_19070633") +# +connection default; +SET DEBUG_SYNC= 'RESET'; +disconnect con1; diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/log_errchk.result mysql-5.5-5.5.43/mysql-test/r/log_errchk.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/log_errchk.result 1970-01-01 00:00:00.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/log_errchk.result 2015-02-27 08:30:35.000000000 +0000 @@ -0,0 +1,10 @@ +call mtr.add_suppression("Could not use"); +# Case 1: Setting fife file to general_log_file and slow_query_log_file +# system variable. +SET GLOBAL general_log_file="MYSQLTEST_VARDIR/tmp/general_log.fifo";; +ERROR 42000: Variable 'general_log_file' can't be set to the value of 'MYSQLTEST_VARDIR/tmp/general_log.fifo' +SET GLOBAL slow_query_log_file="MYSQLTEST_VARDIR/tmp/slow_log.fifo";; +ERROR 42000: Variable 'slow_query_log_file' can't be set to the value of 'MYSQLTEST_VARDIR/tmp/slow_log.fifo' +# Case 2: Starting server with fifo file as general log file +# and slow query log file. +Setting fifo file as general log file and slow query log failed. diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/mysqld--help-notwin.result mysql-5.5-5.5.43/mysql-test/r/mysqld--help-notwin.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/mysqld--help-notwin.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/mysqld--help-notwin.result 2015-02-27 08:30:35.000000000 +0000 @@ -712,8 +712,8 @@ one-thread-per-connection, no-threads, loaded-dynamically --thread-stack=# The stack size for each thread --time-format=name The TIME format (ignored) - --timed-mutexes Specify whether to time mutexes (only InnoDB mutexes are - currently supported) + --timed-mutexes Specify whether to time mutexes. Deprecated, has no + effect. --tmp-table-size=# If an internal in-memory temporary table exceeds this size, MySQL will automatically convert it to an on-disk MyISAM table diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/mysqld--help-win.result mysql-5.5-5.5.43/mysql-test/r/mysqld--help-win.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/mysqld--help-win.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/mysqld--help-win.result 2015-02-27 08:30:35.000000000 +0000 @@ -720,8 +720,8 @@ one-thread-per-connection, no-threads, loaded-dynamically --thread-stack=# The stack size for each thread --time-format=name The TIME format (ignored) - --timed-mutexes Specify whether to time mutexes (only InnoDB mutexes are - currently supported) + --timed-mutexes Specify whether to time mutexes. Deprecated, has no + effect. --tmp-table-size=# If an internal in-memory temporary table exceeds this size, MySQL will automatically convert it to an on-disk MyISAM table diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/openssl_1.result mysql-5.5-5.5.43/mysql-test/r/openssl_1.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/openssl_1.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/openssl_1.result 2015-02-27 08:30:35.000000000 +0000 @@ -3,8 +3,8 @@ insert into t1 values (5); grant select on test.* to ssl_user1@localhost require SSL; grant select on test.* to ssl_user2@localhost require cipher "DHE-RSA-AES256-SHA"; -grant select on test.* to ssl_user3@localhost require cipher "DHE-RSA-AES256-SHA" AND SUBJECT "/C=SE/ST=Uppsala/O=MySQL AB"; -grant select on test.* to ssl_user4@localhost require cipher "DHE-RSA-AES256-SHA" AND SUBJECT "/C=SE/ST=Uppsala/O=MySQL AB" ISSUER "/C=SE/ST=Uppsala/L=Uppsala/O=MySQL AB"; +grant select on test.* to ssl_user3@localhost require cipher "DHE-RSA-AES256-SHA" AND SUBJECT "/C=SE/ST=Stockholm/L=Stockholm/O=Oracle/OU=MySQL/CN=Client"; +grant select on test.* to ssl_user4@localhost require cipher "DHE-RSA-AES256-SHA" AND SUBJECT "/C=SE/ST=Stockholm/L=Stockholm/O=Oracle/OU=MySQL/CN=Client" ISSUER "/C=SE/ST=Stockholm/L=Stockholm/O=Oracle/OU=MySQL/CN=CA"; grant select on test.* to ssl_user5@localhost require cipher "DHE-RSA-AES256-SHA" AND SUBJECT "xxx"; flush privileges; connect(localhost,ssl_user5,,test,MASTER_PORT,MASTER_SOCKET); diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/outfile_loaddata.result mysql-5.5-5.5.43/mysql-test/r/outfile_loaddata.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/outfile_loaddata.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/outfile_loaddata.result 2015-02-27 08:30:35.000000000 +0000 @@ -143,15 +143,16 @@ LOAD DATA INFILE 'MYSQLTEST_VARDIR/tmp/t1.txt' INTO TABLE t2 CHARACTER SET binary FIELDS TERMINATED BY 'ъ'; Warnings: Warning 1638 Non-ASCII separator arguments are not fully supported -Warning 1265 Data truncated for column 'a' at row 1 -Warning 1261 Row 1 doesn't contain data for all columns -Warning 1261 Row 1 doesn't contain data for all columns -Warning 1265 Data truncated for column 'a' at row 2 -Warning 1261 Row 2 doesn't contain data for all columns -Warning 1261 Row 2 doesn't contain data for all columns SELECT * FROM t1 UNION SELECT * FROM t2 ORDER BY a, b, c; a b c -1 NULL NULL +1 ABC-АБВ DEF-ÂÃÄ +2 NULL NULL +SELECT * FROM t1; +a b c +1 ABC-АБВ DEF-ÂÃÄ +2 NULL NULL +SELECT * FROM t2; +a b c 1 ABC-АБВ DEF-ÂÃÄ 2 NULL NULL SELECT * FROM t1 INTO OUTFILE 'MYSQLTEST_VARDIR/tmp/t1.txt' LINES STARTING BY 'ъ'; @@ -181,7 +182,14 @@ SELECT * FROM t1 UNION SELECT * FROM t2 ORDER BY a, b, c; a b c 1 ABC-АБВ DEF-ÂÃÄ -1 ABC-АБВ DEF-ÂÃÄÑŠ2 +2 NULL NULL +SELECT * FROM t1; +a b c +1 ABC-АБВ DEF-ÂÃÄ +2 NULL NULL +SELECT * FROM t2; +a b c +1 ABC-АБВ DEF-ÂÃÄ 2 NULL NULL # Default (binary) charset: SELECT * INTO OUTFILE 'MYSQLTEST_VARDIR/tmp/t1.txt' FROM t1; diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/parser.result mysql-5.5-5.5.43/mysql-test/r/parser.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/parser.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/parser.result 2015-02-27 08:30:35.000000000 +0000 @@ -622,3 +622,28 @@ # # End of 5.1 tests # +# +# Bug#17075846 : unquoted file names for variable values are +# accepted but parsed incorrectly +# +SET default_storage_engine=a.myisam; +ERROR 42000: Incorrect argument type to variable 'default_storage_engine' +SET default_storage_engine = .a.MyISAM; +ERROR 42000: Incorrect argument type to variable 'default_storage_engine' +SET default_storage_engine = a.b.MyISAM; +ERROR 42000: Incorrect argument type to variable 'default_storage_engine' +SET default_storage_engine = `a`.MyISAM; +ERROR 42000: Incorrect argument type to variable 'default_storage_engine' +SET default_storage_engine = `a`.`MyISAM`; +ERROR 42000: Incorrect argument type to variable 'default_storage_engine' +set default_storage_engine = "a.MYISAM"; +ERROR 42000: Unknown storage engine 'a.MYISAM' +set default_storage_engine = 'a.MYISAM'; +ERROR 42000: Unknown storage engine 'a.MYISAM' +set default_storage_engine = `a.MYISAM`; +ERROR 42000: Unknown storage engine 'a.MYISAM' +CREATE TABLE t1 (s VARCHAR(100)); +CREATE TRIGGER trigger1 BEFORE INSERT ON t1 FOR EACH ROW +SET default_storage_engine = NEW.INNODB; +ERROR 42S22: Unknown column 'INNODB' in 'NEW' +DROP TABLE t1; diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/partition_archive.result mysql-5.5-5.5.43/mysql-test/r/partition_archive.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/partition_archive.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/partition_archive.result 2015-02-27 08:30:35.000000000 +0000 @@ -126,3 +126,29 @@ count(*) 100 drop table t1; +# +#BUG 18618561: FAILED ALTER TABLE ENGINE CHANGE WITH PARTITIONS +# CORRUPTS FRM +CREATE TABLE t1 (fld1 INT PRIMARY KEY) ENGINE= MYISAM PARTITION BY HASH(fld1) +PARTITIONS 5; +SHOW CREATE TABLE t1; +Table Create Table +t1 CREATE TABLE `t1` ( + `fld1` int(11) NOT NULL, + PRIMARY KEY (`fld1`) +) ENGINE=MyISAM DEFAULT CHARSET=latin1 +/*!50100 PARTITION BY HASH (fld1) +PARTITIONS 5 */ +ALTER TABLE t1 ENGINE= ARCHIVE; +ERROR HY000: Can't create table 'test.#sql-temporary' (errno: 1) +#After the patch, the ENGINE is correctly displayed as MyISAM +SHOW CREATE TABLE t1; +Table Create Table +t1 CREATE TABLE `t1` ( + `fld1` int(11) NOT NULL, + PRIMARY KEY (`fld1`) +) ENGINE=MyISAM DEFAULT CHARSET=latin1 +/*!50100 PARTITION BY HASH (fld1) +PARTITIONS 5 */ +#Cleanup. +DROP TABLE t1; diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/partition_pruning.result mysql-5.5-5.5.43/mysql-test/r/partition_pruning.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/partition_pruning.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/partition_pruning.result 2015-02-27 08:30:35.000000000 +0000 @@ -3294,3 +3294,117 @@ id select_type table partitions type possible_keys key key_len ref rows Extra 1 SIMPLE t1 p0,p1,p2 ALL NULL NULL NULL NULL 100 Using where drop table t0, t1; +# +# Bug#71095: Wrong results with PARTITION BY LIST COLUMNS() +# +CREATE TABLE t1 +(c1 int, +c2 int, +c3 int, +c4 int, +PRIMARY KEY (c1,c2)) +PARTITION BY LIST COLUMNS (c2) +(PARTITION p1 VALUES IN (1,2), +PARTITION p2 VALUES IN (3,4)); +INSERT INTO t1 VALUES (1, 1, 1, 1), (2, 3, 1, 1); +INSERT INTO t1 VALUES (1, 2, 1, 1), (2, 4, 1, 1); +SELECT * FROM t1 WHERE c1 = 1 AND c2 < 1; +c1 c2 c3 c4 +SELECT * FROM t1 WHERE c1 = 1 AND c2 <= 1; +c1 c2 c3 c4 +1 1 1 1 +SELECT * FROM t1 WHERE c1 = 1 AND c2 = 1; +c1 c2 c3 c4 +1 1 1 1 +SELECT * FROM t1 WHERE c1 = 1 AND c2 >= 1; +c1 c2 c3 c4 +1 1 1 1 +1 2 1 1 +SELECT * FROM t1 WHERE c1 = 1 AND c2 > 1; +c1 c2 c3 c4 +1 2 1 1 +SELECT * FROM t1 WHERE c1 = 1 AND c2 < 3; +c1 c2 c3 c4 +1 1 1 1 +1 2 1 1 +SELECT * FROM t1 WHERE c1 = 1 AND c2 <= 3; +c1 c2 c3 c4 +1 1 1 1 +1 2 1 1 +SELECT * FROM t1 WHERE c1 = 2 AND c2 <= 3; +c1 c2 c3 c4 +2 3 1 1 +SELECT * FROM t1 WHERE c1 = 2 AND c2 = 3; +c1 c2 c3 c4 +2 3 1 1 +SELECT * FROM t1 WHERE c1 = 2 AND c2 >= 3; +c1 c2 c3 c4 +2 3 1 1 +2 4 1 1 +SELECT * FROM t1 WHERE c1 = 2 AND c2 > 3; +c1 c2 c3 c4 +2 4 1 1 +SELECT * FROM t1 WHERE c1 = 2 AND c2 < 4; +c1 c2 c3 c4 +2 3 1 1 +SELECT * FROM t1 WHERE c1 = 2 AND c2 <= 4; +c1 c2 c3 c4 +2 3 1 1 +2 4 1 1 +SELECT * FROM t1 WHERE c1 = 2 AND c2 = 4; +c1 c2 c3 c4 +2 4 1 1 +SELECT * FROM t1 WHERE c1 = 2 AND c2 >= 4; +c1 c2 c3 c4 +2 4 1 1 +SELECT * FROM t1 WHERE c1 = 2 AND c2 > 4; +c1 c2 c3 c4 +EXPLAIN PARTITIONS SELECT * FROM t1 WHERE c1 = 1 AND c2 < 1; +id select_type table partitions type possible_keys key key_len ref rows Extra +1 SIMPLE NULL NULL NULL NULL NULL NULL NULL NULL Impossible WHERE noticed after reading const tables +EXPLAIN PARTITIONS SELECT * FROM t1 WHERE c1 = 1 AND c2 <= 1; +id select_type table partitions type possible_keys key key_len ref rows Extra +1 SIMPLE t1 p1 range PRIMARY PRIMARY 8 NULL 1 Using where +EXPLAIN PARTITIONS SELECT * FROM t1 WHERE c1 = 1 AND c2 = 1; +id select_type table partitions type possible_keys key key_len ref rows Extra +1 SIMPLE t1 p1 const PRIMARY PRIMARY 8 const,const 1 +EXPLAIN PARTITIONS SELECT * FROM t1 WHERE c1 = 1 AND c2 >= 1; +id select_type table partitions type possible_keys key key_len ref rows Extra +1 SIMPLE t1 p1,p2 range PRIMARY PRIMARY 8 NULL 2 Using where +EXPLAIN PARTITIONS SELECT * FROM t1 WHERE c1 = 1 AND c2 > 1; +id select_type table partitions type possible_keys key key_len ref rows Extra +1 SIMPLE t1 p1,p2 range PRIMARY PRIMARY 8 NULL 2 Using where +EXPLAIN PARTITIONS SELECT * FROM t1 WHERE c1 = 1 AND c2 < 3; +id select_type table partitions type possible_keys key key_len ref rows Extra +1 SIMPLE t1 p1 range PRIMARY PRIMARY 8 NULL 1 Using where +EXPLAIN PARTITIONS SELECT * FROM t1 WHERE c1 = 1 AND c2 <= 3; +id select_type table partitions type possible_keys key key_len ref rows Extra +1 SIMPLE t1 p1,p2 range PRIMARY PRIMARY 8 NULL 2 Using where +EXPLAIN PARTITIONS SELECT * FROM t1 WHERE c1 = 2 AND c2 <= 3; +id select_type table partitions type possible_keys key key_len ref rows Extra +1 SIMPLE t1 p1,p2 range PRIMARY PRIMARY 8 NULL 2 Using where +EXPLAIN PARTITIONS SELECT * FROM t1 WHERE c1 = 2 AND c2 = 3; +id select_type table partitions type possible_keys key key_len ref rows Extra +1 SIMPLE t1 p2 const PRIMARY PRIMARY 8 const,const 1 +EXPLAIN PARTITIONS SELECT * FROM t1 WHERE c1 = 2 AND c2 >= 3; +id select_type table partitions type possible_keys key key_len ref rows Extra +1 SIMPLE t1 p2 range PRIMARY PRIMARY 8 NULL 1 Using where +EXPLAIN PARTITIONS SELECT * FROM t1 WHERE c1 = 2 AND c2 > 3; +id select_type table partitions type possible_keys key key_len ref rows Extra +1 SIMPLE t1 p2 range PRIMARY PRIMARY 8 NULL 1 Using where +EXPLAIN PARTITIONS SELECT * FROM t1 WHERE c1 = 2 AND c2 < 4; +id select_type table partitions type possible_keys key key_len ref rows Extra +1 SIMPLE t1 p1,p2 range PRIMARY PRIMARY 8 NULL 2 Using where +EXPLAIN PARTITIONS SELECT * FROM t1 WHERE c1 = 2 AND c2 <= 4; +id select_type table partitions type possible_keys key key_len ref rows Extra +1 SIMPLE t1 p1,p2 range PRIMARY PRIMARY 8 NULL 2 Using where +EXPLAIN PARTITIONS SELECT * FROM t1 WHERE c1 = 2 AND c2 = 4; +id select_type table partitions type possible_keys key key_len ref rows Extra +1 SIMPLE t1 p2 const PRIMARY PRIMARY 8 const,const 1 +EXPLAIN PARTITIONS SELECT * FROM t1 WHERE c1 = 2 AND c2 >= 4; +id select_type table partitions type possible_keys key key_len ref rows Extra +1 SIMPLE t1 p2 range PRIMARY PRIMARY 8 NULL 1 Using where +EXPLAIN PARTITIONS SELECT * FROM t1 WHERE c1 = 2 AND c2 > 4; +id select_type table partitions type possible_keys key key_len ref rows Extra +1 SIMPLE NULL NULL NULL NULL NULL NULL NULL NULL Impossible WHERE noticed after reading const tables +DROP TABLE t1; diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/plugin_auth_qa_3.result mysql-5.5-5.5.43/mysql-test/r/plugin_auth_qa_3.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/plugin_auth_qa_3.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/plugin_auth_qa_3.result 2015-02-27 08:30:35.000000000 +0000 @@ -6,6 +6,6 @@ current_user() user() @@local.proxy_user @@local.external_user qa_test_11_dest@% qa_test_11_user@localhost 'qa_test_11_user'@'%' 'qa_test_11_user'@'%' exec MYSQL PLUGIN_AUTH_OPT --default_auth=qa_auth_client -h localhost -P MASTER_MYPORT -u qa_test_2_user --password=qa_test_11_dest test_user_db -e "SELECT current_user(),user(),@@local.proxy_user,@@local.external_user;" 2>&1 -ERROR 1045 (28000): Access denied for user 'qa_test_2_user'@'localhost' (using password: NO) +ERROR 1045 (28000): Access denied for user 'qa_test_2_user'@'localhost' (using password: YES) DROP USER qa_test_11_user, qa_test_11_dest; DROP DATABASE test_user_db; diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/plugin.result mysql-5.5-5.5.43/mysql-test/r/plugin.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/plugin.result 2013-11-05 07:19:25.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/plugin.result 2015-02-27 08:30:35.000000000 +0000 @@ -143,3 +143,73 @@ @@SESSION.example_double_thdvar 1000.500000 UNINSTALL PLUGIN example; +# +# BUG#18008907 - DEADLOCK BETWEEN MYSQL_CHANGE_USER(), SHOW VARIABLES AND INSTALL PLUGIN +# +CREATE PROCEDURE p_install() +BEGIN +INSTALL PLUGIN no_such_plugin SONAME 'no_such_object'; +END +| +CREATE PROCEDURE p_show_vars() +BEGIN +SELECT COUNT(*) FROM INFORMATION_SCHEMA.GLOBAL_VARIABLES; +END| +connect con1, localhost, root,,; +# Case 18008907_1: Deadlock situation cause by +# con1: has LOCK_system_variables_hash and waits on LOCK_plugin AND +# default: has LOCK_plugin and waits on LOCK_system_variables_hash. +# +SET DEBUG_SYNC='acquired_LOCK_system_variables_hash SIGNAL install_plugin WAIT_FOR cont_show_vars'; +call p_show_vars();; +connection default; +SET DEBUG_SYNC='now WAIT_FOR install_plugin'; +SET DEBUG_SYNC='acquired_LOCK_plugin SIGNAL cont_show_vars'; +call p_install();; +connection con1; +COUNT(*) +# +SET DEBUG_SYNC='RESET'; +connection default; +ERROR HY000: Can't open shared library +SET DEBUG_SYNC='RESET'; +# Case 18008907_2: Deadlock situation caused by +# default: has LOCK_system_variables_hash and waits on LOCK_global_system_variables, +# con1: has LOCK_plugin and waits on LOCK_system_variables_hash AND +# con2: has LOCK_global_system_variables and waits on LOCK_plugin. +SET DEBUG_SYNC='acquired_LOCK_system_variables_hash SIGNAL install_plugin WAIT_FOR nothing TIMEOUT 10'; +call p_show_vars();; +connection con1; +SET DEBUG_SYNC='now WAIT_FOR install_plugin'; +SET DEBUG_SYNC='acquired_LOCK_plugin SIGNAL create_connection WAIT_FOR nothing TIMEOUT 10'; +call p_install();; +connect con2, localhost, root,,; +SET DEBUG_SYNC='now WAIT_FOR create_connection'; +connection con1; +ERROR HY000: Can't open shared library +connection default; +COUNT(*) +# +Warnings: +# 1639 debug sync point wait timed out +disconnect con2; +# Case 18008907_3: Testing Concurrent "Show Variables" and "Plugin Uninstall" operations. +INSTALL PLUGIN example SONAME 'ha_example.so'; +connection con1; +SET DEBUG_SYNC='acquired_LOCK_system_variables_hash SIGNAL uninstall_plugin WAIT_FOR go'; +call p_show_vars();; +connect con2, localhost, root,,; +SET DEBUG_SYNC='now WAIT_FOR uninstall_plugin'; +UNINSTALL PLUGIN example;; +connection default; +SET DEBUG_SYNC='now SIGNAL go'; +connection con1; +COUNT(*) +# +connection con2; +connection default; +DROP PROCEDURE p_show_vars; +DROP PROCEDURE p_install; +SET DEBUG_SYNC='RESET'; +disconnect con1; +disconnect con2; diff -Nru mysql-5.5-5.5.35+dfsg/mysql-test/r/show_processlist.result mysql-5.5-5.5.43/mysql-test/r/show_processlist.result --- mysql-5.5-5.5.35+dfsg/mysql-test/r/show_processlist.result 1970-01-01 00:00:00.000000000 +0000 +++ mysql-5.5-5.5.43/mysql-test/r/show_processlist.result 2015-02-27 08:30:35.000000000 +0000 @@ -0,0 +1,47 @@ +Bug#17283409 4-WAY DEADLOCK: ZOMBIES, PURGING BINLOGS, SHOW PROCESSLIST, +SHOW BINLOGS +connect connection1,localhost,root,,test,$MASTER_MYPORT,; +connection default; +SET DEBUG_SYNC='before_one_element_read_from_threads_iterator SIGNAL parked1 WAIT_FOR go'; +SHOW PROCESSLIST; +connection connection1; +"Wait_for parked1" +SET DEBUG_SYNC='now WAIT_FOR parked1'; +connect connection2,localhost,root,,test,$MASTER_MYPORT,; +connect connection3,localhost,root,,test,$MASTER_MYPORT,; +SET DEBUG_SYNC='now SIGNAL go'; +connection default; +Id User Host db Command Time State Info + root test