| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| | |
into mysql.com:/home/wax/mysql/mysql-4.0chsize
|
| |
| |
| |
| |
| |
| | |
Add functions SetFilePointerEx and SetEndOfFile for huge
tables instead of chsize
Move chsize to right place
|
|\ \
| | |
| | |
| | | |
into sanja.is.com.ua:/home/bell/mysql/bk/work-merged_qc-4.0
|
| |\ \
| | | |
| | | |
| | | | |
into mysql.com:/home/dlenev/src/mysql-4.0-bugfix
|
| | | |
| | | |
| | | |
| | | | |
ignorant about ssl_type attribute
|
|/ / / |
|
|/ /
| |
| |
| | |
Fix bug introduced in 4.0.13 and reported by Emic: if a CREATE TABLE ended in a comment, a memory overrun could happen
|
| |
| |
| |
| | |
innodb_fast_shutdown CAN take an argument though it was not specified so in mysqld.cc
|
| |
| |
| |
| | |
binary logging.
|
|\ \
| | |
| | |
| | | |
into mysql.com:/home/mysql_src/mysql-4.0
|
| | |
| | |
| | |
| | |
| | | |
so that it really tests replication of SET FOREIGN_KEY_CHECKS (previously
it used MyISAM).
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Merge
trx0trx.c:
Print more info about a trx in SHOW INNODB status; try to find the bug reported by Plaxo
buf0buf.c:
Check that page log sequence numbers are not in the future
log0recv.c, log0log.c:
Fixed a bug: if you used big BLOBs, and your log files were relatively small, InnoDB could in a big BLOB operation temporarily write over the log produced AFTER the latest checkpoint. If InnoDB would crash at that moment, then the crash recovery would fail, because InnoDB would not be able to scan the log even up to the latest checkpoint. Starting from this version, InnoDB tries to ensure the latest checkpoint is young enough. If that is not possible, InnoDB prints a warning to the .err log
|
|\ \ \
| |/ /
|/| |
| | | |
into gluh.mysql.r18.ru:/home/gluh/mysql-4.0.fix
|
| | | |
|
|\ \ \
| |/ /
|/| |
| | | |
into mysql.com:/home/mysql_src/mysql-4.0
|
| | |
| | |
| | |
| | |
| | | |
just a flush_relay_log_info() at the end of CHANGE MASTER
(there was already flush_master_info()).
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I extended the task to cleaning error messages, making them look nicer,
and making the output of SHOW SLAVE STATUS (column Last_error) be as complete
as what's printed on the .err file;
previously we would have, for a failure of a replicated LOAD DATA INFILE:
- in the .err, 2 lines:
"duplicate entry 2708 for key 1"
"failed loading SQL_LOAD-5-2-2.info"
- and in SHOW SLAVE STATUS, only:
"failed loading SQL_LOAD-5-2-2.info".
Now SHOW SLAVE STATUS will contain the concatenation of the 2 messages.
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | | |
into gluh.mysql.r18.ru:/home/gluh/mysql-4.0.fix
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Here is fix for bug 554.
Added configure options
--with-openssl-includes[=DIR] and --with-openssl-libs[=DIR]
|
| | | |
| | | |
| | | |
| | | | |
- bumped up version number in configure.in to 4.0.15
|
|/ / /
| | |
| | |
| | | |
Fix bug: if there was a 'record too long' error in an insert, InnoDB forgot to free reserved file space extents; they were only freed in mysqld restart
|
| | |
| | |
| | |
| | | |
Fix an error in the previous push
|
| | |
| | |
| | |
| | | |
Fix bug reported by Dyego Souza do Carmo: if a row becomes too long, > 8000 bytes, in an update, then InnoDB simply removes the clustered index record and does not report of table handler error 139
|
|/ / |
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | | |
into deer.(none):/home/hf/work/mysql-4.0
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Monty revoked any locks for temporary tables in
ha_myisam::external_lock()
But further code bans using write cache on nonlocked tables
this makes operations much slower
|
|\ \ \
| | | |
| | | |
| | | | |
into mashka.(none):/home/my/mysql-4.0
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
|
| | | | |
| | | | |
| | | | |
| | | | | |
went away.
|
|\ \ \ \ \
| | |/ / /
| |/| | |
| | | | | |
into mysql.com:/space/my/mysql-4.0
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | | |
into narttu.mysql.fi:/my/mysql-4.0
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
auto_increment key where one part was a packed CHAR
|
|\ \ \ \ \ \
| |/ / / / /
| | | | | |
| | | | | | |
into mysql.com:/space/my/mysql-4.0-build
|
| |\ \ \ \ \
| | |_|/ / /
| |/| | | |
| | | | | | |
into eagle.mysql.r18.ru:/home/vva/work/BUG_683/mysql-4.0
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
as requested by PeterZ
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
a node name was changed in manual.texi which resulted in a very large
ReadMe.txt file, as the generating script could not find the (renamed)
ending node. Fixed the ending node name in Docs/Makefile.am and the
Docs/Support/generate-text-files.pl Perl script to make sure this does
not happen again (I only discovered this because the Do-pkg script was
not able to add the ReadMe.txt to the Apple Disk image because it ran out
of disk space due to the size of the file)
|
|\ \ \ \ \
| |/ / / /
|/| | | |
| | | | | |
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
|
| | | | | |
|
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | | |
in mysqld_safe (commented out by default), to not override any options
defined in my.cnf (thanks to Axel Schwenke from Jobpilot.de for the
suggestion)
|
| | | | |
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Fixed test for binary build
|