database/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-09-02 09:41:40 +03:00
Code Activity
63,394 Commits 3,153 Branches 363 Tags
c8310653b4a9a804576fac3afab75448fca1d1b5
Commit Graph

247 Commits

Author SHA1 Message Date
tomas@poseidon.ndb.mysql.com
148faca833 Bug #19395 mysqld does not always detect cluster shutdown 2006-05-19 12:54:12 +02:00
tomas@poseidon.ndb.mysql.com
d0fd5ecde8 Bug #19395 mysqld does not always detect cluster shutdown 
Bug #17610 ndbapi: dropEventOperation leaves object behind, memleak
 2006-05-18 23:38:07 +02:00
tomas@poseidon.ndb.mysql.com
0cb31d7d5f Bug #16875 Using stale MySQLD FRM files can cause restored cluster to fail 2006-05-17 08:34:48 +02:00
tomas@poseidon.ndb.mysql.com
c5987ab67a Bug #16875 Using stale MySQLD FRM files can cause restored cluster to fail 
- adoptions to handle binlog
 2006-05-16 20:56:45 +02:00
tomas@poseidon.ndb.mysql.com
f30014f8a4 ndb: added extra printout on failed "internal" discovery for binlog 
+ removed extra (not needed) discovery done at online create/drop index
 2006-05-10 16:54:29 +02:00
tomas@poseidon.ndb.mysql.com
792f7383ac Bug #19572 Memory leaks in cluster when running make test 2006-05-08 18:09:01 +02:00
tomas@poseidon.ndb.mysql.com
6a48847b1a Bug #19492 --binlog-do-db option cuases tables create issues for ndb master 
- ndb system tables not created because of filter, moved chack of filter
 2006-05-06 01:25:44 +02:00
petr@mysql.com
fec70c97c9 WL#3153 "Split logs". Recommit with post-review fixes 2006-05-05 10:45:58 +04:00
tomas@poseidon.ndb.mysql.com
f6ede396c0 Merge tulin@bk-internal.mysql.com:/home/bk/mysql-5.1-new 
into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb
 2006-05-04 21:55:12 +02:00
tomas@poseidon.ndb.mysql.com
37e8b5ac06 removing the usage if the ndb local dict cache to adress the 241 errors we get now and then 2006-05-04 13:58:17 +02:00
acurtis@xiphis.org
53d4594cfe Merge xiphis.org:/home/antony/work2/wl3201.3 
into  xiphis.org:/home/antony/work2/wl3201.merge
 2006-04-24 13:36:15 -07:00
tomas@poseidon.ndb.mysql.com
7bbf39cd0f ndb: minor modification in replication timer code 
added missing setting of latest applied epoch
 2006-04-21 18:28:00 +02:00
tomas@poseidon.ndb.mysql.com
c73d00dcf9 Bug #19214 running mysqld without binlog causes 10s timeout to drigger on schema ops 
- binlog thread should not wait for apply status share if binlog is not enabled
 2006-04-20 14:44:16 +02:00
tomas@poseidon.ndb.mysql.com
928514cf80 BUG#18094 Slave caches invalid table definition after atlters causes select failure 
- return correct object status from ndb dictionary
- check for validity of index retrieved from index, and retry if invalid
 2006-04-19 14:54:39 +02:00
mskold@mysql.com
a8d4eb8c34 Merge mskold@bk-internal.mysql.com:/home/bk/mysql-5.1-new 
into  mysql.com:/usr/local/home/marty/MySQL/mysql-5.1-new
 2006-04-18 09:00:02 +02:00
mskold@mysql.com
2a924b8c15 Invalidate old table at rename 2006-04-18 08:57:37 +02:00
acurtis@xiphis.org
4e11a4d941 WL#3201 
" Configure support for server plugins "
 2006-04-13 13:49:29 -07:00
tomas@poseidon.ndb.mysql.com
66f745cd01 wrong ndb object used to drop event operation causing DBUG_ASSERT in shutdown/cleanup 2006-04-13 09:37:43 +02:00
tomas@poseidon.ndb.mysql.com
4a5f9b47b9 ndb: 
freeing non freed objects on server shutdown
corrected timeout handling on schema events
 2006-04-12 18:01:19 +02:00
