MySQL 5.5.18 发布下载
jopen 12年前
<p>MySQL 5.5 分支发布了第 18 个更新版本，下载地址：</p> <ul> <li><a href="/misc/goto?guid=4958190590933212798" target="_blank">http://dev.mysql.com/downloads/mysql/5.5.html</a></li> </ul> <p>改进内容：</p> <p><span class="bold"><strong>添加或修改的功能</strong></span></p> <div class="itemizedlist"> <ul> <li> <p>Upgrading from an <code class="literal">Advanced GPL</code> RPM package to an <code class="literal">Advanced</code> RPM package did not work. Now on Linux it is possible to use <span><strong class="command">rpm -U</strong></span> to replace any installed MySQL product by any other of the same release family. It is not necessary to remove the old produce with <span><strong class="command">rpm -e</strong></span> first. (Bug #11886309)</p> </li> </ul> </div> <p><span class="bold"><strong>Bugs Fixed</strong></span></p> <div class="itemizedlist"> <ul> <li> <p><span class="bold"><strong>Incompatible Change</strong></span>: <span class="bold"><strong>Replication</strong></span>: The statements in the following list are now marked as unsafe for statement-based replication. This is due to the fact that each of these statements depends on the results of a <a title="12.2.9. SELECT Syntax" href="/misc/goto?guid=4958200132193442593"><code class="literal">SELECT</code></a> statement whose order cannot always be determined. When using <code class="literal">STATEMENT</code> logging mode, a warning is issued in the binary log for any of these statements; when using <code class="literal">MIXED</code> logging mode, the statement is logged using the row-based format. </p> <div class="itemizedlist"> <ul> <li> <p><a title="12.2.5.1. INSERT ... SELECT Syntax" href="/misc/goto?guid=4958200132936492128"><code class="literal">INSERT ... SELECT</code></a><a title="12.2.5.3. INSERT ... ON DUPLICATE KEY UPDATE Syntax" href="/misc/goto?guid=4958200133677659196"><code class="literal"> ... ON DUPLICATE KEY UPDATE</code></a> </p> </li> <li> <p><a title="12.2.8. REPLACE Syntax" href="/misc/goto?guid=4958200134415735899"><code class="literal">REPLACE ... SELECT</code></a> </p> </li> <li> <p><a title="12.1.17.1. CREATE TABLE ... SELECT Syntax" href="/misc/goto?guid=4958200135164197926"><code class="literal">CREATE TABLE ... IGNORE SELECT</code></a> </p> </li> <li> <p><a title="12.1.17.1. CREATE TABLE ... SELECT Syntax" href="/misc/goto?guid=4958200135164197926"><code class="literal">CREATE TABLE ... REPLACE SELECT</code></a> </p> </li> <li> <p><a title="12.2.5.1. INSERT ... SELECT Syntax" href="/misc/goto?guid=4958200132936492128"><code class="literal">INSERT IGNORE ... SELECT</code></a> </p> </li> <li> <p><a title="12.2.11. UPDATE Syntax" href="/misc/goto?guid=4958200137263573267"><code class="literal">UPDATE IGNORE</code></a> </p> </li> </ul> </div> <p>When upgrading, you should note the use of these statements in your applications, keeping in mind that a statement that inserts or replaces rows obtained from a <a title="12.2.9. SELECT Syntax" href="/misc/goto?guid=4958200132193442593"><code class="literal">SELECT</code></a> can take up many times as much space in the binary log when logged using row-based format than when only the statement itself is logged. Depending on the number and size of the rows selected and inserted (or replaced) by any such statements, the difference in size of the binary log after the logging of these statements is switched from statement-based to row-based can potentially be several orders of magnitude. See <a title="15.1.2.1. Advantages and Disadvantages of Statement-Based and Row-Based Replication" href="/misc/goto?guid=4958200138680929233">Section 15.1.2.1, “Advantages and Disadvantages of Statement-Based and Row-Based Replication”</a>. (Bug #11758262, Bug #50439)</p> </li> <li> <p><span class="bold"><strong>Replication</strong></span>: A replication master could send damaged events to slaves after the binary log disk on the master became full. To correct this issue, only complete events are now pushed by the master dump thread to the slave I/O thread. In addition, the error text that the master sends to the slave when an incomplete event is found now states that the incomplete event may have been caused by running out of disk space on the master, and provides coordinates of the first and the last event bytes read. (Bug #11747416, Bug #32228)</p> </li> <li> <p>During the table-opening process, memory was allocated and later freed that was needed view loading, even for statements that did not use views. These unnecessary allocation and free operations are no longer done. (Bug #13116518)</p> </li> <li> <p><a title="4.4.4. mysql_plugin — Configure MySQL Server Plugins" href="/misc/goto?guid=4958200139426097134"><span><strong class="command">mysql_plugin</strong></span></a> mishandled the <a href="/misc/goto?guid=4958200140165144614"><code class="option">--plugin-ini</code></a>, <a href="/misc/goto?guid=4958200140901904463"><code class="option">--mysqld</code></a>, and <a href="/misc/goto?guid=4958200141645636858"><code class="option">--my-print-defaults</code></a> options under some circumstances. (Bug #12968815)</p> </li> <li> <p><a title="4.4.4. mysql_plugin — Configure MySQL Server Plugins" href="/misc/goto?guid=4958200139426097134"><span><strong class="command">mysql_plugin</strong></span></a> returned the wrong error code from failed server bootstrap execution. (Bug #12968567)</p> </li> <li> <p>Several improvements were made to the <code class="literal">libedit</code> library bundled with MySQL distributions, and that is available for all platforms that MySQL supports except Windows. </p> <div class="itemizedlist"> <ul> <li> <p>Navigation keys did not work for UTF-8 input. </p> </li> <li> <p>Word navigation and delete operations did not work for UTF-8 input with Cyrillic characters. </p> </li> <li> <p>Nonlatin characters were corrupted in overwrite mode for UTF-8 input. </p> </li> <li> <p>Long queries caused the statement history file to become corrupted. </p> </li> <li> <p>The Alt key caused history operations to fail. </p> </li> </ul> </div> <p>(Bug #12605400, Bug #12613725, Bug #12618092, Bug #12624155, Bug #12617651, Bug #12605388)</p> </li> <li> <p><a title="13.8. The ARCHIVE Storage Engine" href="/misc/goto?guid=4958200143071971328"><code class="literal">ARCHIVE</code></a> tables with <code class="literal">NULL</code> columns could cause server crashes or become corrupt under concurrent load. (Bug #51252, Bug #11758979)</p> </li> <li> <p><a title="12.7.2.4. OPTIMIZE TABLE Syntax" href="/misc/goto?guid=4958200143823006267"><code class="literal">OPTIMIZE TABLE</code></a> could corrupt <a title="13.5. The MyISAM Storage Engine" href="/misc/goto?guid=4958200144566086347"><code class="literal">MyISAM</code></a> tables if <a href="/misc/goto?guid=4958200145306762445"><code class="literal">myisam_use_mmap</code></a> was enabled. (Bug #49030, Bug #11757032)</p> </li> <li> <p>A query that selected a <a href="/misc/goto?guid=4958200146044828158"><code class="literal">GROUP_CONCAT()</code></a> function result could return different values depending on whether an <code class="literal">ORDER BY</code> of the function result was present. (Bug #41090, Bug #11750518)</p> </li> <li> <p>For <a title="13.11. The FEDERATED Storage Engine" href="/misc/goto?guid=4958200146783199621"><code class="literal">FEDERATED</code></a> tables, loss of connection to the remote table during some insert operations could cause a server crash. (Bug #34660, Bug #11747970)</p> </li> </ul> </div> <p></p>