- 14 Jun, 2003 1 commit
-
-
unknown authored
if one is running many mysqlds through mysqld_multi, for example. Without this option, on Linux one mysqld_safe process may kill other mysqlds as well, if started using the same binary and path.
-
- 12 Jun, 2003 8 commits
-
-
unknown authored
into narttu.mysql.fi:/my/mysql-4.0 sql/sql_parse.cc: Auto merged
-
unknown authored
include/my_sys.h: Changed safe_malloc variables to start with sf_ mysys/default.c: Use safemalloc (as we use dynamic_arrays() that uses it inderectly anyway) mysys/my_static.c: Changed safe_malloc variables to start with sf_ mysys/my_static.h: Changed safe_malloc variables to start with sf_ Changed safemalloc structure to not have to be 8 byte aligned mysys/safemalloc.c: Changed safemalloc structure to not have to be 8 byte aligned. (portability fix) BIG code cleanup sql/mysqld.cc: Changed safe_malloc variables to start with sf_ sql/sql_parse.cc: Changed safe_malloc variables to start with sf_
-
unknown authored
-
unknown authored
-
unknown authored
-
unknown authored
mysys/safemalloc.c: Indentation fixes Changes (long*) to (uint32*) to fix a portability problem
-
unknown authored
define a different niceness level in my.cnf (Bug #627) scripts/mysqld_safe.sh: - applied patch from Christian Hammers to be able to define a different niceness level in my.cnf (Bug #627)
-
unknown authored
into mysql.com:/space/my/mysql-4.0-build
-
- 11 Jun, 2003 4 commits
-
-
unknown authored
mysql-test/r/func_time.result: result's checking added mysql-test/t/func_time.test: testcase added
-
unknown authored
Item_extract needs special implementation for eq(). Item_func::eq doesn't work correctly because we have to compare Item_extract::int_type parameters also We need to propagate this to 4.1 sql/item_timefunc.cc: Item_extract::eq implementation added sql/item_timefunc.h: Item_extract::eq definition added BitKeeper/etc/logging_ok: Logging to logging@openlogging.org accepted
-
unknown authored
to accept --socket option (Bug #592) scripts/mysql_explain_log.sh: - applied patch provided by Dennis Haney to accept --socket option (Bug #592)
-
unknown authored
support-files/mysql.spec.sh: - fixed path to init script (/sbin/init.d is obsolete)
-
- 10 Jun, 2003 1 commit
-
-
unknown authored
Added option --gdb Free memory used by replicate_xxx and binglog_xxx options mysql-test/mysql-test-run.sh: Added --gdb when using gdb mysys/thr_alarm.c: Safety check sql/mysql_priv.h: Don't install signal handler for SIGINT by default sql/mysqld.cc: Don't install signal handler for SIGINT by default Added option --gdb Free memory used by replicate_xxx and binglog_xxx options. Add statistics variable for killed threads sql/repl_failsafe.cc: Incremented aborted_connects on failure sql/sql_list.cc: Added free_list() to free memory on shutdown.
-
- 06 Jun, 2003 3 commits
-
-
unknown authored
into mysql.com:/home/mysql_src/mysql-4.0
-
unknown authored
we now make a distinction between if the master is < 3.23.57, 3.23 && >=57, and 4.x (before the 2 3.23 were one). This is because in 3.23.57 we have a way to distinguish between a Start_log_event written at server startup and one written at FLUSH LOGS, so we have a way to know if the slave must drop old temp tables or not. Change: mi->old_format was bool, now it's enum (to handle 3 cases). However, functions which had 'bool old_format' as an argument have their prototypes unchanged, because the old old_format == 0 now corresponds to the enum value BINLOG_FORMAT_CURRENT which is equal to 0, so boolean tests are left untouched. The only case were we use mi->old_format as an enum instead of casting it implicitly to a bool, is in Start_log_event::exec_event, where we want to distinguish between the 3 possible enum values. sql/log_event.cc: Fix for bug 254 : we now make a distinction between if the master is < 3.23.57, 3.23 && >=57, and 4.x (before the 2 3.23 were one), to know if the slave must drop old temp tables or not. sql/slave.cc: Fix for bug 254 : mi->old_format is now enum. An unrelated comment. sql/slave.h: fix for bug 254 : mi->old_format is now enum.
-
unknown authored
Add syntax SAVEPOINT id and ROLLBACK TO SAVEPOINT id. This is compatible with DB2 and Oracle but not with SQL Server. Savepoints do not do anything yet, this is just parsing. sql/lex.h: Add syntax SAVEPOINT id and ROLLBACK TO SAVEPOINT id. This is compatible with DB2 and Oracle but not with SQL Server. Savepoints do not do anything yet, this is just parsing. sql/mysqld.cc: Add syntax SAVEPOINT id and ROLLBACK TO SAVEPOINT id. This is compatible with DB2 and Oracle but not with SQL Server. Savepoints do not do anything yet, this is just parsing. sql/sql_lex.h: Add syntax SAVEPOINT id and ROLLBACK TO SAVEPOINT id. This is compatible with DB2 and Oracle but not with SQL Server. Savepoints do not do anything yet, this is just parsing. sql/sql_parse.cc: Add syntax SAVEPOINT id and ROLLBACK TO SAVEPOINT id. This is compatible with DB2 and Oracle but not with SQL Server. Savepoints do not do anything yet, this is just parsing. sql/sql_yacc.yy: Add syntax SAVEPOINT id and ROLLBACK TO SAVEPOINT id. This is compatible with DB2 and Oracle but not with SQL Server. Savepoints do not do anything yet, this is just parsing.
-
- 05 Jun, 2003 14 commits
-
-
unknown authored
sql/slave.cc: Comment to remember that size of relay logs on disk is not the total size of the relay log.
-
unknown authored
-
unknown authored
into ua126d19.elisa.omakaista.fi:/home/my/bk/mysql-4.0
-
unknown authored
if 'user_name' is the current user and it is not root.
-
unknown authored
Revert a change to dict_mem_index_add_field which slipped prematurely into the bk tree sql/ha_innodb.cc: Revert a change to dict_mem_index_add_field which slipped prematurely into the bk tree
-
unknown authored
Fix the BDB crash in the previous push; to save CPU remove duplicate calls of commit in InnoDB sql/handler.cc: Fix the BDB crash in the previous push; to save CPU remove duplicate calls of commit in InnoDB sql/ha_innodb.cc: Fix the BDB crash in the previous push; to save CPU remove duplicate calls of commit in InnoDB
-
unknown authored
-
unknown authored
-
unknown authored
into ua126d19.elisa.omakaista.fi:/home/my/bk/mysql-4.0
-
unknown authored
in case of an empty string. Bug ID 586.
-
unknown authored
More debugging variables Increment aborted_threads in case of killed or too big packet include/thr_alarm.h: made prototype more portable mysys/thr_alarm.c: Print error if we can't delete an alarm sql/mysqld.cc: Statistics variable (for debugging) sql/net_serv.cc: statistics variable (for debugging) sql/sql_parse.cc: Increment aborted_threads in case of killed or too big packet
-
unknown authored
into narttu.mysql.fi:/my/mysql-4.0
-
unknown authored
-
unknown authored
-
- 04 Jun, 2003 7 commits
-
-
unknown authored
into mysql.com:/space/my/mysql-4.0
-
unknown authored
to set CXX=gcc (cannot link the code with g++) - this should help to recompile the RPM on Distributions using gcc 3 - Added a symlink /usr/sbin/rcmysql -> /etc/init.d/mysql
-
unknown authored
into narttu.mysql.fi:/my/mysql-4.0
-
unknown authored
Red Hat's chkconfig (Bug #272) (The LSB spec is a bit ambigous about what actually needs to be put into this field)
-
unknown authored
-
unknown authored
If the autocommit is on, let handler.cc commit or rollback the whole transaction at an updating SQL statement end. This probably fixes bug number 578. The problem was that when explicit LOCK TABLES is used, then the lock count method in autocommit does not work. sql/handler.cc: If the autocommit is on, let handler.cc commit or rollback the whole transaction at an updating SQL statement end. This probably fixes bug number 578. The problem was that when explicit LOCK TABLES is used, then the lock count method in autocommit does not work.
-
unknown authored
Portability fix for Windows 64 include/config-win.h: Portability fix for Windows 64 include/my_global.h: Portability fix for Windows 64 include/mysql_version.h.in: Added [mysqld-base-version] as a default group for the mysqld server innobase/include/univ.i: Portability fix for Windows 64 sql/mysqld.cc: Added [mysqld-base-version] as a default group for the mysqld server
-
- 03 Jun, 2003 2 commits
-
-
unknown authored
into mysql.com:/home/mysql_src/mysql-4.0
-
unknown authored
Plus a changeset which I had committed but forgot to push (and this changeset is lost on another computer, so I recreate it here). This changeset is "user-friendly SHOW BINLOG EVENTS and CHANGE MASTER TO when log positions < 4 are used. sql/slave.cc: fix for bug 576 (DBUG_ASSERT failure when using CHANGE MASTER TO RELAY_LOG_POS=4). sql/sql_repl.cc: User-friendly SHOW BINLOG EVENTS: SHOW BINLOG EVENTS FROM 0: currently one gets MASTER> show binlog events from 0; ERROR 1220: Error when executing command SHOW BINLOG EVENTS: Invalid log position so we silently convert <4 to 4. sql/sql_yacc.yy: User-friendly CHANGE MASTER TO: presently when one does CHANGE MASTER TO MASTER_LOG_POS=0 he gets 030425 10:12:41 Slave I/O thread: connected to master 'root@localhost:3306', r eplication started in log 'gbichot-bin.013' at position 151 030425 10:12:41 Error reading packet from server: Client requested master to st art replication from impossible position (server_errno=1236) 030425 10:12:41 Got fatal error 1236: 'Client requested master to start replica tion from impossible position' from master when reading data from binary log 030425 10:12:41 Slave I/O thread exiting, read up to log 'gbichot-bin.013', pos ition 151 while she/he probably just wanted to start at the beginning of the binlog, which is 4. So we silently convert <4 to 4 in sql_yacc.yy (i.e. in the slave code; fortunately all versions have the same BIN_LOG_HEADER_SIZE=4 and we should not change this). See comments for an explaination of why we have to do this in sql_yacc.yy, not in sql_repl.cc. Same thing for CHANGE MASTER TO RELAY_LOG_POS. sql/unireg.h: warning comment
-