tomas@poseidon.ndb.mysql.com
85ad10d50d Bug #18932: Cluster binlog mysqld accepts updating although binlog not setup 2006-04-10 16:08:40 +02:00
mskold@mysql.com
fae02215ae Merge mskold@bk-internal.mysql.com:/home/bk/mysql-5.1-new 
into  mysql.com:/usr/local/home/marty/MySQL/mysql-5.1-new
 2006-04-06 11:25:29 +02:00
mskold@mysql.com
68d4b5762f Fix for bug#16445 schema version error 241 after mysqld restart, always invalidate dictionary cache when receiving changed schema events drop table or alter table, regardless if done remotely or not (also includes cluster failures, but refreshing cache is a safe operation) 2006-04-06 10:47:48 +02:00
tomas@poseidon.ndb.mysql.com
d0ca8374cd Bug #18596 binlog schema event auto push causes mysqld errors 
- move slock bitmask to separate hash list, object living only during query
 2006-04-03 19:11:20 +02:00
tomas@poseidon.ndb.mysql.com
d0a3ce5da4 - corrected bug causing hang in getTable when using blob tables 
- make sure cluster/schema table is always created first
 2006-03-24 10:12:34 +01:00
tomas@poseidon.ndb.mysql.com
5cc1da5424 Merge tulin@bk-internal.mysql.com:/home/bk/mysql-5.1-new 
into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new
 2006-03-23 22:50:20 +01:00
tomas@poseidon.ndb.mysql.com
57198f85d6 Bug #18472 race condition between multiple mysqld's when setting up cluster/schema 
- check that event is the correct one, and only delete if wrong version
 2006-03-23 22:49:02 +01:00
pekka@mysql.com
a2263a1fbf ndb - bug#17813 schema.query => blob 2006-03-23 04:59:14 +01:00
tomas@poseidon.ndb.mysql.com
bd9f9533fb Bug #18395 dual mysqld's with binlog do not sync drop table binlog event correctly 
- in ndb_binlog_thread_handle_schema_event make sure to postpone "slock achnowledgement" until event has been put into the binlog

+ some cleanup, Cluster_replication_schem -> Cluster_schema, indentation
 2006-03-21 16:54:56 +01:00
tomas@poseidon.ndb.mysql.com
5a4e512942 changed test to make it predictable 2006-03-13 09:55:41 +01:00
tomas@poseidon.ndb.mysql.com
a7e7a1acf4 wl#3023 clean up 
- enabling some new tests
 2006-03-11 15:52:38 +01:00
tomas@poseidon.ndb.mysql.com
e4b7cd8eab Merge tulin@bk-internal.mysql.com:/home/bk/mysql-5.1-new 
into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new
 2006-03-11 07:26:58 +01:00
tomas@poseidon.ndb.mysql.com
485580e436 wl#3023 ndb to return correct tables for initial table maps 
+ removed extra binlog events generated by drop table schema ops to produce predictable test cases
 2006-03-11 06:58:48 +01:00
lars@mysql.com
681c8717ae Merge mysql.com:/users/lthalmann/bkroot/mysql-5.1-new 
into  mysql.com:/users/lthalmann/bk/mysql-5.1-new-wl3023-mats
 2006-03-10 17:31:06 +01:00
tomas@poseidon.ndb.mysql.com
a7f9699d8a added missing dbug_return 2006-03-10 10:41:52 +01:00
lars@mysql.com
6bcac9fcc6 Merge mysql.com:/users/lthalmann/bkroot/mysql-5.1-new 
into  mysql.com:/users/lthalmann/bk/mysql-5.1-new-wl3023-mats
 2006-03-09 16:12:58 +01:00
tomas@poseidon.ndb.mysql.com
280e2bf440 Bug #18106 Ndb: Online add index together with replication may cause mysqld core 2006-03-09 15:50:26 +01:00
tomas@poseidon.ndb.mysql.com
dc08a83735 missing DBUG_RETURN added 2006-03-09 09:30:32 +01:00
tomas@poseidon.ndb.mysql.com
610aa1e07c Bug #17838 binlog not setup on seconday master after rename 
-added setting up of binlogging after receiving rename table
+cleanup
 2006-03-09 01:04:13 +01:00
