Below is the list of changes that have just been committed into a local
mysqldoc repository of stefan. When stefan does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html
ChangeSet
1.3184 05/08/05 23:04:28 stefan@stripped +8 -0
sql-syntax.xml, replication.xml:
Sync with refman
sql-syntax.xml:
positive (including zero) => non-negative
.sync, .ci:
Include refman-5.1
replication.xml:
Edits in teh field of global read lock
based on Ingo's and Guilhem's input (thanks!)
refman-5.1/sql-syntax.xml
1.2 05/08/05 23:04:20 stefan@stripped +2 -2
Sync with refman
refman-5.0/sql-syntax.xml
1.2 05/08/05 23:04:16 stefan@stripped +2 -2
Sync with refman
refman-4.1/sql-syntax.xml
1.25 05/08/05 23:04:13 stefan@stripped +2 -2
Sync with refman
refman-4.1/replication.xml
1.9 05/08/05 23:04:12 stefan@stripped +17 -5
Sync with refman
refman/sql-syntax.xml
1.32 05/08/05 23:03:48 stefan@stripped +2 -2
positive (including zero) => non-negative
refman/.sync
1.2 05/08/05 23:03:40 stefan@stripped +3 -1
Include refman-5.1
refman/replication.xml
1.11 05/08/05 23:02:47 stefan@stripped +17 -5
Edits in teh field of global read lock
based on Ingo's and Guilhem's input (thanks!)
refman/.ci
1.2 05/08/05 23:02:35 stefan@stripped +2 -0
Include refman-5.1
# This is a BitKeeper patch. What follows are the unified diffs for the
# set of deltas contained in the patch. The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User: stefan
# Host: apollon.site
# Root: /home/stefan/bk/mysqldoc
--- 1.1/refman-5.1/sql-syntax.xml 2005-08-05 19:47:02 +02:00
+++ 1.2/refman-5.1/sql-syntax.xml 2005-08-05 23:04:20 +02:00
@@ -6325,8 +6325,8 @@
The <literal>LIMIT</literal> clause can be used to constrain
the number of rows returned by the <literal>SELECT</literal>
statement. <literal>LIMIT</literal> takes one or two numeric
- arguments, which must both be positive integer constants
- (including zero).
+ arguments, which must both be non-negative integer
+ constants.
</para>
<para>
--- 1.8/refman-4.1/replication.xml 2005-08-01 16:04:06 +02:00
+++ 1.9/refman-4.1/replication.xml 2005-08-05 23:04:12 +02:00
@@ -1047,15 +1047,27 @@
<listitem>
<para>
- If you are using only <literal>MyISAM</literal> tables, flush
- all the tables and block write statements by executing a
- <literal>FLUSH TABLES WITH READ LOCK</literal> statement.
+ Flush all the tables and block write statements by executing a
+ <literal>FLUSH TABLES WITH READ LOCK</literal> statement:
</para>
-
<programlisting>
mysql> FLUSH TABLES WITH READ LOCK;
</programlisting>
-
+ <para>
+ For <literal>InnoDB</literal> tables, note the following:
+ <literal>FLUSH TABLES WITH READ LOCK</literal>
+ blocks <literal>COMMIT</literal> operations, too.
+ (This is true as of MySQL version 4.0.20.)
+ When you have acquired your global read lock, you can start a
+ filesystem snapshot of your <literal>InnoDB</literal> tables,
+ but it will be not necessarily be consistent (because the
+ <literal>InnoDB</literal> caches are not flushed). This means
+ that <literal>InnoDB</literal> will perform a crash recovery
+ when started on this snapshot, but it will not be corrupted.
+ If you want to have a consistent snapshot of your
+ <literal>InnoDB</literal> tables, there's no way around taking
+ down the MySQL server, though.
+ </para>
<para>
Leave the client running from which you issue the
<literal>FLUSH TABLES</literal> statement so that the read
--- 1.24/refman-4.1/sql-syntax.xml 2005-08-04 11:10:45 +02:00
+++ 1.25/refman-4.1/sql-syntax.xml 2005-08-05 23:04:13 +02:00
@@ -6422,8 +6422,8 @@
The <literal>LIMIT</literal> clause can be used to constrain
the number of rows returned by the <literal>SELECT</literal>
statement. <literal>LIMIT</literal> takes one or two numeric
- arguments, which must both be positive integer constants
- (including zero).
+ arguments, which must both be non-negative integer
+ constants.
</para>
<para>
--- 1.10/refman/replication.xml 2005-08-05 14:55:28 +02:00
+++ 1.11/refman/replication.xml 2005-08-05 23:02:47 +02:00
@@ -1103,15 +1103,27 @@
<listitem>
<para>
- If you are using only <literal>MyISAM</literal> tables, flush
- all the tables and block write statements by executing a
- <literal>FLUSH TABLES WITH READ LOCK</literal> statement.
+ Flush all the tables and block write statements by executing a
+ <literal>FLUSH TABLES WITH READ LOCK</literal> statement:
</para>
-
<programlisting>
mysql> FLUSH TABLES WITH READ LOCK;
</programlisting>
-
+ <para>
+ For <literal>InnoDB</literal> tables, note the following:
+ <literal>FLUSH TABLES WITH READ LOCK</literal>
+ blocks <literal>COMMIT</literal> operations, too.
+ (This is true as of MySQL version 4.0.20.)
+ When you have acquired your global read lock, you can start a
+ filesystem snapshot of your <literal>InnoDB</literal> tables,
+ but it will be not necessarily be consistent (because the
+ <literal>InnoDB</literal> caches are not flushed). This means
+ that <literal>InnoDB</literal> will perform a crash recovery
+ when started on this snapshot, but it will not be corrupted.
+ If you want to have a consistent snapshot of your
+ <literal>InnoDB</literal> tables, there's no way around taking
+ down the MySQL server, though.
+ </para>
<para>
Leave the client running from which you issue the
<literal>FLUSH TABLES</literal> statement so that the read
--- 1.31/refman/sql-syntax.xml 2005-08-04 12:32:59 +02:00
+++ 1.32/refman/sql-syntax.xml 2005-08-05 23:03:48 +02:00
@@ -6533,8 +6533,8 @@
The <literal>LIMIT</literal> clause can be used to constrain
the number of rows returned by the <literal>SELECT</literal>
statement. <literal>LIMIT</literal> takes one or two numeric
- arguments, which must both be positive integer constants
- (including zero).
+ arguments, which must both be non-negative integer
+ constants.
</para>
<para>
--- 1.1/refman-5.0/sql-syntax.xml 2005-08-05 19:11:26 +02:00
+++ 1.2/refman-5.0/sql-syntax.xml 2005-08-05 23:04:16 +02:00
@@ -6325,8 +6325,8 @@
The <literal>LIMIT</literal> clause can be used to constrain
the number of rows returned by the <literal>SELECT</literal>
statement. <literal>LIMIT</literal> takes one or two numeric
- arguments, which must both be positive integer constants
- (including zero).
+ arguments, which must both be non-negative integer
+ constants.
</para>
<para>
--- 1.1/refman/.ci 2005-06-21 13:19:37 +02:00
+++ 1.2/refman/.ci 2005-08-05 23:02:35 +02:00
@@ -3,4 +3,6 @@
bk ci -y"Sync with refman"
cd ../refman-5.0
bk ci -y"Sync with refman"
+cd ../refman-5.1
+bk ci -y"Sync with refman"
cd ../refman
--- 1.1/refman/.sync 2005-06-21 00:54:00 +02:00
+++ 1.2/refman/.sync 2005-08-05 23:03:40 +02:00
@@ -3,4 +3,6 @@
patch < ../refman/tempdiff
cd ../refman-5.0
patch < ../refman/tempdiff
-cd ../refman
\ No newline at end of file
+cd ../refman-5.1
+patch < ../refman/tempdiff
+cd ../refman
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (stefan:1.3184) | stefan | 5 Aug |
