dbTalk Databases Forums  

bk commit - mysqldoc tree (heikki:1.2826)

mailing.database.mysql-internals mailing.database.mysql-internals


Discuss bk commit - mysqldoc tree (heikki:1.2826) in the mailing.database.mysql-internals forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Heikki Tuuri
 
Posts: n/a

Default bk commit - mysqldoc tree (heikki:1.2826) - 04-06-2005 , 08:30 AM






Below is the list of changes that have just been committed into a local
mysqldoc repository of heikki. When heikki 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/Install...urce_tree.html

ChangeSet
1.2826 05/04/06 15:43:19 heikki (AT) hundin (DOT) mysql.fi +1 -0
manual.texi:
Add InnoDB-4.1.11 change notes

Docs/manual.texi
1.2663 05/04/06 15:43:12 heikki (AT) hundin (DOT) mysql.fi +17 -0
Add InnoDB-4.1.11 change notes

# 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: heikki
# Host: hundin.mysql.fi
# Root: /home/heikki/mysqldoc

--- 1.2662/Docs/manual.texi Wed Apr 6 14:33:02 2005
+++ 1.2663/Docs/manual.texi Wed Apr 6 15:43:12 2005
@@ -99766,6 +99766,23 @@
created in the temporary directory of the operating system. On Netware,
@code{InnoDB} will continue to ignore @code{--tmpdir}. (Bug #5822)
@item
+@code{InnoDB}: If MySQL wrote to its binlog, but for some
+reason @code{trx->update_undo}
+and @code{trx->insert_undo} were NULL in InnoDB, then
+@code{trx->commit_lsn} was garbage, and InnoDB could assert in the log flush
+of @code{trx_commit_complete_for_mysql()}. (Bug #9277)
+@item
+@code{InnoDB}: If InnoDB cannot allocate memory, keep retrying for 60 seconds
+before we intentionally crash @file{mysqld}; maybe the memory shortage is
+just temporary.
+@item
+@code{InnoDB}: If one used @code{LOCK TABLES}, created an InnoDB temp table,
+and did a multi-table update where a MyISAM table was the update table and
+the temp table was a read table, then InnoDB asserted in @file{row0sel.c}
+because @code{n_mysql_tables_in_use} was 0. Also, we remove the assertion
+altogether and just print an error to
+the @file{.err} log if this important consistency check fails. (Bug #8677)
+@item
@command{mysqldump} now avoids writing @code{SET NAMES} to the dump output
if the server is older than version 4.1 and would not understand that
statement. (Bug #7997)

--
MySQL Internals Mailing List
For list archives: http://lists.mysql.com/internals
To unsubscribe: http://lists.mysql.com/internals?uns...ie.nctu.edu.tw


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.