List:Internals« Previous MessageNext Message »
From:monty Date:May 13 2005 10:34pm
Subject:bk commit - mysqldoc@docsrva tree (monty:1.2666)
View as plain text  
Below is the list of changes that have just been committed into a local
mysqldoc repository of monty. When monty 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.2666 05/05/14 01:34:21 monty@stripped +1 -0
  Changelog 4.0 & 5.0
  New description of current_insert

  Docs/manual.texi
    1.2857 05/05/14 01:34:14 monty@stripped +25 -4
    Changelog 4.0 & 5.0
    New description of current_insert

# 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:	monty
# Host:	narttu.mysql.com
# Root:	/home/my/mysqldoc

--- 1.2856/Docs/manual.texi	2005-05-13 23:01:39 +03:00
+++ 1.2857/Docs/manual.texi	2005-05-14 01:34:14 +03:00
@@ -20780,7 +20780,7 @@
 | collation_connection            | latin1_swedish_ci                                           |
 | collation_database              | latin1_swedish_ci                                           |
 | collation_server                | latin1_swedish_ci                                           |
-| concurrent_insert               | ON                                                          |
+| concurrent_insert               | 1                                                           |
 | connect_timeout                 | 5                                                           |
 | datadir                         | /usr/local/mysql/data/                                      |
 | date_format                     | %Y-%m-%d                                                    |
@@ -20882,7 +20882,6 @@
 | max_user_connections            | 0                                                           |
 | max_write_lock_count            | 4294967295                                                  |
 | myisam_data_pointer_size        | 4                                                           |
-| myisam_max_extra_sort_file_size | 107374182400                                                |
 | myisam_max_sort_file_size       | 107374182400                                                |
 | myisam_recover_options          | OFF                                                         |
 | myisam_repair_threads           | 1                                                           |
@@ -21126,6 +21125,16 @@
 @command{mysqld} with @code{--safe} or @code{--skip-new}.
 This variable was added in MySQL 3.23.7.
 
+In MySQL 5.0.6 this variable was changed to an integer that takes 3 values:
+
+@multitable @columnfractions .10 .75
+@item @strong{Value} @tab @strong{Description}
+@item 0 @tab Off
+@item 1 @tab (Default) Enables concurrent insert for MyISAM tables that doesn't have holes
+@item 2 @tab Enables concurrent inserts for all MyISAM tables. If table has a hole and is in use by another thread the new row will be inserted at end of table.  If table is not in use then MySQL will do a normal read lock and insert the new row into the hole.
+@end multitable
+
+
 @cindex timeout
 @item connect_timeout
 The number of seconds the @command{mysqld} server waits for a connect
@@ -21784,7 +21793,7 @@
 tables to use the slower key cache method to create the index.
 This variable was added in MySQL 3.23.37.
 @strong{Note}: The value is given in megabytes before 4.0.3 and
-in bytes thereafter.
+in bytes thereafter. This flag was removed in MySQL 5.0.6.
 
 @item myisam_max_sort_file_size
 The maximum size of the temporary file MySQL is allowed to use while
@@ -22375,7 +22384,6 @@
 @item @code{max_write_lock_count} @tab numeric @tab @code{GLOBAL}
 @item @code{multi_read_range} @tab numeric @tab @code{GLOBAL} | @code{SESSION}
 @item @code{myisam_data_pointer_size} @tab numeric @tab @code{GLOBAL}
-@item @code{myisam_max_extra_sort_file_size} @tab numeric @tab @code{GLOBAL} | @code{SESSION}
 @item @code{myisam_max_sort_file_size} @tab numeric @tab @code{GLOBAL} | @code{SESSION}
 @item @code{myisam_repair_threads} @tab numeric @tab @code{GLOBAL} | @code{SESSION}
 @item @code{myisam_sort_buffer_size} @tab numeric @tab @code{GLOBAL} | @code{SESSION}
@@ -65349,6 +65357,7 @@
 Used to help MySQL to decide when to use the slow but safe key cache index
 creation method. @strong{Note}: This parameter is given in megabytes
 before MySQL 4.0.3, and in bytes as of 4.0.3.
+This flag was removed in MySQL 5.0.6.
 
 @item myisam_max_sort_file_size
 
@@ -100011,6 +100020,15 @@
 Functionality added or changed:
 @itemize @bullet
 @item
+Removed not used variable @code{myisam_max_extra_sort_file_size}.
+@item
+Changed default value of @code{myisam_data_pointer_size} from 4 to 6.
+This allows us to avoid @code{table is full} errors for most cases.
+@item
+The variable @code{concurrent_insert} now takes 3 values.  Setting this to
+2 changes MyISAM to do concurrent inserts to end of table if table is in use
+by another thread.
+@item
 New @code{/*>} prompt for @command{mysql}. This prompt indicates that a
 @code{/* ... */} comment was begun on an earlier line and the closing
 @code{*/} sequence has not yet been seen.  (Bug #9186)
@@ -105156,6 +105174,9 @@
 
 Bugs fixed:
 @itemize @bullet
+@item
+Fixed wrong buffer usage for auto-increment key with blob part that caused
+@code{CHECK TABLE} to report that the table was wrong. (Bug #10045)
 @item
 The test in @command{configure} to see whether @code{CXX} specified
 @command{gcc} failed if @command{gcc} was specified as a full pathname.
Thread
bk commit - mysqldoc@docsrva tree (monty:1.2666)monty14 May