Author: paul
Date: 2008-09-02 21:30:19 +0200 (Tue, 02 Sep 2008)
New Revision: 11642
Log:
r33588@frost: paul | 2008-09-02 14:27:37 -0500
Document bugfixes:
Bug#33023: Online backup could mangle object names if non-std charset is used
Bug#35230: Backup: no backupdir
Bug#35468: Slowdown and wrong result for uncorrelated subquery w/o where
Bug#36579: Dumping information about locks in use may lead to a server crash
Bug#37120: optimizer_switch allowable values not according to specification
Bug#37548: result value erronously reported being NULL in certain subqueries
Bug#37799: Columns after a column from type BIT are handled as string
Bug#38195: Executing query causes memory access violation error in mysql service
Modified:
trunk/dynamic-docs/changelog/mysqld-1.xml
trunk/dynamic-docs/command-optvars/mysqld.xml
trunk/refman-6.0/dba-core.xml
trunk/refman-6.0/sql-syntax-server-administration.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:33576
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:32819
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:33588
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:32819
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2008-09-02 17:34:12 UTC (rev 11641)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2008-09-02 19:30:19 UTC (rev 11642)
Changed blocks: 2, Lines Added: 194, Lines Deleted: 0; 4272 bytes
@@ -25343,6 +25343,7 @@
<versions>
<version ver="5.0.70"/>
<version ver="5.1.28"/>
+ <version ver="6.0.6"/>
</versions>
<message>
@@ -25789,4 +25790,197 @@
</logentry>
+ <logentry entrytype="bug">
+
+ <tags>
+ <manual type="BACKUP DATABASE"/>
+ <manual type="RESTORE"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="33023"/>
+ </bugs>
+
+ <versions>
+ <version ver="6.0.7"/>
+ </versions>
+
+ <message>
+
+ <para>
+ <literal>BACKUP DATABASE</literal> followed by
+ <literal>RESTORE</literal> could mangle object names if a
+ non-standard charset was used.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <manual type="optimizer_switch"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="37120"/>
+ </bugs>
+
+ <versions>
+ <version ver="6.0.7"/>
+ </versions>
+
+ <message>
+
+ <para>
+ The <literal>optimizer_switch</literal> system variable takes a
+ comma-separated list of values, but only the first value in the
+ list was used.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <manual type="subqueries"/>
+ <manual type="optimizer"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="35468"/>
+ </bugs>
+
+ <versions>
+ <version ver="6.0.7"/>
+ </versions>
+
+ <message>
+
+ <para>
+ For uncorrelated subqueries without a <literal>WHERE</literal>
+ clause, use of semi-join or materialization options could result
+ in slow performance, or use of the LooseScan strategy could
+ produce incorrect results.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <manual type="optimizer"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="37548"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.28"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When using indexed <literal>ORDER BY</literal> sorting,
+ incorrect query results could be produced if the optimizer
+ switched from a covering index to a non-covering index.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <manual type="optimizer"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="38195"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.0.70"/>
+ <version ver="5.1.28"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Incorrect handling of aggregate functions when loose index scan
+ was used caused a server crash.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <manual type="BIT"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="37799"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.28"/>
+ </versions>
+
+ <message>
+
+ <para>
+ If a table has a <literal>BIT NOT NULL</literal> column
+ <literal>c1</literal> with a length shorter than 8 bits and some
+ additional <literal>NOT NULL</literal> columns
+ <literal>c2</literal>, ..., and a <literal>SELECT</literal>
+ query has a <literal>WHERE</literal> clause of the form
+ <literal>(c1 = <replaceable>constant</replaceable>) AND c2
+ ...</literal>, the query could return an unexpected result set.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="feature">
+
+ <tags>
+ <manual type="backupdir"/>
+ <manual type="BACKUP DATABASE"/>
+ <manual type="RESTORE"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="35230"/>
+ </bugs>
+
+ <versions>
+ <version ver="6.0.7"/>
+ </versions>
+
+ <message>
+
+ <para>
+ A new system variable, <literal>backupdir</literal>, enables the
+ default directory to be specified for <literal>BACKUP
+ DATABASE</literal> and <literal>RESTORE</literal> operations
+ when the image file pathname is not a full pathname. The default
+ value for this variable is the data directory.
+ </para>
+
+ </message>
+
+ </logentry>
+
</changelog>
Modified: trunk/dynamic-docs/command-optvars/mysqld.xml
===================================================================
--- trunk/dynamic-docs/command-optvars/mysqld.xml 2008-09-02 17:34:12 UTC (rev 11641)
+++ trunk/dynamic-docs/command-optvars/mysqld.xml 2008-09-02 19:30:19 UTC (rev 11642)
Changed blocks: 1, Lines Added: 25, Lines Deleted: 0; 1060 bytes
@@ -5335,6 +5335,31 @@
</mysqloption>
+ <mysqloption section="server" id="backupdir">
+
+ <xrefto id="option_mysqld_backupdir"/>
+
+ <name>backupdir</name>
+
+ <shortdescription lang="en">
+ Default backup image file directory
+ </shortdescription>
+
+ <types>
+ <optype class="cmdline" format="--backupdir=name" setvar="backupdir"/>
+ <optype class="mycnf" format="backupdir" setvar="backupdir"/>
+ <vartype class="system" isdynamic="yes" scope="global" format="backupdir"/>
+ </types>
+
+ <values vartype="filename" platform="all"/>
+
+ <versions>
+ <manual version="6.0"/>
+ <introduced version="6.0.7"/>
+ </versions>
+
+ </mysqloption>
+
<mysqloption section="server" id="basedir">
<xrefto id="option_mysqld_basedir"/>
Modified: trunk/refman-6.0/dba-core.xml
===================================================================
--- trunk/refman-6.0/dba-core.xml 2008-09-02 17:34:12 UTC (rev 11641)
+++ trunk/refman-6.0/dba-core.xml 2008-09-02 19:30:19 UTC (rev 11642)
Changed blocks: 2, Lines Added: 37, Lines Deleted: 7; 2544 bytes
@@ -372,6 +372,36 @@
</listitem>
<listitem>
+ <para id="option_mysqld_backupdir">
+ <indexterm>
+ <primary>mysqld</primary>
+ <secondary>backupdir option</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>backupdir option</primary>
+ <secondary>mysqld</secondary>
+ </indexterm>
+
+ <option>--backupdir=<replaceable>path</replaceable></option>
+ </para>
+
+ <para condition="dynamic:optvar:item" role="6.0:mysqld:backupdir"/>
+
+ <para>
+ The path to the default iimage file directory for
+ <literal>BACKUP DATABASE</literal> and
+ <literal>RESTORE</literal> operations. If an image file is
+ named as a relative pathname, it is interpreted relative to
+ the value of <literal>backupdir</literal>. If the value of
+ <literal>backupdir</literal> is itself a relative pathname,
+ its value is interpreted relative to the data directory. The
+ default value is the data directory. This variable was added
+ in MySQL 6.0.7.
+ </para>
+ </listitem>
+
+ <listitem>
<para id="option_mysqld_basedir">
<indexterm>
<primary>mysqld</primary>
@@ -12554,13 +12584,13 @@
<listitem>
<para>
- Log contents are accessible vian SQL statements. This enables
- the use of queries that select only those log entries that
- satisfy specific criteria. For example, to select log
- contents associated with a particular client (which can be
- useful for identifying problematic queries from that
- client), it is easier to do this using a log table than a
- log file.
+ Log contents are accessible vian SQL statements. This
+ enables the use of queries that select only those log
+ entries that satisfy specific criteria. For example, to
+ select log contents associated with a particular client
+ (which can be useful for identifying problematic queries
+ from that client), it is easier to do this using a log table
+ than a log file.
</para>
</listitem>
Modified: trunk/refman-6.0/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-6.0/sql-syntax-server-administration.xml 2008-09-02 17:34:12 UTC (rev 11641)
+++ trunk/refman-6.0/sql-syntax-server-administration.xml 2008-09-02 19:30:19 UTC (rev 11642)
Changed blocks: 3, Lines Added: 24, Lines Deleted: 12; 3080 bytes
@@ -2661,12 +2661,6 @@
[COMPRESSION_ALGORITHM [=] <replaceable>algorithm_name</replaceable>]]
</programlisting>
- <remark role="todo">
- The interpretation of relative filenames has not yet been
- settled. So recommend full pathname as a "best
- practice" for now.
- </remark>
-
<remark role="help-description-begin"/>
<para>
@@ -2675,12 +2669,21 @@
contents). The file must be named as a literal string. The file
can be a regular file, in which case, it must not already exist.
As of MySQL 6.0.6, the file can be an existing FIFO on Unix. The
- file should be specified as a full pathname. The file is written
- to the server host. Its location must be in a directory where
- the server can create and write files.
+ file is written to the server host. Its location must be in a
+ directory where the server can create and write files.
</para>
<para>
+ As of MySQL 6.0.7, the <literal>backupdir</literal> system
+ variable value is the default image file directory for
+ <literal>BACKUP DATABASE</literal> operations. If an image file
+ is named as a relative pathname, it is interpreted relative to
+ the value of <literal>backupdir</literal>. The default value is
+ the data directory. Before MySQL 6.0.7, the file should be
+ specified as a full pathname.
+ </para>
+
+ <para>
<literal>BACKUP DATABASE</literal> requires the
<literal>SUPER</literal> and <literal>FILE</literal> privileges,
as well as the <literal>SELECT</literal> privilege for all
@@ -2878,12 +2881,21 @@
Given a backup image file created by the <literal>BACKUP
DATABASE</literal> statement, <literal>RESTORE</literal>
restores the databases contained in the image. The image file
- must be named as a literal string. It should be specified as a
- full pathname. Its location must be in a directory where the
- server can read files.
+ must be named as a literal string. Its location must be in a
+ directory where the server can read files.
</para>
<para>
+ As of MySQL 6.0.7, the <literal>backupdir</literal> system
+ variable value is the default image file directory for
+ <literal>RESTORE</literal> operations. If an image file is named
+ as a relative pathname, it is interpreted relative to the value
+ of <literal>backupdir</literal>. The default value is the data
+ directory. Before MySQL 6.0.7, the file should be specified as a
+ full pathname.
+ </para>
+
+ <para>
<literal>RESTORE</literal> requires the <literal>SUPER</literal>
privilege.
</para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r11642 - in trunk: . dynamic-docs/changelog dynamic-docs/command-optvars refman-6.0 | paul.dubois | 2 Sep |
