| List: | Commits | « Previous MessageNext Message » | |
| From: | paul | Date: | July 28 2007 1:26am |
| Subject: | svn commit - mysqldoc@docsrva: r7256 - in trunk: . refman-5.1 refman-5.2 | ||
| View as plain text | |||
Author: paul Date: 2007-07-28 01:26:32 +0200 (Sat, 28 Jul 2007) New Revision: 7256 Log: r23107@frost: paul | 2007-07-27 17:59:04 -0500 5.1 log destination default has changed from TABLE to FILE. (Bug#29993) Modified: trunk/refman-5.1/dba-core.xml trunk/refman-5.1/installing.xml trunk/refman-5.1/news-5.1.xml trunk/refman-5.2/dba-core.xml Property changes on: trunk ___________________________________________________________________ Name: svk:merge - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:28009 7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:23096 b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18941 + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:28009 7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:23107 b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18941 Modified: trunk/refman-5.1/dba-core.xml =================================================================== --- trunk/refman-5.1/dba-core.xml 2007-07-27 20:04:09 UTC (rev 7255) +++ trunk/refman-5.1/dba-core.xml 2007-07-27 23:26:32 UTC (rev 7256) Changed blocks: 3, Lines Added: 10, Lines Deleted: 18; 2162 bytes @@ -21731,19 +21731,19 @@ do so while running the server without <option>--old-passwords</option>. </para> - + <formalpara role="mnmas"> - + <title>MySQL Enterprise</title> - + <para> - Subscribers to the MySQL Network Monitoring and Advisory Service - are automatically alerted whenever a server is running with the - <option>--old-passwords</option> option. For more + Subscribers to the MySQL Network Monitoring and Advisory + Service are automatically alerted whenever a server is running + with the <option>--old-passwords</option> option. For more information see <ulink url="&base-url-enterprise;advisors.html"/>. </para> - + </formalpara> <para> @@ -28342,9 +28342,9 @@ <para> If <option>--log-output</option> is omitted or given without a value, the effect is the same as - <option>--log-output=TABLE</option>. That is, the table - destination is selected. (This differs from the default - destination of using files before MySQL 5.1.6.) + <option>--log-output=FILE</option>. That is, the file + destination is selected. (For MySQL 5.1.6 through 5.1.20, + the default is the table destination.) </para> </listitem> @@ -28368,14 +28368,6 @@ system tables after upgrading to make sure that the log tables exist. See <xref linkend="mysql-upgrade"/>. </para> - - <para> - Also, the default log destination changes from files to tables - as of MySQL 5.1.6. If you had the server configured for - logging to log files formerly, use - <option>--log-output=FILE</option> to preserve this behavior - after an upgrade to 5.1.6 or higher. - </para> </note> <para> Modified: trunk/refman-5.1/installing.xml =================================================================== --- trunk/refman-5.1/installing.xml 2007-07-27 20:04:09 UTC (rev 7255) +++ trunk/refman-5.1/installing.xml 2007-07-27 23:26:32 UTC (rev 7256) Changed blocks: 1, Lines Added: 13, Lines Deleted: 20; 2384 bytes @@ -12500,27 +12500,20 @@ <listitem> <para> - <emphasis role="bold">Incompatible change</emphasis>: Before - MySQL 5.1.6, the server writes general query log and slow - query log entries to log files. As of MySQL 5.1.6, the - server's logging capabilities for these logs are more - flexible. Log entries can be written to log files (as - before) or to the <literal>general_log</literal> and - <literal>slow_log</literal> tables in the - <literal>mysql</literal> database. If logging is enabled, - either or both destinations can be selected. The - <option>--log-output</option> option controls the - destination or destinations of log output. See - <xref linkend="log-tables"/>. + <emphasis role="bold">Incompatible change</emphasis>: In + MySQL 5.1.6, when log tables were implemented, the default + log destination for the general query and slow query log was + <literal>TABLE</literal>. As of MySQL 5.1.21, this default + has been changed to <literal>FILE</literal>, which is + compatible with MySQL 5.0, but incompatible with earlier + releases of MySQL 5.1 from 5.1.6 to 5.1.20. If you are + upgrading from MySQL 5.0 to this release, no logging option + changes should be necessary. However, if you are upgrading + from 5.1.6 through 5.1.20 to this release and were using + <literal>TABLE</literal> logging, use the + <option>--log-output=TABLE</option> option explicitly to + preserve your server's table-logging behavior. </para> - - <para> - If logging is enabled, the default destination now is to log - to tables, which differs from earlier versions. If you had - the server configured for logging to log files formerly, use - <option>--log-output=FILE</option> to preserve this behavior - after an upgrade to MySQL 5.1.6 or higher. - </para> </listitem> <listitem> Modified: trunk/refman-5.1/news-5.1.xml =================================================================== --- trunk/refman-5.1/news-5.1.xml 2007-07-27 20:04:09 UTC (rev 7255) +++ trunk/refman-5.1/news-5.1.xml 2007-07-27 23:26:32 UTC (rev 7256) Changed blocks: 2, Lines Added: 22, Lines Deleted: 1; 1623 bytes @@ -52,7 +52,11 @@ </para> &enterprise-offering-note; - + + <remark role="note"> + Leave any incompatible chnages first in the list. + </remark> + <para> Functionality added or changed: </para> @@ -61,6 +65,23 @@ <listitem> <para> + <emphasis role="bold">Incompatible change</emphasis>: In MySQL + 5.1.6, when log tables were implemented, the default log + destination for the general query and slow query log was + <literal>TABLE</literal>. This default has been changed to + <literal>FILE</literal>, which is compatible with MySQL 5.0, + but incompatible with earlier releases of MySQL 5.1 from 5.1.6 + to 5.1.20. If you are upgrading from MySQL 5.0 to this + release, no logging option changes should be necessary. + However, if you are upgrading from 5.1.6 through 5.1.20 to + this release and were using <literal>TABLE</literal> logging, + use the <option>--log-output=TABLE</option> option explicitly + to preserve your server's table-logging behavior. (Bug #29993) + </para> + </listitem> + + <listitem> + <para> Previously, prepared statements processed using <literal>PREPARE</literal> and <literal>EXECUTE</literal> were not subject to caching in the query cache if they contained Modified: trunk/refman-5.2/dba-core.xml =================================================================== --- trunk/refman-5.2/dba-core.xml 2007-07-27 20:04:09 UTC (rev 7255) +++ trunk/refman-5.2/dba-core.xml 2007-07-27 23:26:32 UTC (rev 7256) Changed blocks: 8, Lines Added: 23, Lines Deleted: 43; 5596 bytes @@ -28161,14 +28161,12 @@ <title>Selecting General Query and Slow Query Log Output Destinations</title> <para> - Before MySQL 5.1.6, the server uses log files as the destination - for general query log and slow query log entries, if those logs - are enabled. As of MySQL 5.1.6, the server provides more - flexible control over the destination for log output. Log - entries can be written to log files (as before) or to the - <literal>general_log</literal> and <literal>slow_log</literal> - tables in the <literal>mysql</literal> database. If logging is - enabled, either or both destinations can be selected. + MySQL Server provides flexible control over the destination for + log output. Log entries can be written to log files (as before) + or to the <literal>general_log</literal> and + <literal>slow_log</literal> tables in the + <literal>mysql</literal> database. If logging is enabled, either + or both destinations can be selected. </para> <para> @@ -28197,9 +28195,8 @@ <para> If <option>--log-output</option> is omitted or given without a value, the effect is the same as - <option>--log-output=TABLE</option>. That is, the table - destination is selected. (This differs from the default - destination of using files before MySQL 5.1.6.) + <option>--log-output=FILE</option>. That is, the file + destination is selected. </para> </listitem> @@ -28223,14 +28220,6 @@ system tables after upgrading to make sure that the log tables exist. See <xref linkend="mysql-upgrade"/>. </para> - - <para> - Also, the default log destination changes from files to tables - as of MySQL 5.1.6. If you had the server configured for - logging to log files formerly, use - <option>--log-output=FILE</option> to preserve this behavior - after an upgrade to 5.1.6 or higher. - </para> </note> <para> @@ -28376,8 +28365,8 @@ </para> <para> - Beginning with MySQL 5.1.12, the log tables can be altered to - use the <literal>MyISAM</literal> storage engine. You cannot use + The log tables can be altered to use the + <literal>MyISAM</literal> storage engine. You cannot use <literal>ALTER TABLE</literal> to alter a log table that is in use. The log must be disabled first. No engines other than <literal>CSV</literal> or <literal>MyISAM</literal> are legal @@ -28410,15 +28399,13 @@ </para> <para> - Beginning with MySQL 5.1.12, <literal>FLUSH TABLES</literal> - ignores log tables. To flush the log tables, use <literal>FLUSH - LOGS</literal> instead. + <literal>FLUSH TABLES</literal> ignores log tables. To flush the + log tables, use <literal>FLUSH LOGS</literal> instead. </para> <para> - Beginning with MySQL 5.1.13, you can atomically rename a log - table (to perform log rotation, for example) using the following - strategy: + You can atomically rename a log table (to perform log rotation, + for example) using the following strategy: </para> <programlisting> @@ -28555,18 +28542,13 @@ </para> <para> - To enable the general query log as of MySQL 5.1.6, start - <command>mysqld</command> with the + To enable the general query log, start <command>mysqld</command> + with the <option>--log[=<replaceable>file_name</replaceable>]</option> or <option>-l [<replaceable>file_name</replaceable>]</option> option, and optionally use <option>--log-output</option> to specify the log destination (as described in - <xref linkend="log-tables"/>). Before 5.1.6, the general query - log destination is always a file. To enable the general query - log file, use the - <option>--log[=<replaceable>file_name</replaceable>]</option> or - <option>-l [<replaceable>file_name</replaceable>]</option> - option. + <xref linkend="log-tables"/>). </para> <para> @@ -28580,12 +28562,11 @@ <para> When <option>--log</option> or <option>-l</option> is specified, - the <option>--general-log</option> option also may be given as - of MySQL 5.1.12 to specify the initial general query log state. - With no argument or an argument of 0, the option disables the - log. If omitted or given with an argument of 1, the option - enables the log. If <option>--log</option> or - <option>-l</option> is not specified, + the <option>--general-log</option> option also may be given to + specify the initial general query log state. With no argument or + an argument of 0, the option disables the log. If omitted or + given with an argument of 1, the option enables the log. If + <option>--log</option> or <option>-l</option> is not specified, <option>--general-log</option> has no effect. </para> @@ -28631,8 +28612,7 @@ </para> <para> - As of MySQL 5.1.12, you can disable the general query log at - runtime: + You can disable the general query log at runtime: </para> <programlisting>
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r7256 - in trunk: . refman-5.1 refman-5.2 | paul | 28 Jul |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.442 sec. using MySQL 5.1.14-beta-log