MySQL Community Server 5.6.4 has been released
occur when these four things happened at the same time: 1) An old dump thread was waiting for the binary log to grow. 2) The slave server that replicates from the old dump thread tried to reconnect. During reconnection, the new dump thread tried to kill the old dump thread. 3) A KILL statement tried to kill the old dump thread. 4) An INSERT statement caused a binary log rotation. (Bug #56299, Bug #11763573) * myisampack could create corrupt FULLTEXT indexes when compressing tables. (Bug #53646, Bug #11761180) * The SQL_BIG_RESULT modifier could change the results for queries that included a GROUP BY clause. (Bug #53534, Bug #11761078) * ARCHIVE tables with NULL columns could cause server crashes or become corrupt under concurrent load. (Bug #51252, Bug #11758979) * InnoDB used incorrect identifier quoting style in an error message that resulted in an error if a user followed the suggestion in the message. (Bug #49556, Bug #11757503) * OPTIMIZE TABLE could corrupt MyISAM tables if myisam_use_mmap was enabled. (Bug #49030, Bug #11757032) * A query that selected a GROUP_CONCAT() function result could return different values depending on whether an ORDER BY of the function result was present. (Bug #41090, Bug #11750518) * A linking problem prevented the FEDERATED storage engine plugin from loading. (Bug #40942, Bug #11750417) * Subqueries could return incorrect results when materialization was enabled. (Bug #40037, Bug #11749901, Bug #12705660, Bug #12908058) * For debug builds, an assertion could be raised for ALTER statements that performed a RENAME operation. This occurred for storage engine handlertons that exposed the HTON_FLUSH_AFTER_RENAME flag. (Bug #38028, Bug #11749050) * The estimate of space required for filesort operations could be too high, resulting in inefficient initialization. (Bug #37359, Bug #11748783) * An ALTER TABLE that included an ADD ... AFTER operation to add a new column after a column that had been modified earlier in the statement failed to find the existing column. (Bug #34972, Bug #11748057) * For FEDERATED tables, loss of connection to the remote table during some insert operations could cause a server crash. (Bug #34660, Bug #11747970) * For some queries, the index_merge access method was used even when more expensive then ref access. (Bug #32254, Bug #11747423) Regards, -- Jonathan Perkin, Release Engineering Manager, MySQL Oracle Corporation UK Ltd. http://oss.oracle.com/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Community Server 5.1.39 has been released
non-transactional tables to the binary log in the correct order.) However, in some cases, this situation was not handled properly, and the determination whether a given statement was safe or not under these conditions was not always correct. In particular, a multi-table update that affected both transactional and non-transactional tables or a statement modifying data in a non-transactional table having a trigger that operated on a transactional table (or the reverse) was not determined to be unsafe when it should have been. With this fix, the following determinations regarding replication safety are made when combining updates to transactional and non-transactional tables within the same transaction in statement-based logging mode: 1. Any statement modifying data in a non-transactional table within a given transaction is considered safe if it is issued prior to any data modification statement accessing a transactional table within the same transaction. 2. A statement that updates transactional tables only is always considered safe. 3. A statement affecting both transactional and non-transactional tables within a transaction is always considered unsafe. It is not necessary that both tables be modified for this to be true; for example, a statement such as INSERT INTO innodb_table SELECT * FROM myisam_table is also considered unsafe. Note The current fix is valid only when using statement-based logging mode; we plan to address similar issues occurring when using the MIXED or ROW format in a future MySQL release. (Bug#28976: http://bugs.mysql.com/28976) * Stack overflow checking did not account for the size of the structure stored in the heap. (Bug#46807: http://bugs.mysql.com/46807) * In queries for which the loose index scan access method was chosen, using a condition of the form col_name rather than the equivalent col_name 0 caused an assertion failure. (Bug#46607: http://bugs.mysql.com/46607) * Killing a query that was performing a sort could result in a memory leak. (Bug#45962: http://bugs.mysql.com/45962) * Truncation of DECIMAL values could lead to assertion failures; for example, when deducing the type of a table column from a literal DECIMAL value. (Bug#45261: http://bugs.mysql.com/45261) * Bulk insert performance could suffer with large read_buffer_size values. (Bug#44723: http://bugs.mysql.com/44723) * A buffer overflow could occur during handling of IS NULL ranges. (Bug#37044: http://bugs.mysql.com/37044) * mysqladmin --wait ping crashed on Windows systems. (Bug#35132: http://bugs.mysql.com/35132) -- Jonathan Perkin, Release Engineering, MySQL Database Technology Group, Sun Microsystems -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
MySQL Community Server 5.1.38 has been released
: http://bugs.mysql.com/18828) -- Jonathan Perkin, Release Engineering, MySQL Database Technology Group, Sun Microsystems -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
MySQL Community Server 5.1.36 has been released
leak in association with use of X509 certificates. (Bug#42158: http://bugs.mysql.com/42158) * There was a race condition when changing innodb_commit_concurrency at runtime from zero to nonzero or from nonzero to zero. Now this variable cannot be changed at runtime from zero to nonzero or vice versa. The value can still be changed from one nonzero value to another. (Bug#42101: http://bugs.mysql.com/42101) * SELECT ... INTO @var could produce values different from SELECT ... without the INTO clause. (Bug#42009: http://bugs.mysql.com/42009) * mysql_zap did not work on Mac OS X. (Bug#41883: http://bugs.mysql.com/41883) * For views created with a column list clause, column aliases were not substituted when selecting through the view using a HAVING clause. (Bug#40825: http://bugs.mysql.com/40825) * A multiple-table DELETE involving a table self-join could cause a server crash. (Bug#39918: http://bugs.mysql.com/39918) * Creating an InnoDB table with a comment containing a '#' character caused foreign key constraints to be omitted. (Bug#39793: http://bugs.mysql.com/39793) * The mysql option --ignore-spaces was nonfunctional. (Bug#39101: http://bugs.mysql.com/39101) * If a query was such as to produce the error 1054 Unknown column '...' in 'field list', using EXPLAIN EXTENDED with the query could cause a server crash. (Bug#37362: http://bugs.mysql.com/37362) * If the MYSQL_HISTFILE environment variable was set to /dev/null, the mysql client overwrote the /dev/null device file as a normal file. (Bug#34224: http://bugs.mysql.com/34224) * mysqld_safe mishandled certain parameters if they contained spaces. (Bug#33685: http://bugs.mysql.com/33685) * mysqladmin kill did not work for thread IDs larger than 32 bits. (Bug#32457: http://bugs.mysql.com/32457) * Several client programs failed to interpret --skip-password as send no password. (Bug#28479: http://bugs.mysql.com/28479) * Output from mysql --html did not encode the , , or characters. (Bug#27884: http://bugs.mysql.com/27884) * mysql_convert_table_format did not prevent converting tables to MEMORY or BLACKHOLE tables, which could result in data loss. (Bug#27149: http://bugs.mysql.com/27149) -- Jonathan Perkin, Release Engineering, MySQL Database Technology Group, Sun Microsystems -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
MySQL 6.0.11 Alpha has been released!
Dear MySQL users,
MySQL 6.0.11-alpha, a new version of the MySQL database system has been
released. The main page for MySQL 6.0 release is at
http://www.mysql.com/mysql60/
6.0.11 will be the last release of 6.0. After this we will be
transitioning into a New Release Model for the MySQL Server
http://forge.mysql.com/wiki/Development_Cycle
The goal of this transition is to enable more frequent and timely
releases of the MySQL Server.
The planned milestone for September 2009 will probably include most of
the features from 6.0. More detail on which, will be communicated
before end of June. Features not in this milestone (e.g. Online Backup,
Falcon, Connection thread pooling, and 4 Byte UTF Support) are planned
for future milestones when they stabilize.
MySQL 6.0 includes two new storage engines: the transactional Falcon
engine, and the crash-safe Maria engine.
If you are new to the Falcon storage engine and need more information,
please read the Falcon Evaluation Guide at
http://www.mysql.com/why-mysql/white-papers/falcon-getting-started.php
and the Falcon White Paper at
http://www.mysql.com/why-mysql/white-papers/storage-engines-falcon.php
The Maria storage engine is a crash-safe version of MyISAM. Maria
supports all of the main functionality of the MyISAM engine, plus recovery
support (in the event of a system crash), all MyISAM row formats and a new
Maria-specific row format. Maria is documented at
http://dev.mysql.com/doc/refman/6.0/en/se-maria.html
MySQL 6.0.11-alpha is available in source and binary form for a number of
platforms from our download pages at
http://dev.mysql.com/downloads/mysql/6.0.html
and mirror sites. Note that not all mirror sites may be up to date at
this point in time, so if you can't find this version on some mirror,
please try again later or choose another download site.
We welcome and appreciate your feedback, bug reports, bug fixes, and
patches at
http://forge.mysql.com/wiki/Contributing
The following section lists functionality which has been added or changed,
as well as security-related, incompatible and important bugs fixes since
the previous version of MySQL 6.0. The full changelog including many
other changes can be viewed online at
http://dev.mysql.com/doc/refman/6.0/en/news-6-0-11.html
Enjoy!
Jonathan Perkin
The MySQL Build Team, Sun Microsystems
==
Functionality added or changed:
* Incompatible Change: The optimizer_switch system variable
controls optimizations that can be switched on and off. The
syntax for flags in its value has changed from 'no_opt_name'
to 'opt_name={on|off|default}'. For information about the new
syntax, see Section 7.2.22, Using optimizer_switch to Control
the Optimizer.
* Replication: The global server variables sync_master_info and
sync_relay_log_info are introduced for use on replication
slaves to control synchronization of, respectively, the
master.info and relay.info files.
In each case, setting the variable to a nonzero integer value
N causes the slave to synchonize the corresponding file to
disk after every N events. Setting its value to 0 allows the
operation system to handle syncronization of the file instead.
The actions of these variables, when enabled, are analogous to
how the sync_binlog variable works with regard to binary logs
on a replication master.
These variables can also be set in my.cnf, or by using the
server options --sync-master-info and --sync-relay-log-info
respectively.
An additional system variable relay_log_recovery is also now
available. When enabled, this variable causes a replication
slave to discard relay log files obtained from the replication
master following a crash.
This variable can also be set in my.cnf, or by using the
--relay-log-recovery server option.
This fix improves and expands upon one made in MySQL 6.0.10
which introduced the sync_relay_log variable. For more
information about all of the server system variables
introduced by these fixes, see Section 16.1.3.3, Replication
Slave Options and Variables.
(Bug#31665: http://bugs.mysql.com/31665,
Bug#35542: http://bugs.mysql.com/35542,
Bug#40337: http://bugs.mysql.com/40337)
* mysql-test-run.pl now supports an --experimental=file_name
option. It enables you to specify a file that contains a list
of test cases that should be displayed with the [ exp-fail ]
code rather than [ fail ] if they fail.
(Bug#42888: http://bugs.mysql.com/42888)
* The MD5 algorithm now uses the Xfree implementation.
(Bug#42434: http://bugs.mysql.com/42434)
* The RESTORE statement now has a SKIP_GAP_EVENT option that
causes the restore operation not to write the gap
MySQL Community Server 5.1.34 has been released
Dear MySQL users, MySQL Community Server 5.1.34, a new version of the popular Open Source Database Management System, has been released. MySQL 5.1.34 is recommended for use on production systems. MySQL 5.1.34 will be the final release of MySQL 5.1 for AIX 5.2, which will be EOL'd from 30th April 2009. For further information please see http://www.mysql.com/support/eol-notice.html For an overview of what's new in MySQL 5.1, please see http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html For information on installing MySQL 5.1.34 on new servers or upgrading to MySQL 5.1.34 from previous MySQL releases, please see http://dev.mysql.com/doc/refman/5.1/en/installing.html MySQL Server is available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/ Not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. We welcome and appreciate your feedback, bug reports, bug fixes, patches, etc.: http://forge.mysql.com/wiki/Contributing For information on open issues in MySQL 5.1, please see the errata list at http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.1. It may also be viewed online at http://dev.mysql.com/doc/refman/5.1/en/news-5-1-34.html Enjoy! Jonathan Perkin The MySQL build team at Sun Microsystems === Functionality added or changed: * Optimizer: The @@optimizer_switch setting was backported from MySQL 6.0, with additional switches to turn on/off use of index_merge optimizations or a particular index_merge algorithm. For more information please see http://s.petrunia.net/blog/?p=52 Bugs fixed: * Replication: Important Note: Binary logging with --binlog_format=ROW failed when a change to be logged included more than 251 columns. This issue was not known to occur with mixed-format or statement-based logging. (Bug#42977: http://bugs.mysql.com/42977) See also Bug#42914: http://bugs.mysql.com/42914. * Replication: Assigning an invalid directory for the --slave-load-tmpdir caused the replication slave to crash. (Bug#42861: http://bugs.mysql.com/42861) * Replication: The mysql.procs_priv system table was not replicated. (Bug#42217: http://bugs.mysql.com/42217) * Replication: An INSERT DELAYED into a TIMESTAMP column issued concurrently with a an insert on the same column not using DELAYED, but applied after the other insert, was logged using the same timestamp as generated by the other (non-DELAYED) insert. (Bug#41719: http://bugs.mysql.com/41719) * Replication: The MIXED binary logging format did not switch to row-based mode for statements containing the LOAD_FILE() function. (Bug#39701: http://bugs.mysql.com/39701) * Replication: When the server SQL mode included IGNORE_SPACE, statement-based replication of LOAD DATA INFILE ... INTO tbl_name failed because the statement was read incorrectly from the binary log; a trailing space was omitted, causing the statement to fail with a syntax error when run on the slave. (Bug#22504: http://bugs.mysql.com/22504) See also Bug#43746: http://bugs.mysql.com/43746. * An attempt by a user who did not have the SUPER privilege to kill a system thread could cause a server crash. (Bug#43748: http://bugs.mysql.com/43748) * On Windows, incorrectly specified link dependencies in CMakeLists.txt resulted in link errors for mysql_embedded, mysqltest_embedded, and mysql_client_test_embedded. (Bug#43715: http://bugs.mysql.com/43715) * mysql crashed if a request for the current database name returned an empty result, such as after the client has executed a preceding SET sql_select_limit=0 statement. (Bug#43254: http://bugs.mysql.com/43254) * If the value of the version_comment system variable was too long, the mysql client displayed a truncated startup message. (Bug#43153: http://bugs.mysql.com/43153) * Queries of the following form returned an empty result: SELECT ... WHERE ... (col=col AND col=col) OR ... (false expression) (Bug#42957: http://bugs.mysql.com/42957) * The strings/CHARSET_INFO.txt file was not included in source distributions. (Bug#42937: http://bugs.mysql.com/42937) * A dangling pointer in mysys/my_error.c could lead to client crashes. (Bug#42675: http://bugs.mysql.com/42675) * Passing an unknown time zone specification to CONVERT_TZ() resulted in a memory leak. (Bug#42502: http://bugs.mysql.com/42502) * With more than two arguments, LEAST(), GREATEST(), and CASE could unnecessarily return Illegal mix of collations errors. (Bug#41627: http://bugs.mysql.com/41627) * The mysql
MySQL Community Server 5.1.33 has been released
Dear MySQL users, MySQL Community Server 5.1.33, a new version of the popular Open Source Database Management System, has been released. MySQL 5.1.33 is recommended for use on production systems. Users running AIX 5.2 should be aware that this platform will be EOL'd from 30th April 2009, therefore 5.1.33 is likely to be the penultimate 5.1 release for AIX 5.2. For further information please see http://www.mysql.com/support/eol-notice.html For an overview of what's new in MySQL 5.1, please see http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html For information on installing MySQL 5.1.33 on new servers or upgrading to MySQL 5.1.33 from previous MySQL releases, please see http://dev.mysql.com/doc/refman/5.1/en/installing.html MySQL Server is available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/ Not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. We welcome and appreciate your feedback, bug reports, bug fixes, patches, etc.: http://forge.mysql.com/wiki/Contributing For information on open issues in MySQL 5.1, please see the errata list at http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.1. It may also be viewed online at http://dev.mysql.com/doc/refman/5.1/en/news-5-1-33.html Enjoy! Jonathan Perkin The MySQL build team at Sun Microsystems === Functionality added or changed: * mysql-test-run.pl now supports an --experimental=file_name option. It enables you to specify a file that contains a list of test cases that should be displayed with the [ exp-fail ] code rather than [ fail ] if they fail. (Bug#42888: http://bugs.mysql.com/42888) * The MD5 algorithm now uses the Xfree implementation. (Bug#42434: http://bugs.mysql.com/42434) * The query cache now checks whether a SELECT statement begins with SQL_NO_CACHE to determine whether it can skip checking for the query result in the query cache. This is not supported when SQL_NO_CACHE occurs within a comment. (Bug#37416: http://bugs.mysql.com/37416) Bugs fixed: * Partitioning: A duplicate key error raised when inserting into a partitioned table used a different error code from that returned by such an error raised when inserting into a table that was not partitioned. (Bug#38719: http://bugs.mysql.com/38719) See also Bug#28842: http://bugs.mysql.com/28842. * Partitioning: Several error messages relating to partitioned tables were incorrect or missing. (Bug#36001: http://bugs.mysql.com/36001) * Replication: When --binlog_format was set to STATEMENT, a statement unsafe for statement-based logging caused an error or warning to be issued even if sql_log_bin was set to 0. (Bug#41980: http://bugs.mysql.com/41980) * Replication: When using MIXED replication format and temporary tables were created in statement-based mode, but a later operation in the same session caused a switch to row-based mode, the temporary tables were not dropped on the slave at the end of the session. (Bug#40013: http://bugs.mysql.com/40013) See also Bug#43046: http://bugs.mysql.com/43046. This regression was introduced by Bug#20499: http://bugs.mysql.com/20499. * Replication: When using the MIXED replication format, UPDATE and DELETE statements that searched for rows where part of the key had nullable BIT columns failed. This occurred because operations that inserted the data were replicated as statements, but UPDATE and DELETE statements affecting the same data were replicated using row-based format. This issue did not occur when using statement-based replication (only) or row-based replication (only). (Bug#39753: http://bugs.mysql.com/39753) See also Bug#39648: http://bugs.mysql.com/39648. * Replication: The server SQL mode in effect when a stored procedure was created was not retained in the binary log. This could cause a CREATE PROCEDURE statement that succeeded on the master to fail on the slave. This issue was first noticed when a stored procedure was created when ANSI_QUOTES was in effect on the master, but could possibly cause failed CREATE PROCEDURE statements and other problems on the slave when using other server SQL modes as well. (Bug#39526: http://bugs.mysql.com/39526) * Replication: If --secure-file-priv was set on the slave, it was unable to execute LOAD DATA INFILE statements sent from the master when using mixed-format or statement-based replication. As a result of this fix, this security restriction is now ignored on the slave in such cases; instead
MySQL 6.0.10 Alpha has been released!
Dear MySQL users, MySQL 6.0.10-alpha, a new version of the MySQL database system has been released. The main page for MySQL 6.0 release is at http://www.mysql.com/mysql60/ MySQL 6.0 includes two new storage engines: the transactional Falcon engine, and the crash-safe Maria engine. If you are using the Falcon storage engine in MySQL 6.0.9-alpha, you are encouraged to wait for the MySQL 6.0.11-alpha before upgrading. Live upgrade is not recommended for 6.0 alpha releases. Users are strongly encouraged to dump their database and reload them after the upgrade. If you are new to the Falcon storage engine, we encourage you to either test Falcon in MySQL 6.0.9-alpha or wait for MySQL 6.0.11-alpha. The 6.0.10 release contains a large number of bug fixes for Falcon. After 6.0.10-alpha was built several bugs were reported and fixed, and will be part of the MySQL 6.0.11-alpha release. If you are new to the Falcon storage engine and need more information, please read the Falcon Evaluation Guide at http://www.mysql.com/why-mysql/white-papers/falcon-getting-started.php and the Falcon White Paper at http://www.mysql.com/why-mysql/white-papers/storage-engines-falcon.php The Maria storage engine is a crash-safe version of MyISAM. Maria supports all of the main functionality of the MyISAM engine, plus recovery support (in the event of a system crash), all MyISAM row formats and a new Maria-specific row format. Maria is documented at http://dev.mysql.com/doc/refman/6.0/en/se-maria.html MySQL 6.0.10-alpha is available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/mysql/6.0.html and mirror sites. Note that not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. We welcome and appreciate your feedback, bug reports, bug fixes, and patches at http://forge.mysql.com/wiki/Contributing The following section lists functionality which has been added or changed, as well as security-related, incompatible and important bugs fixes since the previous version of MySQL 6.0. The full changelog including many other changes can be viewed online at http://dev.mysql.com/doc/refman/6.0/en/news-6-0-10.html Enjoy! Jonathan Perkin The MySQL Build Team, Sun Microsystems == Functionality added or changed: * Important Change: Replication: RESET MASTER and RESET SLAVE now reset the values shown for Last_IO_Error, Last_IO_Errno, Last_SQL_Error, and Last_SQL_Errno in the output of SHOW SLAVE STATUS. (Bug#34654: http://bugs.mysql.com/34654) * Replication: A new global server variable sync_relay_log is introduced for use on replication slaves. Setting this variable to a nonzero integer value N causes the slave to synchonize the relay log to disk after every N events. It is analogous to how the sync_binlog variable works for binary logs on a replication master. This variable can also be set in my.cnf using the server option --sync-relay-log. For more information, see Section 16.1.3.3, Replication Slave Options and Variables. (Bug#31665: http://bugs.mysql.com/31665, Bug#35542: http://bugs.mysql.com/35542, Bug#40337: http://bugs.mysql.com/40337) * Replication: In circular replication, it was sometimes possible for an event to propagate such that it would be reapplied on all servers. This could occur when the originating server was removed from the replication circle and so could no longer act as the terminator of its own events, as normally happens in circular replication. In order to prevent this from occurring, a new IGNORE_SERVER_IDS option is introduced for the CHANGE MASTER TO statement. This option takes a list of replication server IDs; events having a server ID which appears in this list are ignored and not applied. For more information, see Section 12.6.2.1, CHANGE MASTER TO Syntax. (Bug#25998: http://bugs.mysql.com/25998) See also Bug#27808: http://bugs.mysql.com/27808. * The libedit library was upgraded to version 2.11. (Bug#42433: http://bugs.mysql.com/42433) * A new status variable, Queries, indicates the number of statements executed by the server. This includes statements executed within stored programs, unlike the Questions variable which includes only statements sent to the server by clients. (Bug#41131: http://bugs.mysql.com/41131) * Columns that provide a catalog value in INFORMATION_SCHEMA tables (for example, TABLES.TABLE_CATALOG) now have a value of def rather than NULL. (Bug#35427: http://bugs.mysql.com/35427) * mysql-test-run.pl now supports --client-bindir
MySQL 6.0.9 Alpha has been released!
Dear MySQL users, MySQL 6.0.9-alpha, a new version of the MySQL database system has been released. The main page for MySQL 6.0 release is at http://www.mysql.com/mysql60/ A new algorithm that uses both index access to the joined table and a join buffer has been implemented. It's called Batched Key Access (BKA) Join algorithm. The algorithm supports inner join, outer join and semi-join operations, including nested outer joins and nested semi-joins. Block Nested Loops Join algorithm previously used only for inner joins has been amended and now can be employed for outer join and semi-join operations, including nested nested outer joins and nested semi-joins. MySQL 6.0 includes two new storage engines: the transactional Falcon engine, and the crash-safe Maria engine. If you are new to the Falcon storage engine and need more information, please read the Falcon Evaluation Guide at http://www.mysql.com/why-mysql/white-papers/falcon-getting-started.php and the Falcon White Paper at http://www.mysql.com/why-mysql/white-papers/storage-engines-falcon.php The Maria storage engine is a crash-safe version of MyISAM. Maria supports all of the main functionality of the MyISAM engine, plus recovery support (in the event of a system crash), all MyISAM row formats and a new Maria-specific row format. Maria is documented at http://dev.mysql.com/doc/refman/6.0/en/se-maria.html MySQL 6.0.9-alpha is available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/mysql/6.0.html and mirror sites. Note that not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. We welcome and appreciate your feedback, bug reports, bug fixes, and patches at http://forge.mysql.com/wiki/Contributing The following section lists changes since the previous version of MySQL 6.0. The full changelog can also be viewed online at http://dev.mysql.com/doc/refman/6.0/en/news-6-0-9.html Enjoy! Jonathan Perkin, Product Engineering, MySQL Database Technology Group, Sun Microsystems == Functionality added or changed: * BACKUP DATABASE and RESTORE now indicate in the server's error log which databases are being backed up or restored. (Bug#40307: http://bugs.mysql.com/40307) * Performance of SELECT * retrievals from INFORMATION_SCHEMA.COLUMNS was improved slightly. (Bug#38918: http://bugs.mysql.com/38918) * Previously, index hints did not work for FULLTEXT searches. Now they work as follows: For natural language mode searches, index hints are silently ignored. For example, IGNORE INDEX(i) is ignored with no warning and the index is still used. For boolean mode searches, index hints with FOR ORDER BY or FOR GROUP BY are silently ignored. Index hints with FOR JOIN or no FOR modifier are honored. In contrast to how hints apply for non-FULLTEXT searches, the hint is used for all phases of query execution (finding rows and retrieval, grouping, and ordering). This is true even if the hint is given for a non-FULLTEXT index. (Bug#38842: http://bugs.mysql.com/38842) * MySQL support for adding collations using LDML specifications did not support the i identity rule that indicates one character sorts identically to another. The i rule now is supported. (Bug#37129: http://bugs.mysql.com/37129) * Previously, RESTORE overwrote any databases with information from the backup image. Now, RESTORE aborts with an error if the backup image contains any databases that currently exist on the server, unless the optional keyword OVERWRITE is given following the image filename. (Bug#34579: http://bugs.mysql.com/34579) * A new statement, PURGE BACKUP LOGS, enables the contents of the MySQL Backup logs to be culled. See Section 12.5.3.2, PURGE BACKUP LOGS Syntax. (Bug#33364: http://bugs.mysql.com/33364) Bugs fixed: * Security Enhancement: When the DATA DIRECTORY or INDEX DIRECTORY clause of a CREATE TABLE statement referred to a subdirectory of the data directory via a symlinked component of the data directory path, it was accepted, when for security reasons it should be rejected. (Bug#39277: http://bugs.mysql.com/39277) * Incompatible Change: CHECK TABLE ... FOR UPGRADE did not check for collation changes made in MySQL 6.0.1 to latin2_czech_cs or collation changes made in MySQL 6.0.6 to big5_chinese_ci, cp866_general_ci, gb2312_chinese_ci, and gbk_chinese_ci. (This also affects mysqlcheck and mysql_upgrade, which cause that statement to be executed.) (Bug#40054: http://bugs.mysql.com/40054
MySQL 6.0.7 Alpha has been released!
Dear MySQL users, MySQL 6.0.7-alpha, a new version of the MySQL database system has been released. The main page for MySQL 6.0 release is at http://www.mysql.com/mysql60/ MySQL 6.0 includes two new storage engines: the transactional Falcon engine, and the crash-safe Maria engine. If you are new to the Falcon storage engine and need more information, please read the Falcon Evaluation Guide at http://www.mysql.com/why-mysql/white-papers/falcon-getting-started.php and the Falcon White Paper at http://www.mysql.com/why-mysql/white-papers/storage-engines-falcon.php The Maria storage engine is a crash safe version of MyISAM. Maria supports all of the main functionality of the MyISAM engine, but includes recovery support (in the event of a system crash), full logging (including CREATE, DROP, RENAME and TRUNCATE operations), all MyISAM row formats and a new Maria specific row format. Maria is documented at http://dev.mysql.com/doc/refman/6.0/en/se-maria.html MySQL 6.0.7-alpha is available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/mysql/6.0.html and mirror sites. Note that not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. We welcome and appreciate your feedback, bug reports, bug fixes, and patches at http://forge.mysql.com/wiki/Contributing The following section lists important, incompatible and security changes since the previous version of MySQL 6.0. The full changelog, including many more fixes can be viewed online at http://dev.mysql.com/doc/refman/6.0/en/news-6-0-7.html Important functionality added or changed: * Important Change: mysqlbinlog now supports --verbose and --base64-output=DECODE-ROWS options to display row events as commented SQL statements. (The default otherwise is to display row events encoded as base-64 strings using BINLOG statements.) See Section 4.6.7.2, mysqlbinlog Row Event Display. (Bug#31455: http://bugs.mysql.com/31455) Important, security, or incompatible bugs fixed: * Security Enhancement: The server consumed excess memory while parsing statements with hundreds or thousands of nested boolean conditions (such as OR (OR ... (OR ... ))). This could lead to a server crash or incorrect statement execution, or cause other client statements to fail due to lack of memory. The latter result constitutes a denial of service. (Bug#38296: http://bugs.mysql.com/38296) * Incompatible Change: There were some problems using DllMain() hook functions on Windows that automatically do global and per-thread initialization for libmysqld.dll: + Per-thread initialization: MySQL internally counts the number of active threads, which causes a delay in my_end() if not all threads have exited. But there are threads that can be started either by Windows internally (often in TCP/IP scenarios) or by users. Those threads do not necessarily use libmysql.dll functionality but still contribute to the open-thread count. (One symptom is a five-second delay in times for PHP scripts to finish.) + Process-initialization: my_init() calls WSAStartup that itself loads DLLs and can lead to a deadlock in the Windows loader. To correct these problems, DLL initialization code now is not invoked from libmysql.dll by default. (Bug#37226: http://bugs.mysql.com/37226) * Incompatible Change: Some performance problems of SHOW ENGINE INNODB STATUS were reduced by removing used cells and Total number of lock structs in row lock hash table from the output. These values are now present only if UNIV_DEBUG is defined at MySQL build time. (Bug#36941: http://bugs.mysql.com/36941, Bug#36942: http://bugs.mysql.com/36942) * Important Change: The INFORMATION_SCHEMA.FALCON_TABLES table has been removed. (Bug#29211: http://bugs.mysql.com/29211, Bug#34705: http://bugs.mysql.com/34705, Bug#34706: http://bugs.mysql.com/34706) Enjoy! -- Jonathan Perkin, Product Engineering, MySQL Database Technology Group, Sun Microsystems -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySQL Community Server 5.0.67 has been released!
statements (where IDs are now always obtained in batches of 32 or more), but only between statements. The default value for this variable has also changed, and is now 1. (Bug#25176: http://bugs.mysql.com/25176, Bug#31956: http://bugs.mysql.com/31956, Bug#32055: http://bugs.mysql.com/32055) * Important Change: Replication: When the master crashed during an update on a transactional table while in AUTOCOMMIT mode, the slave failed. This fix causes every transaction (including AUTOCOMMIT transactions) to be recorded in the binlog as starting with a BEGIN and ending with a COMMIT or ROLLBACK. (Bug#26395: http://bugs.mysql.com/26395) * Important Change: It was possible to use FRAC_SECOND as a synonym for MICROSECOND with DATE_ADD(), DATE_SUB(), and INTERVAL; now, using FRAC_SECOND with anything other than TIMESTAMPADD() or TIMESTAMPDIFF() produces a syntax error. It is now possible (and preferable) to use MICROSECOND with TIMESTAMPADD() and TIMESTAMPDIFF(), and FRAC_SECOND is now deprecated. (Bug#33834: http://bugs.mysql.com/33834) * Important Change: The server no longer issues warnings for truncation of excess spaces for values inserted into CHAR columns. This reverts a change in the previous release that caused warnings to be issued. (Bug#30059: http://bugs.mysql.com/30059) * Replication: Important Note: Network timeouts between the master and the slave could result in corruption of the relay log. This fix rectifies a long-standing replication issue when using unreliable networks, including replication over wide area networks such as the Internet. If you experience reliability issues and see many You have an error in your SQL syntax errors on replication slaves, we strongly recommend that you upgrade to a MySQL version which includes this fix. (Bug#26489: http://bugs.mysql.com/26489) Enjoy! -- Jonathan Perkin, Product Engineering, MySQL Database Technology Group, Sun Microsystems -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySQL 6.0.5 Alpha has been released!
information is now shown in the Data_free column of SHOW TABLE STATUS and in the DATA_FREE column of the INFORMATION_SCHEMA.TABLES table. (Bug#32440: http://bugs.mysql.com/32440) This regression was introduced by Bug#11379: http://bugs.mysql.com/11379 * Important Change: The server handled truncation of values having excess trailing spaces into CHAR, VARCHAR, and TEXT columns in different ways. This behavior has now been made consistent for columns of all three of these types, and now follows the existing behavior of VARCHAR columns in this regard; that is, a Note is always issued whenever such truncation occurs. This change does not affect columns of these three types when using a binary encoding; BLOB columns are also unaffected by the change, since they always use a binary encoding. (Bug#30059: http://bugs.mysql.com/30059) * Important Change: An AFTER UPDATE trigger was not invoked when the UPDATE did not make any changes to the table for which the trigger was defined. Now AFTER UPDATE triggers behave the same in this regard as do BEFORE UPDATE triggers, which are invoked whether the UPDATE makes any changes in the table or not. (Bug#23771: http://bugs.mysql.com/23771) * Replication: Important Note: Network timeouts between the master and the slave could result in corruption of the relay log. This fix rectifies a long-standing replication issue when using unreliable networks, including replication over wide area networks such as the Internet. If you experience reliability issues and see many You have an error in your SQL syntax errors on replication slaves, we strongly recommend that you upgrade to a MySQL version which includes this fix. (Bug#26489: http://bugs.mysql.com/26489) Enjoy! -- Jonathan Perkin, Senior Production Engineer, MySQL Database Technology Group, Sun Microsystems -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
