mariadb

Tree: 062f57e279

Author	SHA1	Message	Date
Alexander Nozdrin	759d5bc535	Another incarnation of the patch for Bug#30708 (make relies GNU extentions). The patch was partially backport from 6.0. Original comment: bug#30708: make relies GNU extensions. Now that we no longer use BitKeeper we can safely remove the SCCS handling with no loss of functionality.	16 years ago
Marko Makela	c144a091db	recv_sys_init(), recv_sys_empty_hash(): Shrink recv_sys->addr_hash. This addresses Bug #53122 in the built-in InnoDB.	16 years ago
Marko Makela	0ca989eaaf	Reduce the next-key locking of READ UNCOMMITTED to match that of READ COMMITTED in the built-in InnoDB. (Bug #48607)	16 years ago
Marko Makela	91702fd313	Merge r6103 from InnoDB Plugin to the built-in InnoDB to fix Bug #53202 : ------------------------------------------------------------------------ r6103 \| marko \| 2009-10-26 15:46:18 +0200 (Mon, 26 Oct 2009) \| 4 lines Changed paths: M /branches/zip/row/row0ins.c branches/zip: row_ins_alloc_sys_fields(): Zero out the system columns DB_TRX_ID, DB_ROLL_PTR and DB_ROW_ID, in order to avoid harmless Valgrind warnings about uninitialized data. (The warnings were harmless, because the fields would be initialized at a later stage.) ------------------------------------------------------------------------	16 years ago
Vasil Dimov	a1bdbe8a0c	Do not define UNIV_DEBUG_VALGRIND when HAVE_purify because this results in some valgrind errors. Bug#53202 valgrind: uninitialized bytes in dtuple_print() has been opened to track this.	16 years ago
Marko Mäkelä	4d646bd16e	lock_rec_queue_validate(): Disable a bogus check that a transaction that holds a lock on a clustered index record also holds a lock on the secondary index record.	16 years ago
Marko Mäkelä	063928ba05	row_search_for_mysql(): Never try semi-consistent read in unique searches. They are only useful in table scans. (Bug #52663)	16 years ago
Mats Kindahl	c0817bacaf	WL#5030: Splitting mysql_priv.h Removing traces of mysql_priv.h from comments and other non-source files that were missed before.	16 years ago
Marko =?ISO-8859-1?Q?M=E4kel=E4?=	ca85feba83	Enable UNIV_DEBUG_VALGRIND when HAVE_purify is set.	16 years ago
Mats Kindahl	23d8586dbf	WL#5030: Split and remove mysql_priv.h This patch: - Moves all definitions from the mysql_priv.h file into header files for the component where the variable is defined - Creates header files if the component lacks one - Eliminates all include directives from mysql_priv.h - Eliminates all circular include cycles - Rename time.cc to sql_time.cc - Rename mysql_priv.h to sql_priv.h	16 years ago
Vasil Dimov	292add1cf8	Rename the newly added mysql-tests from InnoDB to their proper location.	16 years ago
Vasil Dimov	3f78f016e7	Move ./storage/innobase/mysql-test/* into ./mysql-test/* except innodb., innodb_bug34300 and innodb_bug39438* in order to preserve their history from SVN.	16 years ago
MySQL Build Team	edbb0ba6c2	Backport of "Bug #50409 Solaris 8 compatibility broken by assumption about printstack() being present"	16 years ago
Sergey Vojtovich	ad849f010f	Applying InnoDB snapshot Detailed revision comments: r6822 \| vasil \| 2010-03-15 10:17:31 +0200 (Mon, 15 Mar 2010) \| 12 lines branches/5.1: Typecast to silence a compiler warning: row/row0sel.c: 4548 C4244: '=' : conversion from 'float' to 'ib_ulonglong', possible loss of data row/row0sel.c: 4553 C4244: '=' : conversion from 'double' to 'ib_ulonglong', possible loss of data Reported by: Jonas Oreland <Jonas.Oreland@Sun.COM> Discussed with: Sunny Bains <sunny.bains@oracle.com>	16 years ago
Sergey Vojtovich	b0bf53aa65	Applying InnoDB snapshot, fixes BUG#47621. Detailed revision comments: r6783 \| jyang \| 2010-03-09 17:54:14 +0200 (Tue, 09 Mar 2010) \| 9 lines branches/5.1: Fix bug #47621 "MySQL and InnoDB data dictionaries will become out of sync when renaming columns". MySQL does not provide new column name information to storage engine to update the system table. To avoid column name mismatch, we shall just request a table copy for now. rb://246 approved by Marko.	16 years ago
Sergey Vojtovich	59583948c1	Applying InnoDB snapshot Detailed revision comments: r6780 \| vasil \| 2010-03-08 19:13:20 +0200 (Mon, 08 Mar 2010) \| 4 lines branches/5.1: Whitespace fixup.	16 years ago
Sergey Vojtovich	eb60a27a2a	Applying InnoDB snapshot, fixes BUG#51653 Detailed revision comments: r6774 \| calvin \| 2010-03-03 23:56:10 +0200 (Wed, 03 Mar 2010) \| 2 lines branches/5.1: fix bug#51653: outdated reference to set-variable Non functional change.	16 years ago
MySQL Build Team	6424a3463e	Backport into build-201003230706-5.1.43sp1 > ------------------------------------------------------------ > revno: 3329.2.3 > revision-id: svoj@sun.com-20100122095702-e18xzhmyll1e5s25 > parent: svoj@sun.com-20100122095632-j8ssd5csnlzp1zpf > committer: Sergey Vojtovich <svoj@sun.com> > branch nick: mysql-5.1-bugteam > timestamp: Fri 2010-01-22 13:57:02 +0400 > message: > Applying InnoDB snapshot, fixes BUG#46193. > > Detailed revision comments: > > r6424 \| marko \| 2010-01-12 12:22:19 +0200 (Tue, 12 Jan 2010) \| 16 lines > branches/5.1: In innobase_initialize_autoinc(), do not attempt to read > the maximum auto-increment value from the table if > innodb_force_recovery is set to at least 4, so that writes are > disabled. (Bug #46193) > > innobase_get_int_col_max_value(): Move the function definition before > ha_innobase::innobase_initialize_autoinc(), because that function now > calls this function. > > ha_innobase::innobase_initialize_autoinc(): Change the return type to > void. Do not attempt to read the maximum auto-increment value from > the table if innodb_force_recovery is set to at least 4. Issue > ER_AUTOINC_READ_FAILED to the client when the auto-increment value > cannot be read. > > rb://144 by Sunny, revised by Marko	16 years ago
Joerg Bruehe	b61fe56bd7	Fixes related to bug#46587: archive storage engine headers don't include my_global.h first During the build of 5.5.3-m3 on older Linux platforms (kernels 2.4 or early 2.6), the symptom described in the bug report occurred both in the "archive" and in the "innobase" storage engine. This change is the patch proposed in that bug report, and a similar one in innobase, that latter is aligned with Vasil Dimov of Innobase, the original author.	16 years ago
Vladislav Vaintroub	fa083b75c3	Fix cmake build on OSX/i386 (many innodb tests fail in optimized build) Unlike in autotools build, innodb was compiled with -DUNIV_MUST_NOT_INLINE set. this exposed what seems to be a bug in gcc backend. The fix is to remove extra definition.	16 years ago
Vladislav Vaintroub	402cab754a	Fix typo (CMAKE_SIZEOF_VOIDP=>CMAKE_SIZEOF_VOID_P)	16 years ago
Sergey Vojtovich	b751f4e03b	Applying InnoDB snapshot, fixes BUG#50691 Detailed revision comments: r6669 \| jyang \| 2010-02-11 12:24:19 +0200 (Thu, 11 Feb 2010) \| 7 lines branches/5.1: Fix bug #50691, AIX implementation of readdir_r causes InnoDB errors. readdir_r() returns an non-NULL value in the case of reaching the end of a directory. It should not be treated as an error return. rb://238 approved by Marko	16 years ago
Sergey Vojtovich	70564eb62d	Applying InnoDB snapshot, fixes BUG#38901 Detailed revision comments: r6613 \| inaam \| 2010-02-09 20:23:09 +0200 (Tue, 09 Feb 2010) \| 11 lines branches/5.1: Fix Bug #38901 InnoDB logs error repeatedly when trying to load page into buffer pool In buf_page_get_gen() if we are unable to read a page (because of corruption or some other reason) we keep on retrying. This fills up error log with millions of entries in no time and we'd eventually run out of disk space. This patch limits the number of attempts that we make (currently set to 100) and after that we abort with a message. rb://241 Approved by: Heikki	16 years ago
Sergey Vojtovich	7ca225167b	Applying InnoDB snapshot, fixes BUG#49001 Detailed revision comments: r6545 \| jyang \| 2010-02-03 03:57:32 +0200 (Wed, 03 Feb 2010) \| 8 lines branches/5.1: Fix bug #49001, "SHOW INNODB STATUS deadlock info incorrect when deadlock detection aborts". Print the correct lock owner when recursive function lock_deadlock_recursive() exceeds its maximum depth LOCK_MAX_DEPTH_IN_DEADLOCK_CHECK. rb://217, approved by Marko.	16 years ago
Sergey Vojtovich	57c328ba65	Applying InnoDB snapshot Detailed revision comments: r6538 \| sunny \| 2010-01-30 00:43:06 +0200 (Sat, 30 Jan 2010) \| 6 lines branches/5.1: Check first_value every time against the column max value and set first_value to next autoinc if it's > col max value. ie. not rely on what is passed in from MySQL. [49497] Error 1467 (ER_AUTOINC_READ_FAILED) on inserting a negative value rb://236	16 years ago
Sergey Vojtovich	7633ece07d	Applying InnoDB snapshot Detailed revision comments: r6537 \| sunny \| 2010-01-30 00:35:00 +0200 (Sat, 30 Jan 2010) \| 2 lines branches/5.1: Undo r6536.	16 years ago
Sergey Vojtovich	f1c641d1b6	Applying InnoDB snapshot Detailed revision comments: r6536 \| sunny \| 2010-01-30 00:13:42 +0200 (Sat, 30 Jan 2010) \| 6 lines branches/5.1: Check first_value everytime against the column max value and set first_value to next autoinc if it's > col max value. ie. not rely on what is passed in from MySQL. [49497] Error 1467 (ER_AUTOINC_READ_FAILED) on inserting a negative value rb://236	16 years ago
Sergey Vojtovich	ed057d2806	Applying InnoDB snapshot Detailed revision comments: r6535 \| sunny \| 2010-01-30 00:08:40 +0200 (Sat, 30 Jan 2010) \| 11 lines branches/5.1: Undo the change from r6424. We need to return DB_SUCCESS even if we were unable to initialize the tabe autoinc value. This is required for the open to succeed. The only condition we currently treat as a hard error is if the autoinc field instance passed in by MySQL is NULL. Previously if the table autoinc value was 0 and the next value was requested we had an assertion that would fail. Change that assertion and treat a value of 0 to mean that the autoinc system is unavailable. Generation of next value will now return failure. rb://237	16 years ago
Vladislav Vaintroub	0faa8ef87a	Fix typo HAVE_IBGCC_ATOMIC_BUILTINS=>HAVE_IB_GCC_ATOMIC_BUILTINS. Due to the typo, detection of atomics was broken. It also lead to valgrind error during shutdown (access to freed memory),which is likely present in all builds where atomics are not used.	16 years ago
Vladislav Vaintroub	da91b8d73e	Cleanup casing in MYSQL_ADD_PLUGIN, patch provided by Kent	16 years ago
Sergey Vojtovich	12665e79e4	Applying InnoDB snapshot, fixes BUG#46193. Detailed revision comments: r6424 \| marko \| 2010-01-12 12:22:19 +0200 (Tue, 12 Jan 2010) \| 16 lines branches/5.1: In innobase_initialize_autoinc(), do not attempt to read the maximum auto-increment value from the table if innodb_force_recovery is set to at least 4, so that writes are disabled. (Bug #46193) innobase_get_int_col_max_value(): Move the function definition before ha_innobase::innobase_initialize_autoinc(), because that function now calls this function. ha_innobase::innobase_initialize_autoinc(): Change the return type to void. Do not attempt to read the maximum auto-increment value from the table if innodb_force_recovery is set to at least 4. Issue ER_AUTOINC_READ_FAILED to the client when the auto-increment value cannot be read. rb://144 by Sunny, revised by Marko	16 years ago
Sergey Vojtovich	9aaa3cc4df	Applying InnoDB snapshot Detailed revision comments: r6422 \| marko \| 2010-01-12 11:34:27 +0200 (Tue, 12 Jan 2010) \| 3 lines branches/5.1: Non-functional change: Make innobase_get_int_col_max_value() a static function. It does not access any fields of class ha_innobase.	16 years ago
Sergey Vojtovich	f65b3f7889	Applying InnoDB snapshot, fixes BUG#49238. Detailed revision comments: r6421 \| jyang \| 2010-01-12 07:59:16 +0200 (Tue, 12 Jan 2010) \| 8 lines branches/5.1: Fix bug #49238: Creating/Dropping a temporary table while at 1023 transactions will cause assert. Handle possible DB_TOO_MANY_CONCURRENT_TRXS when deleting metadata in row_drop_table_for_mysql(). rb://220, approved by Marko	16 years ago
Vladislav Vaintroub	a71e4cf18e	- another take on BUILD_CONFIG variable - use OPTION instead of SET for boolean variables to ensure option is in cache. Also use documented CMAKE_USE_MAKE_RULES_OVERRIDE feature instead of INCLUDE. - remove superfluous tests in innobase's CMakeLists.txt	16 years ago
Vladislav Vaintroub	6d59902ccf	Do not run GCC atomic builtins tests on MSVC	16 years ago
Vladislav Vaintroub	10a7c78ed4	just in case old linux is used, add _GNU_SOURCE preprocessor constant to be able to see pthread_rwlock_t	16 years ago
Vladislav Vaintroub	e0b7046b4f	storage/innobase/CMakeLists.txt:	16 years ago
Joerg Bruehe	f62540ee25	Backport a fix from "trunk" into 5.5.1 which came after cloning only. Original comment: revno: 2930 \| revision-id: alik@sun.com-20091223120351-m6l2t721tvtsiumu \| parent: alik@sun.com-20091223104155-cq3uw9l2yvg6jmgc \| committer: Alexander Nozdrin <alik@sun.com> \| branch nick: mysql-trunk-bugfixing \| timestamp: Wed 2009-12-23 15:03:51 +0300 \| message: \| Backporting fix for Bug#49834 from mysql-next-mr-bugfixing \| into mysql-trunk-bugfixing. \| \| Original revision: \| ------------------------------------------------------------ \| revision-id: vvaintroub@mysql.com-20091222115311-bam0xorumd8gvjyo \| parent: mattias.jonsson@sun.com-20091221104426-x2e6c93x8iik4fo0 \| committer: Vladislav Vaintroub <vvaintroub@mysql.com> \| branch nick: mysql-next-mr-bugfixing \| timestamp: Tue 2009-12-22 12:53:11 +0100 \| message: \| Bug#49834 - fixed a bug introduced by mismerge. \| restore original innobase version	16 years ago
Alexander Nozdrin	ba60b39ca3	Backporting fix for Bug#49834 from mysql-next-mr-bugfixing into mysql-trunk-bugfixing. Original revision: ------------------------------------------------------------ revision-id: vvaintroub@mysql.com-20091222115311-bam0xorumd8gvjyo parent: mattias.jonsson@sun.com-20091221104426-x2e6c93x8iik4fo0 committer: Vladislav Vaintroub <vvaintroub@mysql.com> branch nick: mysql-next-mr-bugfixing timestamp: Tue 2009-12-22 12:53:11 +0100 message: Bug#49834 - fixed a bug introduced by mismerge. restore original innobase version ------------------------------------------------------------	16 years ago
Satya B	83d5ca950b	Applying InnoDB snapshot 5.1-ss6344, Fixes BUG#47814 and also applying 5.1-ss6355 Detailed revision comments: r6324 \| jyang \| 2009-12-17 06:54:24 +0200 (Thu, 17 Dec 2009) \| 8 lines branches/5.1: Fix bug #47814 - Diagnostics are frequently not printed after a long lock wait in InnoDB. Separate out the lock wait timeout check thread from monitor information printing thread. rb://200 Approved by Marko. r6349 \| marko \| 2009-12-22 11:09:54 +0200 (Tue, 22 Dec 2009) \| 3 lines branches/5.1: lock_print_info_summary(): Remove a reference to innobase_mysql_end_print_arbitrary_thd() that should have been removed in r6347 when removing the function. r6350 \| marko \| 2009-12-22 11:11:09 +0200 (Tue, 22 Dec 2009) \| 1 line branches/5.1: Remove an obsolete declaration of LOCK_thread_count.	16 years ago
Vladislav Vaintroub	0d0ff32c6e	Bug#49834 - fixed a bug introduced by mismerge. restore original innobase version	16 years ago
Satya B	2f04df4ab0	Applying InnoDB snapshot 5.1-ss6344, part 2. Fixes BUG#41609 but does not address the printouts issue Detailed revision comments: r6310 \| marko \| 2009-12-15 15:23:54 +0200 (Tue, 15 Dec 2009) \| 30 lines branches/5.1: Merge r4922 from branches/zip. This the fix for the first part of Bug #41609 from InnoDB Plugin to the built-in InnoDB in MySQL 5.1. This allows InnoDB Hot Backup to back up a database while the built-in InnoDB in MySQL 5.1 is creating temporary tables. (This fix does not address the printouts about missing .ibd files for temporary tables at InnoDB startup, which was committed to branches/zip in r6252.) rb://219 approved by Sunny Bains. branches/zip: Distinguish temporary tables in MLOG_FILE_CREATE. This addresses Mantis Issue #23 in InnoDB Hot Backup and some of MySQL Bug #41609. In MLOG_FILE_CREATE, we need to distinguish temporary tables, so that InnoDB Hot Backup can work correctly. It turns out that we can do this easily, by using a bit of the previously unused parameter for page number. (The page number parameter of MLOG_FILE_CREATE has been written as 0 ever since MySQL 4.1, which introduced MLOG_FILE_CREATE.) MLOG_FILE_FLAG_TEMP: A flag for indicating a temporary table in the page number parameter of MLOG_FILE_ operations. fil_op_write_log(): Add the parameter log_flags. fil_op_log_parse_or_replay(): Add the parameter log_flags. Do not replay MLOG_FILE_CREATE when MLOG_FILE_FLAG_TEMP is set in log_flags. This only affects ibbackup --apply-log. InnoDB itself never replays file operations.	16 years ago
Vladislav Vaintroub	fef794a800	Bug #49811 : inconsistent usage of SAFEMALLOC in debug compilation on windows Remove per-project SAFEMALLOCs definitions, as they result in malloc/free mismatches.	16 years ago
Jon Olav Hauglid	a5beaf5cbf	Partial backport of: ------------------------------------------------------------ revno: 2617.14.26 committer: Vladislav Vaintroub <vvaintroub@mysql.com> branch nick: mysql-6.0-wtf timestamp: Wed 2008-11-05 11:19:19 +0100 message: CMakeLists.txt files cleanup. - remove SAFEMALLOC and SAFE_MUTEX definitions that were present in each CMakeLists.txt. Instead, put them into top level MakeLists.txt, but disable on Windows, because a) SAFEMALLOC does not add any functionality that is not already present in Debug C runtime ( and 2 safe malloc one on top of the other only unnecessarily slows down the server) b)SAFE_MUTEX does not work on Windows and have been explicitely disabled on Windows with #undef previously. Fortunately, ntdll does pretty good job identifying l problems with CRITICAL_SECTIONs. (DebugBreak()s on using uninited critical section, unlocking unowned critical section) -Remove occationally used -D_DEBUG (added by compiler anyway) -Remove MAP file generation, it became obsolete . There are many ways to get callstack of a crash now, with stacktrace in error log , minidump etc	16 years ago
Vladislav Vaintroub	cedb6101db	Cleanup, use MYSQL_INSTALL_TARGETS macro instead of INSTALL(TARGETS) combined with INSTALL_DEBUG_SYMBOLS	16 years ago
Gleb Shchepa	43d8e02f59	Bug #38883 : thd_security_context is not thread safe, crashes? After-push minor code cleanup for WL 2360: unnecessary external reference to LOCK_thread_count has been removed from ha_innodb.cc.	16 years ago
Vladislav Vaintroub	d2139f3135	- Introduce MYSQL_ADD_PLUGIN that replaces MYSQL_STORAGE_ENGINE - Fix semisync library prefix (remove lib on Unixes) - restrict exported symbols from zlib and yassl (fvisibility=hidden)	16 years ago
Satya B	cde05f0645	Applying InnoDB snapshot 5.1-ss6242, part 8. Fixes BUG#47720 1. BUG#47720 - REPLACE INTO Autoincrement column with negative values. Detailed revision comments: r6235 \| sunny \| 2009-11-26 01:14:42 +0200 (Thu, 26 Nov 2009) \| 9 lines branches/5.1: Fix Bug#47720 - REPLACE INTO Autoincrement column with negative values. This bug is similiar to the negative autoinc filter patch from earlier, with the additional handling of filtering out the negative column values set explicitly by the user. rb://184 Approved by Heikki.	16 years ago
Satya B	4b3114b60d	Applying InnoDB snapshot 5.1-ss6242, part 7. Fixes BUG#49032 1. BUG#49032 - auto_increment field does not initialize to last value in InnoDB Storage Engine 2. Fix whitespace issues and fix tests and make read float/double arg const Detailed revision comments: r6231 \| sunny \| 2009-11-25 10:26:27 +0200 (Wed, 25 Nov 2009) \| 7 lines branches/5.1: Fix BUG#49032 - auto_increment field does not initialize to last value in InnoDB Storage Engine. We use the appropriate function to read the column value for non-integer autoinc column types, namely float and double. rb://208. Approved by Marko. r6232 \| sunny \| 2009-11-25 10:27:39 +0200 (Wed, 25 Nov 2009) \| 2 lines branches/5.1: This is an interim fix, fix white space errors. r6233 \| sunny \| 2009-11-25 10:28:35 +0200 (Wed, 25 Nov 2009) \| 2 lines branches/5.1: This is an interim fix, fix tests and make read float/double arg const. r6234 \| sunny \| 2009-11-25 10:29:03 +0200 (Wed, 25 Nov 2009) \| 2 lines branches/5.1: This is an interim fix, fix whitepsace issues.	16 years ago
Satya B	96a121d35d	Applying InnoDB snapshot 5.1-ss6242, part 5. Fixes BUG#45961 1. BUG#45961 - DDL on partitioned innodb tables leaves data dictionary in an inconsistent state 2. Fix formatting Detailed revision comments: r6205 \| jyang \| 2009-11-20 07:55:48 +0200 (Fri, 20 Nov 2009) \| 11 lines branches/5.1: Add a special case to handle the Duplicated Key error and return DB_ERROR instead. This is to avoid a possible SIGSEGV by mysql error handling re-entering the storage layer for dup key info without proper table handle. This is to prevent a server crash when error situation in bug #45961 "DDL on partitioned innodb tables leaves data dictionary in an inconsistent state" happens. rb://157 approved by Sunny Bains. r6206 \| jyang \| 2009-11-20 09:38:43 +0200 (Fri, 20 Nov 2009) \| 3 lines branches/5.1: Non-functional change, fix formatting.	16 years ago

1 2 3 4 5 ...

463 Commits (062f57e2799bc74a2585670516a971aba31b63a0)