mariadb

Tree: bc03c9ef19

Author	SHA1	Message	Date
Martin Skold	9e5b67c525	bug #31231 mysql_alter_table() tries to drop a non-existing table bug#31233 mysql_alter_table() fails to drop UNIQUE KEY	17 years ago
gkodinov/kgeorge@macbook.gmz	7cb4b7c19d	fixed warnings and compile errors from the fix for bug 26243	18 years ago
anozdrin/alik@quad.	340906f46d	Fix for Bug#30217: Views: changes in metadata behaviour between 5.0 and 5.1. The problem was that in the patch for Bug#11986 it was decided to store original query in UTF8 encoding for the INFORMATION_SCHEMA. This approach however turned out to be quite difficult to implement properly. The main problem is to preserve the same IS-output after dump/restore. So, the fix is to rollback to the previous functionality, but also to fix it to support multi-character-set-queries properly. The idea is to generate INFORMATION_SCHEMA-query from the item-tree after parsing view declaration. The IS-query should: - be completely in UTF8; - not contain character set introducers. For more information, see WL4052.	18 years ago
tomas@poseidon.ndb.mysql.com	04c26018a7	Bug #34275 mysqld leak if doing multiple statements within same transaction (or wo/ trans) - in autocommit do not allocate statistics share, but instead use one directly on the handler	18 years ago
mskold/marty@mysql.com/quadfish.(none)	35d3bef712	Ndb.hpp, Ndb.cpp, ha_ndbcluster.cc: Add a check if setting an auto_increment field will change it's next value before retrieving tuple_id_range lock. This avoids hitting locks when updating auto_increment values to a lower value than the current maximum. This is useful in loading a table with auto_increment where one loads the highest numbered pk's first and then proceeds backwards to the first. This can then be achieved with the same performance as a normal insert without auto_increment. ndb_restore.result: Updated result file	18 years ago
msvensson@pilot.mysql.com	1fa7072bfa	Bug#33763 Mysqld leaves readonly mode for cluster tables too early - part2 - Open tables readonly while not properly initialized - Close cached tables when coming out of readonly mode - Apply basically same patch as for 32275	18 years ago
davi@mysql.com/endora.local	137e90ed55	Bug#32395 Alter table under a impending global read lock causes a server crash The problem is that some DDL statements (ALTER TABLE, CREATE TRIGGER, FLUSH TABLES, ...) when under LOCK TABLES need to momentarily drop the lock, reopen the table and grab the write lock again (using reopen_tables). When grabbing the lock again, reopen_tables doesn't pass a flag to mysql_lock_tables in order to ignore the impending global read lock, which causes a assertion because LOCK_open is being hold. Also dropping the lock must not signal to any threads that the table has been relinquished (related to the locking/flushing protocol). The solution is to correct the way the table is reopenned and the locks grabbed. When reopening the table and under LOCK TABLES, the table version should be set to 0 so other threads have to wait for the table. When grabbing the lock, any other flush should be ignored because it's theoretically a atomic operation. The chosen solution also fixes a potential discrepancy between binlog and GRL (global read lock) because table placeholders were being ignored, now a FLUSH TABLES WITH READ LOCK will properly for table with open placeholders. It's also important to mention that this patch doesn't fix a potential deadlock if one uses two GRLs under LOCK TABLES concurrently.	18 years ago
mskold/marty@mysql.com/quadfish.(none)	0c62882776	Removed illegal cast	18 years ago
mskold/marty@mysql.com/quadfish.(none)	4619caa5d5	Removed illegal cast	18 years ago
mskold/marty@mysql.com/quadfish.(none)	6047fb2e44	Removed illegal cast	18 years ago
mskold/marty@mysql.com/quadfish.(none)	af908e61b7	bug#21072 Duplicate key error in NDB references wrong key: Post-merge fixes	18 years ago
mskold/marty@mysql.com/quadfish.(none)	fc6f839b03	bug#21072 Duplicate key error in NDB references wrong key: Post-review fixes	18 years ago
mskold/marty@mysql.com/quadfish.(none)	27c025061d	bug#21072 Duplicate key error in NDB references wrong key: Return correct key for non-batching inserts	18 years ago
mkindahl@dl145h.mysql.com	23cd47e0e1	Reverting changes to debug printouts to ha_ndbcluster.cc.	18 years ago
istruewing@stella.local	10df30f091	Bug#31210 - INSERT DELAYED crashes server when used on partitioned table Post-merge fix A new need for lex initialization arose.	18 years ago
mskold/marty@mysql.com/quadfish.(none)	56ab11c8cb	ndb_auto_increment.result: Rename: mysql-test/r/ndb_auto_increment.result -> mysql-test/suite/ndb/r/ndb_auto_increment.result ndb_auto_increment.test, ndb_auto_increment.result: Bug #31956 auto increment bugs in MySQL Cluster: Adapted test cases ha_ndbcluster.cc: Bug #31956 auto increment bugs in MySQL Cluster: Merging from 5.0 ndb_auto_increment.test: Rename: mysql-test/t/ndb_auto_increment.test -> mysql-test/suite/ndb/t/ndb_auto_increment.test	18 years ago
mskold/marty@mysql.com/quadfish.(none)	022b835c67	Removed compiler warnings	18 years ago
mskold/marty@mysql.com/quadfish.(none)	4cf742a8a8	ha_ndbcluster.h: Bug #31956 auto increment bugs in MySQL Cluster: Added utility method and constant for internal prefetch default ndb_auto_increment.result: BitKeeper file /home/marty/MySQL/mysql-5.0-ndb/mysql-test/r/ndb_auto_increment.result mysqld.cc: Bug #25176 Trying to set ndb_autoincrement_prefetch_sz always fails: Changed pointer to max value Bug #31956 auto increment bugs in MySQL Cluster: Changed meaning of ndb_autoincrement_prefetch_sz to specify prefetch between statements, changed default to 1 (with internal prefetch to at least 32 inside a statement) ndb_insert.test, ndb_insert.result: Moved auto_increment tests to ndb_auto_increment.test ndb_auto_increment.test: BitKeeper file /home/marty/MySQL/mysql-5.0-ndb/mysql-test/t/ndb_auto_increment.test ha_ndbcluster.cc: Bug #31956 auto increment bugs in MySQL Cluster: Changed meaning of ndb_autoincrement_prefetch_sz to specify prefetch between statements, changed default to 1 (with internal prefetch to at least 32 inside a statement), added handling of updates of pk/unique key with auto_increment Bug #32055 Cluster does not handle auto inc correctly with insert ignore statement	18 years ago
tomas@whalegate.ndb.mysql.com	9320ec8d16	Bug #31484 Cluster LOST_EVENTS entry not added to binlog on mysqld restart.	18 years ago
knielsen@loke.(none)[knielsen]	e16f03cd64	BUG#31810: Potential infinite loop with autoincrement failures in ndb Fix extra semicolon causing if-statement to be disabled.	18 years ago
mats@kindahl-laptop.dnsalias.net	56ae0be77d	Eliminating some valgrind warnings resulting from that some storage engines do not set the unused null bits (i.e., the filler bits and the X bit) correctly. Also adding some casts to debug printouts to eliminate compiler warnings.	18 years ago
cmiller@zippy.cornsilk.net	91b5c11922	Doxygenization of comments.	18 years ago
mskold/marty@mysql.com/linux.site	c91d8068d1	Bug#25817 UPDATE IGNORE doesn't check write_set when checking unique indexes: Post merge 5.0->5.1	18 years ago
mskold/marty@mysql.com/linux.site	94e7bf9f4b	Removed tabs	18 years ago
mskold/marty@mysql.com/linux.site	403f0afc29	Bug#25817 UPDATE IGNORE doesn't check write_set when checking unique indexes: Added checks	18 years ago
gni@dev3-221.dev.cn.tlan	44472d4233	BUG#29851 TRUNCATE causes error 4350 from cluster in INSERT... ON DUPLICATE KEY UPDATE	18 years ago
mikael@dator6.(none)	f09169670b	Fixed ndbcluster_rollback	18 years ago
mikael@dator6.(none)	0f18ff3350	BUG#30996: Committed too early when autocommit and lock table Moved out a lot of code into functions from external_lock and start_stmt Fixed a crashing bug at memory alloc failure Merged the stmt and all variables into one trans variable Always register start of statement as according to the interface of the handlers. Also register for start of transaction when not statement commit == not autocommit AND no begin - commit ongoing Now that we registered in a proper manner we also needed to handle the commit call when end of statement and transaction is ongoing Added start_stmt_count to know when we have start of statement for first table	18 years ago
tomas@whalegate.ndb.mysql.com	b5e7c8dbd3	change printout to be a warning	18 years ago
tomas@whalegate.ndb.mysql.com	08b8d6aeaf	Bug#20872 master*.err: miscellaneous error messages	18 years ago
tomas@whalegate.ndb.mysql.com	a7921ab61d	Bug#20872 master*.err: miscellaneous error messages	18 years ago
tomas@whalegate.ndb.mysql.com	803228a1a8	Bug #30667 ndb table discovery does not work correcly with information schema - the listed file_names are not necessarily on disk, so we need to discover them if they aren't	19 years ago
tomas@whalegate.ndb.mysql.com	8fb593b840	BUG#30017 log-slave-updates incorrect behavior for cluster - let the receiving injector thread decide what to do (recommit for 5.1.22 target)	19 years ago
mats@kindahl-laptop.dnsalias.net	1fc1bd7f53	Renaming MASTER_INFO to Master_info in order to follow the coding standards (and help Doxygen generating good documentation).	19 years ago
mskold/marty@mysql.com/linux.site	8dd40ef670	bug#30337 DELETE ... WHERE PK IN (..) and AFTER DELETE trigger crashes API node: Disable multi_read_range if there are after delete/update triggers	19 years ago
jonas@perch.ndb.mysql.com	e01f587dd4	ndb - bug#28804 Handle out of transaction buffer in TC for INDX lookups	19 years ago
gni@dev3-221.dev.cn.tlan	5096a9d274	fix merge bug	19 years ago
gluh@mysql.com/eagle.(none)	27ab885525	WL#3732 Information schema optimization	19 years ago
gkodinov/kgeorge@magare.gmz	9a0e6ec6d2	(pushing for Andrei) Bug #27417 thd->no_trans_update.stmt lost value inside of SF-exec-stack Once had been set the flag might later got reset inside of a stored routine execution stack. The reason was in that there was no check if a new statement started at time of resetting. The artifact affects most of binlogable DML queries. Notice, that multi-update is wrapped up within bug@27716 fix, multi-delete bug@29136. Fixed with saving parent's statement flag of whether the statement modified non-transactional table, and unioning (merging) the value with that was gained in mysql_execute_command. Resettling thd->no_trans_update members into thd->transaction.`member`; Asserting code; Effectively the following properties are held. 1. At the end of a substatement thd->transaction.stmt.modified_non_trans_table reflects the fact if such a table got modified by the substatement. That also respects THD::really_abort_on_warnin() requirements. 2. Eventually thd->transaction.stmt.modified_non_trans_table will be computed as the union of the values of all invoked sub-statements. That fixes this bug#27417; Computing of thd->transaction.all.modified_non_trans_table is refined to base to the stmt's value for all the case including insert .. select statement which before the patch had an extra issue bug@28960. Minor issues are covered with mysql_load, mysql_delete, and binloggin of insert in to temp_table select. The supplied test verifies limitely, mostly asserts. The ultimate testing is defered for bug@13270, bug@23333.	19 years ago
stewart@flamingspork.com[stewart]	f9d977f980	[PATCH] Bug#26793 I_S query crashes in NDB If ::exteral_lock hadn't been called, we'd have no NDB object, so need to check/get one here. It looks like sql_show.cc is the only place that does this.... or at least the other places will be well hidden. Index: ndb-work/sql/ha_ndbcluster.cc ===================================================================	19 years ago
svoj@mysql.com/april.(none)	3b18aae71c	BUG#29806 - binlog_innodb.test creates a server log Stopping mysql server could result in an entry in mysql error file: "InnoDB: Error: MySQL is freeing a thd". This happened because InnoDB assumes that the server will never call external_lock(F_UNLCK) in case external_lock(READ/WRITE) failed. Prior to this patch we haven't had strict definition whether external_lock(F_UNLCK) must be called in case external_lock(READ/WRITE) fails. This patch states that we never call external_lock(F_UNLCK) in case external_lock(READ/WRITE) fails.	19 years ago
tomas@whalegate.ndb.mysql.com	81bc79a711	BUG#30017 log-slave-updates incorrect behavior for cluster - let the receiving injector thread decide what to do	19 years ago
gni@dev3-221.dev.cn.tlan	ad6defd4ba	BUG#28423 cluster to storage engine error code mapping problem	19 years ago
kostja@bodhi.(none)	f5267530d9	A follow up after the patch for Bug#21074 - even though we now have exclusive name lock on the table name in mysql_rm_table_part2, we still should keep LOCK_open - some storage engines are not ready for locking scope change and assume that LOCK_open is kept. Still, the binary logging and query cache invalidation calls moved out of LOCK_open scope. Fixes some of the broken 5.1-runtime tests (tests break on asserts).	19 years ago
jonas@perch.ndb.mysql.com	d46ff21f4f	ndb - bug#28720 fix also undo files	19 years ago
jonas@perch.ndb.mysql.com	381b11cefe	ndb - bug#28720 - "Disk data meta information is not visible in mysqld but exists in ndbd" continue on unknown result (no contact)	19 years ago
thek@adventure.(none)	863e882785	Bug#21074 Large query_cache freezes mysql server sporadically under heavy load Invaldating a subset of a sufficiently large query cache can take a long time. During this time the server is efficiently frozen and no other operation can be executed. This patch addresses this problem by moving the locks which cause the freezing and also by temporarily disable the query cache while the invalidation takes place.	19 years ago
stewart@flamingspork.com[stewart]	77e9eb56fc	[PATCH] BUG#27404 util thd mysql_parse sig11 when mysqld default multibyte charset NDB util thread calls mysql_parse internally with plain old c strings (7bit ascii) to create tables (e.g. mysql.ndb_schema). With mysqld default charset set to a multibyte one (e.g. ucs2) mysql_parse would try to interpret the 7bit string as UCS2 and promptly explode in a heap. Solution is to set the util thread to be using utf8 charset. Index: ndb-work/sql/ha_ndbcluster.cc ===================================================================	19 years ago
tomas@poseidon.mysql.com	efbe23a486	Bug #29222 Statement mode replicates both statement and rows when writing to an NDB table - only log statements locally (changes will not be logged on other servers)	19 years ago
tomas@whalegate.ndb.mysql.com	955c40dece	WL#3303 - get the ndb flags right, so that the behaviour is as before	19 years ago

1 2 3 4 5 ...

1399 Commits (bc03c9ef19c567fa26ecb2a2e35c3b49b241b101)