Author: mcbrown
Date: 2006-11-22 12:55:53 +0100 (Wed, 22 Nov 2006)
New Revision: 4005
Log:
Updates based on Calvin's comments
Modified:
trunk/refman-5.1/se-falcon.xml
Modified: trunk/refman-5.1/se-falcon.xml
===================================================================
--- trunk/refman-5.1/se-falcon.xml 2006-11-21 20:10:05 UTC (rev 4004)
+++ trunk/refman-5.1/se-falcon.xml 2006-11-22 11:55:53 UTC (rev 4005)
Changed blocks: 14, Lines Added: 86, Lines Deleted: 44; 8841 bytes
@@ -50,13 +50,12 @@
<title>Falcon Features</title>
&falcon-warning;
<para>
- Falcon is primarily a memory-based storage engine and has been
- specially developed for systems that are able to support larger
- memory architectures and multi-threaded or multi-core CPU
- environments. Most 64-bit architectures are ideal platforms for
- the Falcon engine, where there is a larger available memory space
- and 2-, 4- or 8-core CPUs available. It can also be deployed
- within a standard 32-bit environment.
+ Falcon has been specially developed for systems that are able to
+ support larger memory architectures and multi-threaded or
+ multi-core CPU environments. Most 64-bit architectures are ideal
+ platforms for the Falcon engine, where there is a larger available
+ memory space and 2-, 4- or 8-core CPUs available. It can also be
+ deployed within a standard 32-bit environment.
</para>
<para>
@@ -79,9 +78,9 @@
<listitem>
<para>
- Flexible locking, including flexible locking levels, smart
- deadlock detection and lock timeouts keep data protected and
- transactions and operations flowing at full speed.
+ Flexible locking, including flexible locking levels and smart
+ deadlock detection keep data protected and transactions and
+ operations flowing at full speed.
</para>
</listitem>
@@ -131,13 +130,6 @@
<listitem>
<para>
- Configurable page sizes enable you to select the page size
- according to your data needs.
- </para>
- </listitem>
-
- <listitem>
- <para>
Intelligent disk management automatically manages disk file
size, extensions and space reclamation.
</para>
@@ -176,6 +168,7 @@
<itemizedlist>
+<!-- [MC] Commented out, not in Alpha release
<listitem>
<para>
<literal>falcon_page_size</literal> — (Page Size)
@@ -184,6 +177,7 @@
KB.
</para>
</listitem>
+-->
<listitem>
<para>
@@ -226,6 +220,7 @@
</para>
</listitem>-->
+<!--[MC] Not supported in alpha release
<listitem>
<para>
<literal>falcon_log_dir</literal> — (Log file location)
@@ -236,6 +231,7 @@
the tablespace file.
</para>
</listitem>
+-->
<!--
<remark>
@@ -291,17 +287,19 @@
</para>
</listitem>
+<!--[MC] Not supported in alpha release (remember to add back hyphens)
<listitem>
<para>
- <literal>--falcon-page-size=#</literal>
+ <literal>falcon-page-size=#</literal>
</para>
</listitem>
<listitem>
<para>
- <literal>--falcon-log-dir=<replaceable>name</replaceable></literal>
+ <literal>falcon-log-dir=<replaceable>name</replaceable></literal>
</para>
</listitem>
+-->
</itemizedlist>
@@ -336,23 +334,25 @@
<title>Creating the Falcon Tablespace</title>
<para>
- Within Falcon, all data is stored within a single tablespace,
- which in turn is stored within a single file within the MySQL
- directory structure. A single Falcon database will create three
- main files. One file contains the Falcon data and will be stored
- in a file with the name of the Falcon database with the extension
- <filename>.fts</filename>. For example, Falcon tables defined
- within the database <literal>test</literal> will be stored within
- the file <filename>test.fts</filename> within the main MySQL data
- directory.
+ Within Falcon, all data within one database is stored within a
+ single tablespace, which in turn is stored within a single file
+ within the MySQL directory structure. A single Falcon database
+ will create three main files. One file contains the Falcon data
+ and will be stored in a file with the name of the Falcon database
+ with the extension <filename>.fts</filename>. For example, Falcon
+ tables defined within the database <literal>test</literal> will be
+ stored within the file <filename>test.fts</filename> within the
+ main MySQL data directory.
</para>
<para>
Two further files contain the on-disk copy of the Falcon serial
log. These are also created within the realm of the corresponding
- database. So with the above example data file
- <filename>test.fts</filename> the log files will be named
- <filename>test.fl1</filename> and <filename>test.fl2</filename>.
+ database. In a future release, you will be able to specify an
+ alternate location for these log files. So with the above example
+ data file <filename>test.fts</filename> the log files will be
+ named <filename>test.fl1</filename> and
+ <filename>test.fl2</filename>.
</para>
<para>
@@ -360,7 +360,8 @@
within a <literal>.frm</literal> file within a database specific
directory. For example, the table <literal>falcontest</literal>
within the <literal>test</literal> database will create the table
- definition file <filename>falcontest.frm</filename>.
+ definition file <filename>falcontest.frm</filename> within the
+ directory test.
</para>
<para>
@@ -470,9 +471,11 @@
<listitem>
<para>
- <emphasis role="bold">Work Threads</emphasis> — move
- data from the Falcon Serial Log into the database page cache
- and from the page cache to disk.
+ <emphasis role="bold">Work Threads</emphasis> — are
+ background threads. There are two threads, the "gopher" thread
+ moves data from the Falcon Serial Log into the database page
+ cache and from the page cache to disk. The second is the page
+ writer thread which writes blob pages.
</para>
</listitem>
@@ -746,12 +749,13 @@
<title>Falcon Crash Recovery</title>
<para>
- The Falcon Serial Log is used automatically during startup to
- recover transactions and update the database. When transactions
- and changes are written to the Serial Log the log includes
- entries that record changes to all areas of the database,
- including the indexes, changes to <literal>BLOB</literal> data,
- and any structural changes to the database.
+ The Falcon Serial Log is used automatically when the first table
+ in a Falcon database is opened to recover transactions and
+ update the database. When transactions and changes are written
+ to the Serial Log the log includes entries that record changes
+ to all areas of the database, including the indexes, changes to
+ <literal>BLOB</literal> data, and any structural changes to the
+ database.
</para>
<para>
@@ -913,23 +917,48 @@
<title>Limits</title>
&falcon-warning;
<para>
- There are a number of limits in the current version of Falcon:
+ There are a number of limits in the alpha release of Falcon; these
+ will be addressed in forthcoming versions:
</para>
<itemizedlist>
<listitem>
<para>
+ <literal>SELECT FOR UPDATE</literal> is not supported.
+ </para>
+ </listitem>
+
+ <listitem>><para>
+ Serializable isolation levels are not supported.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Lock timeout configuration is not supported.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Distributed transactions are not supported.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
There is a limit of 2<superscript>32</superscript> (4.29
billion) rows for a single table. By using multiple tables
within the same tablespace you can have more than this number
- of records.
+ of records. In future releases this limit will be removed.
</para>
</listitem>
<listitem>
<para>
- Pages can be a maximum of 32768 bytes in size.
+ Configurable page sizes are not supported, but are planned for
+ a future release.
</para>
</listitem>
@@ -949,6 +978,19 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ Online backup is not supported, but support is planned in a
+ future release.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Foreign key support is currently not available.
+ </para>
+ </listitem>
+
</itemizedlist>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r4005 - trunk/refman-5.1 | mcbrown | 22 Nov |
