MySQL 5.0.1 Alpha Publish

zhaozj2021-02-16  110

Yesterday, MySQL 5.0.1 Alpha was released, including many new features, please see Changelog for details.

Download: http://dev.mysql.com/downloads/mysql/5.0.1-snapshot.html

News from the ChangeLog: Functionality added or changed: * Added support of read only and updateable VIEWs based on single table or other updateable VIEWs * Implemented a new `` greedy search '' optimizer that can significantly reduce the time spent on optimizing the query. in some many-table joins. (You are affected if not only some particular SELECT is slow, but even using EXPLAIN for it takes a noticeable amount of time.) Two new system variables, optimizer_search_depth and optimizer_prune_level, can be used to fine-tune .!. optimizer behavior * Warning: Incompatible change C API change: mysql_shutdown () now requires a second argument This is a source-level incompatibility that affects how you compile client programs; it does not affect the ability of compiled clients to communicate with older Servers. See section "mysql_shutdown ()" in the manual. * a stored procedure is no longer "global" - IE IT Now belongs to a specific database: * When a database is dropped, all routines belonging to that database are also dropped * Procedure names may be qualified, eg `db.p () '* When executed from another database an implicit" use db ". IS in effect. * Explicit "Uses DB"

is no longer allowed in a stored procedure. * Fixed SHOW TABLES output field name and values ​​according to standard. Field name changed from Type to table_type, values ​​are BASE TABLE, VIEW and ERROR. (Bug # 4603) * Added sql_updatable_view_key system variable. * Added --replicate-same-server-id server option. * Added Last_query_cost status variable that reports optimizer cost for last compiled query. * Added option --to-last-log to mysqlbinlog, for use in conjunction with --read- from-remote-server. * Added --innodb-safe-binlog server option, which adds consistency guarantees between the content of InnoDB tables and the binary log. See section "The binary log" in the manual. * OPTIMIZE TABLE for InnoDB tables Is now mapped to alter table. * sync_frm is now a settable global variable (not only a startup option). * for replication of memory (heap) TABLES: MADE The master Automa tically write a DELETE FROM statement to its binary log when a MEMORY table is opened for the first time since master's startup This is for the case where the slave has replicated a non-empty MEMORY table, then the master is shut down and restarted.: THE TABLE IS NOW EMPTY ON MASTER; The Delete from Empties It On Slave Too. Note That Even with this fix, between the master '

Swing still haas out-of-date data in the table. But if you use the --init-file option to populate the memory table on the master at Startup, IT EnsuRES that the failing time interval is zero. (Bug # 2477) * When a session having open temporary tables terminates, the statement automatically written to the binary log is now DROP TEMPORARY TABLE IF EXISTS instead of DROP TEMPORARY TABLE, for more robustness. * The MySQL server now returns an error if SET SQL_LOG_BIN is issued by a user without the SUPER privilege (in previous versions it just silently ignored the statement in this case). * Changed that when the MySQL server has binary logging disabled (that is, no log -bin Option WAS Used? no transaction binlog cache is allocated for connections (32 kilobytes by default) for evening connection . * Added the sync_binlog = N global variable and startup option, which makes the MySQL server synchronize its binary log to disk (fdatasync ()) after every Nth write to the binary log. * Changed the slave SQL thread to print less useless error messages NO more Message Duplication;

转载请注明原文地址:https://www.9cbs.com/read-10433.html

New Post(0)