Author: paul
Date: 2009-06-04 18:59:51 +0200 (Thu, 04 Jun 2009)
New Revision: 15193
Log:
r41886@frost: paul | 2009-06-04 11:58:32 -0500
Document bug fix:
Bug#19027: MySQL 5.0 starts even with Fatal InnoDB errors
Modified:
trunk/dynamic-docs/changelog/mysqld-1.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:41884
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:38756
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:41886
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:38756
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2009-06-04 16:21:28 UTC (rev 15192)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2009-06-04 16:59:51 UTC (rev 15193)
Changed blocks: 1, Lines Added: 147, Lines Deleted: 0; 5171 bytes
@@ -58381,4 +58381,151 @@
</logentry>
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="incompatiblechange"/>
+ <manual type="plugins"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="19027"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.36"/>
+ </versions>
+
+ <message>
+
+ <para>
+ The server can load plugins under control of startup options.
+ For example, many storage engines can be built in pluggable form
+ and loaded when the server starts. In the following
+ descriptions, <replaceable>plugin_name</replaceable> stands for
+ a plugin name such as <literal>innodb</literal>.
+ </para>
+
+ <para>
+ Previously, plugin options were handled like other boolean
+ options (see <xref linkend="option-modifiers"/>). That is, any
+ of these options enabled the plugin:
+ </para>
+
+<programlisting>
+--<replaceable>plugin_name</replaceable>
+--<replaceable>plugin_name</replaceable>=1
+--enable-<replaceable>plugin_name</replaceable>
+</programlisting>
+
+ <para>
+ And these options disabled the plugin:
+ </para>
+
+<programlisting>
+--<replaceable>plugin_name</replaceable>=0
+--disable-<replaceable>plugin_name</replaceable>
+--skip-<replaceable>plugin_name</replaceable>
+</programlisting>
+
+ <para>
+ However, use of a boolean option for plugin loading did not
+ provide control over what to do if the plugin failed to start
+ properly: Should the server exit, or start with the plugin
+ disabled? The actual behavior has been that the server starts
+ with the plugin disabled, which can be problematic. For example,
+ if <literal>InnoDB</literal> fails to start, existing
+ <literal>InnoDB</literal> tables become inaccessible, and
+ attempts to create new <literal>InnoDB</literal> tables result
+ in tables that use the default storage engine unless the
+ <literal role="sqlmode">NO_ENGINE_SUBSTITUTION</literal> SQL
+ mode has been enabled to cause an error to occur instead.
+ </para>
+
+ <para>
+ Now, there is a change in the options used to control plugin
+ loading, such that they have a tristate format:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <option>--<replaceable>plugin_name</replaceable>=OFF</option>
+ </para>
+ <para>
+ Do not enable the plugin.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <option>--<replaceable>plugin_name</replaceable>=ON</option>
+ </para>
+ <para>
+ Enable the plugin. If plugin initialization fails, start the
+ server anyway, but with the plugin disabled.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <option>--<replaceable>plugin_name</replaceable>=FORCE</option>
+ </para>
+ <para>
+ Enable the plugin. If plugin initialization fails, do not
+ start the server. In other words, force the server to run
+ with the plugin or not at all.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
+ The values <literal>OFF</literal>, <literal>ON</literal>, and
+ <literal>FORCE</literal> are not case sensitive.
+ </para>
+
+ <para>
+ Suppose that <literal>CSV</literal> and
+ <literal>InnoDB</literal> have been built as pluggable storage
+ engines and that you want the server to load them at startup,
+ subject to these conditions: The server is allowed to run if
+ <literal>CSV</literal> initialization fails, but must require
+ that <literal>InnoDB</literal> initialization succeed. To
+ achieve these conditions, use these lines in an option file:
+ </para>
+
+<programlisting>
+[mysqld]
+csv=ON
+innodb=FORCE
+</programlisting>
+
+ <para>
+ This change is incompatible with the previous implementation if
+ you used options of the form
+ <option>--<replaceable>plugin_name</replaceable>=0</option> or
+ <option>--<replaceable>plugin_name</replaceable>=1</option>,
+ which should be changed to
+ <option>--<replaceable>plugin_name</replaceable>=OFF</option> or
+ <option>--<replaceable>plugin_name</replaceable>=ON</option>,
+ respectively.
+ </para>
+
+ <para>
+ <option>--enable-<replaceable>plugin_name</replaceable></option>
+ is still supported and is the same as
+ <option>--<replaceable>plugin_name</replaceable>=ON</option>.
+ <option>--disable-<replaceable>plugin_name</replaceable></option>
+ and
+ <option>--skip-<replaceable>plugin_name</replaceable></option>
+ are still supported and are the same as
+ <option>--<replaceable>plugin_name</replaceable>=OFF</option>.
+ </para>
+
+ </message>
+
+ </logentry>
+
</changelog>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r15193 - in trunk: . dynamic-docs/changelog | paul.dubois | 5 Jun |
