Author: mcbrown
Date: 2007-08-31 14:32:34 +0200 (Fri, 31 Aug 2007)
New Revision: 7623
Log:
Documenting dev bugs:
Bug #30578
Bug #30124
Bug #28351
Bug #29169
Bug #30564
Moving 6.0.1 to 6.0.2 in prep for Alpha release
Adding stubs for options that should be in 6.0.2 Falcon but are not showing
Modified:
trunk/falcon/news-falcon.xml
trunk/falcon/se-falcon.xml
Modified: trunk/falcon/news-falcon.xml
===================================================================
--- trunk/falcon/news-falcon.xml 2007-08-31 11:20:57 UTC (rev 7622)
+++ trunk/falcon/news-falcon.xml 2007-08-31 12:32:34 UTC (rev 7623)
Changed blocks: 5, Lines Added: 99, Lines Deleted: 2; 4541 bytes
@@ -18,9 +18,9 @@
</para>
</note>
- <section id="news-falcon-6-0-1">
+ <section id="news-falcon-6-0-2">
- <title>Changes in release 6.0.1 (Not yet released)</title>
+ <title>Changes in release 6.0.2 (Not yet released)</title>
<para>
Functionality added or changed:
@@ -34,6 +34,15 @@
</para>
</listitem>
+<listitem><para>Mac OS X (Intel) support has been added. Mac OS X is not
+ currently a supported platform. To build on Mac OS X from the repository
+ sources you must have the most
+ recent versions of <literal>bison</literal>, <literal>automake</literal>,
+ <literal>autoconf</literal> and <literal>libtool</literal> installed.</para>
+<para>There are known issues with the Falcon on Mac OS X build. (Bug #30564)</para>
+
+</listitem>
+
<listitem>
<para>
Support for tablespaces.
@@ -49,6 +58,43 @@
</para>
</listitem>
+<!--
+ <listitem>
+ <para>
+ The Falcon record cache parameters have been altered. The
+ <literal>falcon_max_record_memory</literal> and
+ <literal>falcon_min_record_memory</literal> are no longer
+ supported.
+ </para>
+ <para>
+ Instead, the <literal>falcon_record_memory_max</literal>,
+ <literal>falcon_record_scavenge_threshold</literal>,
+ <literal>falcon_record_scavenge_floor</literal> and
+ <literal>falcon_inital_allocation</literal> parameters are now
+ used to control the caching of records in memory within
+ Falcon. See <xref
+ linkend="se-falcon-configuration"/>. (Bug
+ #30083)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The option <option>falcon_initial_allocation</option> has been
+ added to control the initial size of a Falcon tablespace on
+ disk.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The option <option>falcon_disable_fsync</option> has been
+ added. If set to true, then the periodic fsync operation is
+ disabled.
+ </para>
+ </listitem>
+-->
+
</itemizedlist>
<para>
@@ -57,8 +103,47 @@
<itemizedlist>
+<listitem><para>Some Falcon variables were marked as status variables. (Bug
+#29169)</para></listitem>
+ <listitem><para>Under certain situations the Falcon tables and log could
+ become corrupt and prevent recovery from a crashed version of the files.
+ (Bug #28351)</para></listitem>
+<listitem><para>Updating a large table without an index would lock all the
+ records during a transaction and unlock the records individually. (Bug #30124)</para></listitem>
<listitem>
<para>
+ Falcon would incorrectly allow creation of two tables with the
+ same name but different case sensitivity, without raising an
+ error, but treat the two tables as the same during further
+ queries. (Bug #30210).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When loading large datasets into a Falcon table
+ <command>mysqld</command> could crash. An Out of memory error
+ will now be raised in this situation. (Bug #30251)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ An assertion could be thrown during high number of concurrent
+ updates of <literal>BLOB</literal> fields. (Bug #30463)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Accessing an <literal>INFORMATION_SCHEMA</literal> table
+ generated by Falcon, when Falcon has not been enabled would
+ cause <command>mysqld</command> to crash. (Bug #29014)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Falcon could occasionally report a problem with a duplicate
key error during <literal>INSERT</literal> when inserting the
same data into a unique column on two or more connections
@@ -259,6 +344,18 @@
</section>
+ <section id="news-falcon-6-0-1">
+
+ <title>Changes in release 6.0.1 (Not released)</title>
+
+ <note><para>
+ This was an internal
+ release only, and no binaries were published.
+ </para>
+ </note>
+
+ </section>
+
<section id="news-falcon-6-0-0">
<title>Changes in release 6.0.0 (30 April 2007)</title>
Modified: trunk/falcon/se-falcon.xml
===================================================================
--- trunk/falcon/se-falcon.xml 2007-08-31 11:20:57 UTC (rev 7622)
+++ trunk/falcon/se-falcon.xml 2007-08-31 12:32:34 UTC (rev 7623)
Changed blocks: 2, Lines Added: 87, Lines Deleted: 9; 3760 bytes
@@ -172,15 +172,6 @@
<listitem>
<para>
- <literal>falcon_max_transaction_backlog</literal> — the
- maximum number of pending transactions that will be active
- before the update process is blocked until the number of
- pending transactions reduces.
- </para>
- </listitem>
-
- <listitem>
- <para>
<literal>falcon_min_record_memory</literal> — (Record
Cache Base) sets the minimum amount of memory that will be
allocated for caching record data. When cache memory is
@@ -194,8 +185,95 @@
</para>
</listitem>
+<!--
<listitem>
<para>
+ <literal>falcon_record_memory_max</literal> — the fixed
+ upper limit, in MB, of memory reserved by Falcon for the
+ record cache.
+ </para>
+
+ <para>
+ The default value is 250. Minimum value is 5MB.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>falcon_record_scavenge_threshold</literal> —
+ the percentage of <literal>falcon_record_memory_max</literal>
+ that will cause the scavenger thread to start removing old
+ generations of records from the record cache.
+ </para>
+
+ <para>
+ Default value is 67. The minimum accepted value is 10, and the
+ maximum is 100.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>falcon_record_scavenge_floor</literal> — the
+ percentage of
+ <literal>falcon_record_scavenge_threshold</literal> that will
+ be retained in the record cache after the scavenger thread has
+ completed execution.
+ </para>
+
+ <para>
+ You can determine the minimum size of the record cache using
+ this formula:
+ </para>
+
+<programlisting>min(falcon_record_memory_max
+ * (falcon_record_scavenge_threshold/100)
+ * (falcon_record_scavenge_floor/100))</programlisting>
+
+ <para>
+ The default value is 50. The minimum accepted value is 10, and
+ the maximum is 90.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>falcon_initial_allocation</literal> — the
+ amount of space, in MB, that should be preallocated on disk
+ when a new Falcon tablespace file is created.
+ </para>
+
+ <para>
+ The default value is 0 (no preallocation). The minimum value
+ is 10.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>falcon_disable_fsync</literal> — if true, the
+ periodic <literal>fsync</literal> operation to synchronize
+ data on disk is disabled. Setting this value to true may lead
+ to data loss, but may increase performance.
+ </para>
+
+ <para>
+ Default value is false (<literal>fsync</literal> is enabled).
+ </para>
+ </listitem>
+-->
+
+ <listitem>
+ <para>
+ <literal>falcon_max_transaction_backlog</literal> — the
+ maximum number of pending transactions that will be active
+ before the update process is blocked until the number of
+ pending transactions reduces.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>falcon_page_cache_size</literal> — (Page Cache
Size) sets the amount of memory that will be allocated for
caching pages from the tablespace file.
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7623 - trunk/falcon | mcbrown | 31 Aug |
