List:Commits« Previous MessageNext Message »
From:mcbrown Date:February 7 2007 4:41pm
Subject:svn commit - mysqldoc@docsrva: r4842 - trunk/falcon
View as plain text  
Author: mcbrown
Date: 2007-02-07 17:41:27 +0100 (Wed, 07 Feb 2007)
New Revision: 4842

Log:
Docs Bug #26068
Adding changelog to Falcon docs
Uncommenting falcon_page_size option



Added:
   trunk/falcon/news-falcon.xml
Modified:
   trunk/falcon/falcon-overview.xml
   trunk/falcon/falcon.xml
   trunk/falcon/se-falcon.xml


Modified: trunk/falcon/falcon-overview.xml
===================================================================
--- trunk/falcon/falcon-overview.xml	2007-02-07 14:51:48 UTC (rev 4841)
+++ trunk/falcon/falcon-overview.xml	2007-02-07 16:41:27 UTC (rev 4842)
Changed blocks: 2, Lines Added: 58, Lines Deleted: 59; 6511 bytes

@@ -6,21 +6,20 @@
   %fixedchars.entities;
 ]>
 <chapter id="falcon-overview">
-  
+
   <title>The Falcon Storage Engine</title>
-  
+
   <para>
-    Falcon is a Storage Engine for the MySQL database server. A
-    storage engine provides the mechanics for storing, indexing and
-    retreiving information from the physical store of the data. Other
-    storage engines available for MySQL include
-    <xref linkend="innodb"/> and <xref
-      linkend="myisam"/>. For
-    more information on storage engines for MySQL, see
-    <xref linkend="storage-engines"/>. For more detail on MySQL, see
-    the <xref linkend="top"/>.
+    Falcon is a Storage Engine for the MySQL database server. A storage
+    engine provides the mechanics for storing, indexing and retreiving
+    information from the physical store of the data. Other storage
+    engines available for MySQL include <xref linkend="innodb"/> and
+    <xref
+      linkend="myisam"/>. For more information on storage
+    engines for MySQL, see <xref linkend="storage-engines"/>. For more
+    detail on MySQL, see the <xref linkend="top"/>.
   </para>
-  
+
   <para>
     The Falcon Storage Engine has been designed with modern database
     requirements in mind, and particularly for use within high-volume

@@ -28,112 +27,112 @@
     while still supporting the transactional and logging functionality
     required in this environment.
   </para>
-  
+
   <para>
-    Falcon is currently available only for the 32-bit Windows and
-    32-bit or 64-bit Linux operating systems. Additional platforms
-    will be added after the alpha release.
+    Falcon is currently available only for the 32-bit Windows and 32-bit
+    or 64-bit Linux operating systems. Additional platforms will be
+    added after the alpha release.
   </para>
-  
+
   <section id="se-falcon-features">
-    
+
     <title>Falcon Features</title>
-    
+
     <para>
       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.
+      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>
-      The Falcon storage engine is designed to work within
-      high-traffic transactional applications. It supports a number of
-      key features that make this possible:
+      The Falcon storage engine is designed to work within high-traffic
+      transactional applications. It supports a number of key features
+      that make this possible:
     </para>
-    
+
     <itemizedlist>
-      
+
       <listitem>
         <para>
-          True Multi Version Concurrency Control (MVCC) enables
-          records and tables to be updated without the overhead
-          associated with row-level locking mechanisms. The MVCC
-          implementation virtually eliminates the need to lock tables
-          or rows during the update process.
+          True Multi Version Concurrency Control (MVCC) enables records
+          and tables to be updated without the overhead associated with
+          row-level locking mechanisms. The MVCC implementation
+          virtually eliminates the need to lock tables or rows during
+          the update process.
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
-          Flexible locking, including flexible locking levels and
-          smart deadlock detection 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>
-      
+
       <listitem>
         <para>
-          Optimized for modern CPUs and environments to support
-          multiple threads allowing multiple transactions and fast
-          transaction handling.
+          Optimized for modern CPUs and environments to support multiple
+          threads allowing multiple transactions and fast transaction
+          handling.
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Transaction-safe (fully ACID-compliant) and able to handle
           multiple concurrent transactions.
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
-          Serial Log provides high performance and recovery
-          capabilities without sacrificing performance.
+          Serial Log provides high performance and recovery capabilities
+          without sacrificing performance.
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Advanced B-Tree indexes.
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Data compression stores the information on disk in a
           compressed format, compressing and decompressing data on the
