- 11 Jun, 2004 1 commit
-
-
heikki@hundin.mysql.fi authored
Put back the ha_innodb.cc source code lines that were accidentally removed in Jan Lindstrom's push yesterday (he used the account heikki@mysql.com)
-
- 10 Jun, 2004 15 commits
-
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/mysql/mysql-4.1-root
-
konstantin@mysql.com authored
some reason wasn't included before. A lot of files cleaned up from #include <assert.h>
-
bell@sanja.is.com.ua authored
close table before opening in optimize
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-count-4.1
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.1-874
-
guilhem@mysql.com authored
exactly it's mapped to "ALTER TABLE t; ANALYZE TABLE t;"
-
bar@mysql.com authored
-
guilhem@mysql.com authored
New option --sync-binlog=x (and global settable variable) which will fsync the binlog after every x-th disk write to it. That is, if in autocommit mode, after every x-th statement written to the binlog; if using transactions, after every x-th transaction written to the binlog. x==0 means no fsync. x==1 is the slowest. There is no test added for this, I have just checked that it works as --sync-binlog=1 dramatically slows down mysqld. Made sync-frm a global settable variable.
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.1-1595
-
guilhem@mysql.com authored
error messages when a query goes wrong. Note that from now on, if you run with --slave-skip-error=xx, then nothing will be printed to the error log when the slave is having this error xx and skipping it (but you don't care as you want to skip it).
-
heikki@hundin.mysql.fi authored
Added function /*********************************************************************** This function stores binlog offset and flushes logs */ void innobase_store_binlog_offset_and_flush_log(char *binlog_name,longlong offset) requested by Guilhem to ha_innodb.cc and ha_innodb.h. Change made by Jan.Lindstrom@innodb.com
-
pem@mysql.com authored
into mysql.com:/home/pem/work/mysql-4.1
-
pem@mysql.comhem.se authored
-
bell@sanja.is.com.ua authored
-
tomas@mc05.(none) authored
into mc05.(none):/space2/tomas/mysql-4.1-ndb-test
-
- 09 Jun, 2004 5 commits
-
-
konstantin@mysql.com authored
The bug was caused by error in hash calculation function: it always returned hash value for last field in a composite key, so for keys like (a text, b char(1)) we were always getting bad hash values.
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.1-874
-
guilhem@mysql.com authored
binlog even if they changed nothing, and a test for this. This is useful when users use these commands to clean up their master and slave by issuing one command on master (assume master and slave have slightly different data for some reason and you want to clean up both). Note that I have not changed multi-table DELETE and multi-table UPDATE because their error-reporting mechanism is more complicated.
-
bar@mysql.com authored
Fix to be ANSI C complient ,
-
ndbdev@ndbmaster.mysql.com authored
-
- 08 Jun, 2004 19 commits
-
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/mysql/mysql-4.1-4026
-
konstantin@mysql.com authored
is broken (prepared statements)": fixed date handling in many places of prepared statements code.
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.1-874
-
guilhem@mysql.com authored
In mysqlbinlog, there was a problem with how we escaped the content of a string user variable. To be perfect, we should have escaped with character_set_client. But this charset is unknown to mysqlbinlog. So the simplest is to print the string in hex. This is unreadable but 100% safe with any charset (checked with Bar), no more need to bother with character_set_client.
-
ndbdev@ndbmaster.mysql.com authored
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-4.1
-
bar@bar.intranet.mysql.r18.ru authored
-
jplindst@t41.(none) authored
to ha_innodb.cc and ha_innodb.h
-
bar@bar.intranet.mysql.r18.ru authored
-
bar@bar.intranet.mysql.r18.ru authored
into bar.intranet.mysql.r18.ru:/usr/home/bar/mysql-4.1
-
tomas@mc05.(none) authored
into mc05.(none):/space2/tomas/mysql-4.1-ndb-test
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1-ndb
-
bar@bar.intranet.mysql.r18.ru authored
-
heikki@hundin.mysql.fi authored
Fix Bug #4047: remove the improvement ported from 4.0 that made InnoDB to remember the original select_lock_type inside LOCK TABLES
-
tomas@mc05.(none) authored
into mc05.(none):/space2/tomas/mysql-4.1-ndb-test
-
bar@bar.intranet.mysql.r18.ru authored
-
tomas@poseidon.bredbandsbolaget.se authored
into poseidon.bredbandsbolaget.se:/home/tomas/mysql-4.1-ndb
-
tomas@poseidon.bredbandsbolaget.se authored
-