mats@mysql.com
2b2691e975 WL#3023 (Use locks in a statement-based manner): 
Minor changes to make it work with NDB.
 2006-03-08 14:12:26 +01:00
mats@mysql.com
e0f5d35ceb Merge mysql.com:/home/bkroot/mysql-5.1-new 
into  mysql.com:/home/bk/w3023-mysql-5.1-new
 2006-03-03 09:57:42 +01:00
mats@mysql.com
0ffd1be87d WL#3023 (RBR: Use locks in a statement-like manner): 
More adaptions to make it work with existing code base.
 2006-03-03 09:49:46 +01:00
tomas@poseidon.ndb.mysql.com
500fa8262a Bug #17827 cluster: rename of several tables in one statement, gets multiply logged 
- redo log table query for log, split into separate entries per rename, to avoid duplicates, also to only log renames that relate to ndb tables
 2006-03-01 18:23:00 +01:00
tomas@poseidon.ndb.mysql.com
df6bb1994b Bug #17805 Cluster_replication database should be renamed to just cluster 2006-03-01 13:31:21 +01:00
tomas@poseidon.ndb.mysql.com
4dee17f159 Merge tulin@bk-internal.mysql.com:/home/bk/mysql-5.1-new 
into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new
 2006-02-28 12:40:19 +01:00
tomas@poseidon.ndb.mysql.com
fecfbb4834 Bug#16385, Partitions: crash when updating a range partitioned NDB table 
- too little space was allocated for receiving events, partition uses extra column in table
 2006-02-28 12:28:52 +01:00
mats@mysql.com
1e66bc0d16 Merge mysql.com:/home/bkroot/mysql-5.1-new 
into  mysql.com:/home/bk/w3023-mysql-5.1-new
 2006-02-28 10:06:58 +01:00
mats@mysql.com
f0f8795beb Post-merge fixes. 2006-02-27 17:23:20 +01:00
mats@mysql.com
a865af0d4b Merge mysql.com:/home/bkroot/mysql-5.1-new 
into  mysql.com:/home/bk/fix-mysql-5.1-release
 2006-02-27 09:09:02 +01:00
monty@mysql.com
386276d89d Cleanups 
Don't run upgrade.test with embedded server as it requires mysqlcheck
 2006-02-26 16:03:43 +02:00
guilhem@mysql.com
0071749595 WL#2977 and WL#2712 global and session-level variable to set the binlog format (row/statement), 
and new binlog format called "mixed" (which is statement-based except if only row-based is correct,
in this cset it means if UDF or UUID is used; more cases could be added in later 5.1 release):
SET GLOBAL|SESSION BINLOG_FORMAT=row|statement|mixed|default;
the global default is statement unless cluster is enabled (then it's row) as in 5.1-alpha.
It's not possible to use SET on this variable if a session is currently in row-based mode and has open temporary tables (because CREATE
TEMPORARY TABLE was not binlogged so temp table is not known on slave),  or if NDB is enabled (because
NDB does not support such change on-the-fly, though it will later), of if in a stored function (see below).
The added tests test the possibility or impossibility to SET, their effects, and the mixed mode,
including in prepared statements and in stored procedures and functions.
Caveats:
a) The mixed mode will not work for stored functions: in mixed mode, a stored function will
always be binlogged as one call and in a statement-based way (e.g. INSERT VALUES(myfunc()) or SELECT myfunc()).
b) for the same reason, changing the thread's binlog format inside a stored function is
refused with an error message.
c) the same problems apply to triggers; implementing b) for triggers will be done later (will ask
Dmitri).
Additionally, as the binlog format is now changeable by each user for his session, I remove the implication
which was done at startup, where row-based automatically set log-bin-trust-routine-creators to 1
(not possible anymore as a user can now switch to stmt-based and do nasty things again), and automatically
set --innodb-locks-unsafe-for-binlog to 1 (was anyway theoretically incorrect as it disabled
phantom protection).
Plus fixes for compiler warnings.
 2006-02-25 22:21:03 +01:00