Fix a bug in the previous commit change and align also the buffer in simulataled aio for possible use in i/o to raw devices
innobase/os/os0file.c:
Fix a bug in the previous commit change and align also the buffer in simulataled aio for possible use in i/o to raw devices
Align the buffer used in initing a data file to zero; this may be needed if the data file is actually a raw device
innobase/os/os0file.c:
Align the buffer used in initing a data file to zero; this may be needed if the data file is actually a raw device
Suppress prints by slave.cc when there is a normal reconnect after the master has been quiet for the time of the net read timeout; this removes the Error 1159 messages many users have complained about in the replication of 3.23.51
sql/slave.cc:
Suppress prints by slave.cc when there is a normal reconnect after the master has been quiet for the time of the net read timeout; this removes the Error 1159 messages many users have complained about in the replication of 3.23.51
Increase max number of waiting threads to 10000 and put diagnostic prints if this value is exceeded
innobase/srv/srv0srv.c:
Increase max number of waiting threads to 10000 and put diagnostic prints if this value is exceeded
innobase/include/os0thread.h:
Increase max number of waiting threads to 10000 and put diagnostic prints if this value is exceeded
On Monty's suggestion move ha_drop_database back inside LOCK_mysql_create_db, but we release LOCK_open during it to let possible running queries complete. I tested this and it seemed to work also in complex concurrent DELETE, SELECT, DROP DATABASE, and CREATE DATABASE situations
sql/sql_db.cc:
On Monty's suggestion move ha_drop_database back inside LOCK_mysql_create_db, but we release LOCK_open during it to let possible running queries complete. I tested this and it seemed to work also in complex concurrent DELETE, SELECT, DROP DATABASE, and CREATE DATABASE situations
Revert Monty's change to the positioning of ha_drop_database(): otherwise a running query on a table to be dropped in DROP DATABASE always causes the server to hang
sql/sql_db.cc:
Revert Monty's change to the positioning of ha_drop_database(): otherwise a running query on a table to be dropped in DROP DATABASE always causes the server to hang
ppc64 and x86-64, fixed a compile bug when building with TCP wrapper
support on Linux
bdb/dist/acconfig.h:
Added patch for x86_64 (provided by SuSE)
bdb/dist/aclocal/mutex.m4:
Added patch for x86_64 (provided by SuSE)
bdb/include/mutex.h:
Added patch for x86_64 (provided by SuSE)
include/global.h:
Added a SMP-related patch for PPC64 (provided by SuSE)
sql/mysqld.cc:
Compile fix for Linux when compiling with --with-librwap
Fix for access problem (merge from 4.0)
sql/sql_db.cc:
Do handler specific drop-database at safe place.
sql/sql_parse.cc:
Fix for access problem (merge from 4.0)
Update my.cnf example files to reflect InnoDB autoextend and also simplify them for InnoDB
support-files/my-large.cnf.sh:
Update my.cnf example files to reflect InnoDB autoextend and also simplify them for InnoDB
support-files/my-medium.cnf.sh:
Update my.cnf example files to reflect InnoDB autoextend and also simplify them for InnoDB
support-files/my-small.cnf.sh:
Update my.cnf example files to reflect InnoDB autoextend and also simplify them for InnoDB
support-files/my-huge.cnf.sh:
Update my.cnf example files to reflect InnoDB autoextend and also simplify them for InnoDB
I wish I had connection stop / start so that I could have made a
test case.
Docs/manual.texi:
This is the only way to fix ALTER TABLE bug with BDB
sql/sql_table.cc:
This is the only way to fix ALTER TABLE bug with BDB
Remove a debug printf which unintentionally was committed to the source tree
sql/ha_innobase.cc:
Remove a debug printf which unintentionally was committed to the source tree
Clarify the setting of innodb_data_file_path in my.cnf: it is in the [mysqld] section
sql/ha_innobase.cc:
Clarify the setting of innodb_data_file_path in my.cnf: it is in the [mysqld] section
Remove freeing of all memory at shutdown: since we do not exit the i/o-handlers and other threads, we could potentially get a seg fault at shutdown
innobase/srv/srv0start.c:
Remove freeing of all memory at shutdown: since we do not exit the i/o-handlers and other threads, we could potentially get a seg fault at shutdown
The UNIV_DEBUG version asserted if a foreign key check failed because of a lock wait timeout
btr0cur.c:
Fix a bug: if the primary key was updated (or delete + insert) so that only the case of characters changed, we were left with a dangling adaptive hash index pointer, often causing an assertion failure in page0page.ic line 515
innobase/btr/btr0cur.c:
Fix a bug: if the primary key was updated (or delete + insert) so that only the case of characters changed, we were left with a dangling adaptive hash index pointer, often causing an assertion failure in page0page.ic line 515
innobase/row/row0ins.c:
The UNIV_DEBUG version asserted if a foreign key check failed because of a lock wait timeout
Fix a bug: if buffer pool size > 2 GB on a 32-bit computer, we got an assertion failure because >> acted as a division operator (not as a register shift) for a wrapped-over integer value
innobase/include/buf0buf.ic:
Fix a bug: if buffer pool size > 2 GB on a 32-bit computer, we got an assertion failure because >> acted as a division operator (not as a register shift) for a wrapped-over integer value
Crash the server if file flush does not succeed: the database can get corrupt, better to crash it than let it run
innobase/os/os0file.c:
Crash the server if file flush does not succeed: the database can get corrupt, better to crash it than let it run
Slave thread is always in an auto-commit state: remove unnecessary tests when we flush master info
sql/slave.cc:
Slave thread is always in an auto-commit state: remove unnecessary tests when we flush master info
Initing a mutex with MY_MUTEX_INIT_FAST may relieve thread thrashing on Linux
innobase/os/os0sync.c:
Initing a mutex with MY_MUTEX_INIT_FAST may relieve thread thrashing on Linux
Use current_thd to check if a transaction is done by a slave thread
sql/ha_innobase.cc:
Use current_thd to check if a transaction is done by a slave thread
Add syntax SET NO_FOREIGN_KEY_CHECKS=1 and SET RELAXED_UNIQUE_CHECKS=1
sql/lex.h:
Add syntax SET NO_FOREIGN_KEY_CHECKS=1 and SET RELAXED_UNIQUE_CHECKS=1
sql/mysql_priv.h:
Add syntax SET NO_FOREIGN_KEY_CHECKS=1 and SET RELAXED_UNIQUE_CHECKS=1
sql/sql_yacc.yy:
Add syntax SET NO_FOREIGN_KEY_CHECKS=1 and SET RELAXED_UNIQUE_CHECKS=1
Add option innodb_flush_log_at_trx_commit=2 which means we always write the log to file at commit, but only do fsync about once per second
sql/mysqld.cc:
Add option innodb_flush_log_at_trx_commit=2 which means we always write the log to file at commit, but only do fsync about once per second
Add BEGIN andd COMMIT around transactions in the binlog
sql/handler.cc:
Add BEGIN andd COMMIT around transactions in the binlog
sql/log.cc:
Add BEGIN andd COMMIT around transactions in the binlog
Do not flush the position to master.info file if we have a transaction open
sql/slave.cc:
Do not flush the position to master.info file if we have a transaction open
sql/slave.h:
Do not flush the position to master.info file if we have a transaction open