-          fly. The result is in smaller and more efficient physical
-          data sizes.
+          fly. The result is in smaller and more efficient physical data
+          sizes.
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
-          Intelligent disk management automatically manages disk file
-          size, extensions and space reclamation.
+          Intelligent disk management automatically manages data file
+          files and extensions. Space within log and data files is
+          automatically reclaimed and reused.
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Data and index caching provides quick access to data without
           the requirement to load index data from disk.
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
-          Implicit savepoints ensure data integrity during
-          transactions.
+          Implicit savepoints ensure data integrity during transactions.
         </para>
       </listitem>
-      
+
     </itemizedlist>
-    
+
   </section>
-  
+
 </chapter>


Modified: trunk/falcon/falcon.xml
===================================================================
--- trunk/falcon/falcon.xml	2007-02-07 14:51:48 UTC (rev 4841)
+++ trunk/falcon/falcon.xml	2007-02-07 16:41:27 UTC (rev 4842)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 0; 416 bytes

@@ -69,4 +69,6 @@
   
   <xi:include href="se-falcon.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
 
+  <xi:include href="news-falcon.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
 </book>


Added: trunk/falcon/news-falcon.xml
===================================================================
--- trunk/falcon/news-falcon.xml	                        (rev 0)
+++ trunk/falcon/news-falcon.xml	2007-02-07 16:41:27 UTC (rev 4842)
Changed blocks: 1, Lines Added: 115, Lines Deleted: 0; 2859 bytes

@@ -0,0 +1,115 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
+[
+  <!ENTITY % fixedchars.entities  SYSTEM "../common/fixedchars.ent">
+  %fixedchars.entities;
+]>
+<appendix id="news-falcon">
+
+  <title>Changes in MySQL 5.2 Falcon</title>
+
+  <para>
+    An overview of the changes in the MySQL 5.2 Falcon release sequence.
+  </para>
+
+  <section id="news-falcon-5-2-2">
+
+    <title>Changes in release 5.2.2 (not yet released)</title>
+
+    <para>
+      Bugs fixed:
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          MySQL would fail with an assertion on startup. (Bug #25835)
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+  </section>
+
+  <section id="news-falcon-5-2-1">
+
+    <title>Changes in release 5.2.1 (not released)</title>
+
+    <para>
+      Functionality added or changed
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          Performance improvements: thread bottleneckes have been
+          reduced when a larger number of parallel auto-commit threads
+          executed a tribial query in a hard loop.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          You can now configure the page size use for storing data and
+          indexes. The new paramter is called
+          <literal>falcon_page_size</literal>. For more information see
+          <xref linkend="se-falcon-configuration"/>.
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+    <para>
+      Bugs fixed:
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          Setting <literal>falcon_page_size</literal> to non-default
+          size crashes Falcon. (Bug #23220)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Between fails with Unicode field. (Bug #24511)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Crash if create index on nullable <literal>utf8</literal>
+          column. (Bug #25555)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          MySQL crashes during <literal>DROP TABLE</literal> after
+          <literal>CREATE TABLE ... SELECT *</literal>. (Bug #25564)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Assertion when killing a <literal>CREATE TABLE ...
+          SELECT</literal> statement. (Bug #25565)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Falcon compound primary key problem. (Bug #25828)
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+  </section>
+
+</appendix>


Modified: trunk/falcon/se-falcon.xml
===================================================================
--- trunk/falcon/se-falcon.xml	2007-02-07 14:51:48 UTC (rev 4841)
+++ trunk/falcon/se-falcon.xml	2007-02-07 16:41:27 UTC (rev 4842)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 3; 666 bytes

@@ -32,8 +32,7 @@
 
     <itemizedlist>
 
-<!-- [MC] Commented out, not in Alpha release
-      <listitem>
+<listitem>
         <para>
           <literal>falcon_page_size</literal> &mdash; (Page Size)
           controls the size of the pages used to store information

@@ -41,8 +40,8 @@
           KB.
         </para>
       </listitem>
--->
 
+
       <listitem>
         <para>
           <literal>falcon_min_record_memory</literal> &mdash; (Record


Thread
svn commit - mysqldoc@docsrva: r4842 - trunk/falconmcbrown7 Feb