Author: mcbrown
Date: 2008-02-04 01:15:06 +0100 (Mon, 04 Feb 2008)
New Revision: 9691
Log:
Automatic update from openbugs
Modified:
trunk/dynamic-docs/open-bugs/mysqld.xml
Modified: trunk/dynamic-docs/open-bugs/mysqld.xml
===================================================================
--- trunk/dynamic-docs/open-bugs/mysqld.xml 2008-02-03 00:15:08 UTC (rev 9690)
+++ trunk/dynamic-docs/open-bugs/mysqld.xml 2008-02-04 00:15:06 UTC (rev 9691)
Changed blocks: 3, Lines Added: 41, Lines Deleted: 83; 3531 bytes
@@ -121,47 +121,6 @@
</tags>
<bugs>
- <fixes bugid="25162"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- <targetfix ver="5.1+"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Backing up <literal>DB</literal> from 5.1 adds
- '<literal>USING BTREE</literal>' to KEYs on table creates
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- The problem caused by this issue is that it is not possible
- to restore a dump of a 5.1 database to a 5.0 server without
- hand-editing the table definitions in the dump file. Another
- (and simpler) workaround is to create the dump using the
- mysqldump --compatible=mysql40 option or the Compatibility
- Mode in MySQL Administrator.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Client"/>
- </tags>
-
- <bugs>
<fixes bugid="26215"/>
</bugs>
@@ -4450,6 +4409,47 @@
</tags>
<bugs>
+ <fixes bugid="25162"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1"/>
+ <targetfix ver="5.1+"/>
+ </versions>
+
+ <message>
+
+ <para>
+ %BUGID%: Backing up <literal>DB</literal> from 5.1 adds
+ '<literal>USING BTREE</literal>' to KEYs on table creates
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ The problem caused by this issue is that it is not possible
+ to restore a dump of a 5.1 database to a 5.0 server without
+ hand-editing the table definitions in the dump file. Another
+ (and simpler) workaround is to create the dump using the
+ mysqldump --compatible=mysql40 option or the Compatibility
+ Mode in MySQL Administrator.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="custom" customname="open-bugs">
+
+ <tags>
+ <manual type="Server: Parser"/>
+ </tags>
+
+ <bugs>
<fixes bugid="30234"/>
</bugs>
@@ -5527,48 +5527,6 @@
</tags>
<bugs>
- <fixes bugid="26489"/>
- </bugs>
-
- <versions>
- <version ver="5.1"/>
- </versions>
-
- <message>
-
- <para>
- %BUGID%: Corruption in relay logs
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- This can occur whenusing unreliable connections between the
- master and slave. Suggested workarounds: (1) Use SSL
- connections to get an extra level of connection checking and
- possibly to prevent the issue from occurring; (2) if it does
- occur, use this sequence of stements to reset the slave:
- SHOW SLAVE STATUS; STOP SLAVE; CHANGE MASTER TO
- master_log_file=value_from_relay_master_log_file,
- master_log_pos=insert the value from Exec_master_log_pos;
- START SLAVE;.
- </para>
- </listitem>
-
- </itemizedlist>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="custom" customname="open-bugs">
-
- <tags>
- <manual type="Server: Replication"/>
- </tags>
-
- <bugs>
<fixes bugid="26980"/>
</bugs>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r9691 - trunk/dynamic-docs/open-bugs | mcbrown | 4 Feb |
