summaryrefslogtreecommitdiff
path: root/innobase
Commit message (Collapse)AuthorAgeFilesLines
* Merge hundin.mysql.fi:/home/marko/k/mysql-4.0marko@hundin.mysql.fi2005-05-261-0/+5
|\ | | | | | | into hundin.mysql.fi:/home/marko/mysql-4.1
| * InnoDB: Check all referencing tables in DROP DATABASE (Bug #10335).marko@hundin.mysql.fi2005-05-261-0/+5
| |
* | row0mysql.c:heikki@hundin.mysql.fi2005-05-131-2/+10
| | | | | | | | InnoDB wrongly complained in the .err log that MySQL is trying to drop a non-existent table, if tablespace ran out (Bug #10607)
* | Merge marko@bk-internal.mysql.com:/home/bk/mysql-4.1marko@hundin.mysql.fi2005-05-064-20/+61
|\ \ | | | | | | | | | into hundin.mysql.fi:/home/marko/mysql-4.1
| * | InnoDB: Truncate SHOW INNODB STATUS output at the start of the listmarko@hundin.mysql.fi2005-04-194-20/+61
| | | | | | | | | | | | of active transactions, if necessary and possible. (Bug #5436)
* | | dict0dict.c, dict0dict.h, fil0fil.c:heikki@hundin.mysql.fi2005-04-273-1/+27
|/ / | | | | | | Fix a problem in crash recovery of .ibd files on Windows if the user used lower_case_table_names=0 or 2; the directory scan in crash recovery forgot to put all paths to lower case, so that the tablespace name would be consistent with the internal data dictionary of InnoDB; remember that InnoDB puts internally all database names and table names to lower case on Windows, regardless of the value of lower_case_table_names
* | Fixed a bug: deadlock without any locking, simple select and update (Bug #7975).jan@hundin.mysql.fi2005-04-181-18/+23
| | | | | | | | Backported from 5.0.3.
* | fil0fil.c:heikki@hundin.mysql.fi2005-04-141-19/+51
| | | | | | | | Add fault tolerance in the scan of .ibd files at a crash recovery; formerly a single failure of readdir_get_next caused the rest of the directory to be skipped
* | fil0fil.c:heikki@hundin.mysql.fi2005-04-131-1/+2
| | | | | | | | At the shutdown, write the latest lsn only to the first pages of the ibdata files of the system tablespace, NOT to the .ibd files; writing to tens of thousands .ibd files can take minutes
* | row0sel.c:heikki@hundin.mysql.fi2005-04-131-12/+12
| | | | | | | | Do not test the value of err if the lock operation was skipped because innodb_logs_unsafe_for_binlog was TRUE; though this did not cause any bugs visible to the user, because err is inited to DB_SUCCESS at the start of the function row_search_for_mysql()
* | InnoDB: Ignore character set mismatch in ALTER TABLE and RENAME TABLEmarko@hundin.mysql.fi2005-04-125-18/+30
| | | | | | | | if foreign_key_checks=0. (Bug #9802)
* | InnoDB: Avoid test suite failures caused by a locking conflictmarko@hundin.mysql.fi2005-04-063-4/+30
| | | | | | | | | | | | | | | | between two server instances at server shutdown/startup. This conflict on advisory locks appears to be the result of a bug in the operating system; these locks should be released when the files are closed, but somehow that does not always happen immediately in Linux. (Bug #9381)
* | row0sel.c, btr0pcur.c, btr0pcur.ic, btr0pcur.h:heikki@hundin.mysql.fi2005-04-064-1/+27
| | | | | | | | Add diagnostic code to track assertion failure in ut_a(cursor->old_stored == BTR_PCUR_OLD_STORED); the failure happened in OPTIMIZE TABLE, and in 4.0.24 in some other context
* | dict0dict.c:heikki@hundin.mysql.fi2005-04-051-0/+3
| | | | | | | | Add a note that ENUM in new tables cannot reference ENUM in old tables, in FOREIGN KEY constraints
* | trx0trx.c:heikki@hundin.mysql.fi2005-03-211-1/+9
| | | | | | | | If MySQL wrote to its binlog, but for some reason trx->update_undo and trx->insert_undo were NULL in InnoDB, then trx->commit_lsn was garbage, and InnoDB could assert in the log flush of trx_commit_complete_for_mysql() (Bug #9277)
* | Mergeheikki@hundin.mysql.fi2005-03-211-0/+6
|\ \ | |/
| * trx0trx.c, trx0trx.h:heikki@hundin.mysql.fi2005-03-212-1/+15
| | | | | | | | If MySQL wrote to its binlog, but for some reason trx->update_undo and trx->insert_undo were NULL in InnoDB, then trx->commit_lsn was garbage, and InnoDB could assert in the log flush of trx_commit_complete_for_mysql() (Bug #9277)
* | Merge hundin.mysql.fi:/home/marko/k/mysql-4.0marko@hundin.mysql.fi2005-03-151-1/+8
|\ \ | |/ | | | | into hundin.mysql.fi:/home/marko/mysql-4.1
| * dict0load.c:marko@hundin.mysql.fi2005-03-141-1/+8
| | | | | | | | | | dict_load_table(): Refuse to open ROW_FORMAT=COMPACT tables of MySQL 5.0.3 and later.
* | buf0flu.c:heikki@hundin.mysql.fi2005-03-151-1/+9
| | | | | | | | Add diagnostics to track why ut_a(block->state == BUF_BLOCK_FILE_PAGE) failed in buf_flush_ready_for_replace() for a user
* | log0recv.c:heikki@hundin.mysql.fi2005-03-091-1/+3
| | | | | | | | | | Better ibbackup message Add a message explaining why we do a 'crash recovery' after an ibbackup restore; suggested by Tim Smith
* | dict0load.c:marko@hundin.mysql.fi2005-03-081-17/+0
| | | | | | | | | | dict_load_table(): Do not complain about mix_len != 0, because MySQL 3.23.4x left garbage in that column.
* | After merge fixesmarko@hundin.mysql.fi2005-03-081-17/+1
|\ \ | |/
| * dict0load.c:marko@hundin.mysql.fi2005-03-081-16/+0
| | | | | | | | | | | | dict_load_table(): Remove the check for row_format=compact for now, because the flag bit we used (high-order bit of mix_len) has not been zero for at least two customers.
* | Merge hundin.mysql.fi:/home/marko/k/mysql-4.0marko@hundin.mysql.fi2005-03-082-1/+2
|\ \ | |/ | | | | into hundin.mysql.fi:/home/marko/mysql-4.1
| * InnoDB: Win64 portability fix: add missing declaration andmarko@hundin.mysql.fi2005-03-082-1/+2
| | | | | | | | correct the definition of srv_max_buf_pool_modified_pct.
* | Merge marko@bk-internal.mysql.com:/home/bk/mysql-4.1marko@hundin.mysql.fi2005-03-0716-46/+51
|\ \ | | | | | | | | | into hundin.mysql.fi:/home/marko/mysql-4.1
| * | InnoDB: Portability fixes for warnings reported on IA-64 Windowsmarko@hundin.mysql.fi2005-03-0716-46/+51
| | |
* | | trx0trx.c:heikki@hundin.mysql.fi2005-03-071-0/+2
|/ / | | | | | | Print a hex dump of the trx_t object if trx->n_mysql_tables_in_use != 0 at trx_free()
* | ut0mem.c:heikki@hundin.mysql.fi2005-03-041-8/+28
| | | | | | | | If InnoDB cannot allocate memory, keep retrying for 60 seconds before we crash mysqld; maybe the memory shortage is just temporary
* | trx0trx.c:heikki@hundin.mysql.fi2005-03-041-3/+14
| | | | | | | | Do not assert, but print diagnostics if MySQL tries to free a trx where n_mysql_tables_in_use > 0
* | Merge marko@bk-internal.mysql.com:/home/bk/mysql-4.1marko@hundin.mysql.fi2005-03-041-2/+3
|\ \ | | | | | | | | | into hundin.mysql.fi:/home/marko/mysql-4.1
| * | row0sel.c:marko@hundin.mysql.fi2005-03-011-2/+3
| | | | | | | | | | | | row_sel_store_mysql_rec(): Do not try to space-pad BLOB fields. (Bug #8771)
* | | srv0start.c:heikki@hundin.mysql.fi2005-03-031-2/+16
| | | | | | | | | | | | Work around the AIX 5.1 security patch ML7 problem in errno when it should be EEXIST
* | | Mergeheikki@hundin.mysql.fi2005-03-031-9/+0
|\ \ \ | | |/ | |/|
| * | srv0start.c:heikki@hundin.mysql.fi2005-03-032-11/+17
| | | | | | | | | | | | | | | | | | Work around the AIX 5.1 ML7 patch problem in errno at a higher level, in srv0start.c os0file.c: Revert the AIX patch here
* | | Merge hundin.mysql.fi:/home/heikki/mysql-4.0heikki@hundin.mysql.fi2005-03-031-0/+9
|\ \ \ | |/ / | | / | |/ |/| into hundin.mysql.fi:/home/heikki/mysql-4.1
| * os0file.c:heikki@hundin.mysql.fi2005-03-031-0/+9
| | | | | | | | AIX 5.1 after security patch ML7 seems to contain a bug that instead of EEXIST it sets errno to 0 if a file creation fails because the file already exists. Work around that bug by interpreting errno 0 in AIX as EEXIST.
* | After merge fixesmarko@hundin.mysql.fi2005-03-012-8/+5
|\ \ | |/
| * InnoDB: Fix compilation errors on IA-64 Windowsmarko@hundin.mysql.fi2005-03-012-4/+4
| |
* | Merge bk-internal.mysql.com:/home/bk/mysql-4.1monty@mysql.com2005-02-281-1/+2
|\ \ | | | | | | | | | into mysql.com:/home/my/mysql-4.1
| * | Fixed wrong memory references found by purifymonty@mysql.com2005-02-281-1/+2
| | | | | | | | | | | | (No really critical errors found, but a few possible wrong results)
* | | fil0fil.c:heikki@hundin.mysql.fi2005-02-251-7/+7
| | | | | | | | | | | | Check if node == NULL, which means we are outside tablespace bounds, and print a big fatal error message
* | | row0sel.c:heikki@hundin.mysql.fi2005-02-221-2/+7
|/ / | | | | | | Fix bug #8677: if one used LOCK TABLES, created an InnoDB temp table, and did a multi-table update where a MyISAM table was the update table and the temp table was a read table, then InnoDB aserted in row0sel.c because n_mysql_tables_in_use was 0. Also, we remove the assertion altogether and just print an error to the .err log if this important consistency check fails. Then it is up to the user to read the .err log and notice the problem if there still are errors in MySQL's table locking.
* | Merge hundin.mysql.fi:/home/heikki/mysql-4.0heikki@hundin.mysql.fi2005-02-131-1/+1
|\ \ | |/ | | | | into hundin.mysql.fi:/home/heikki/mysql-4.1
| * row0mysql.c:heikki@hundin.mysql.fi2005-02-131-1/+1
| | | | | | | | Backport the column prefix memory corruption fix from 5.0
| * eval0eval.ic:heikki@hundin.mysql.fi2005-02-021-2/+0
| | | | | | | | Remove wrong assertion that fails on 64 bits
| * rem0rec.ic:heikki@hundin.mysql.fi2005-02-021-14/+14
| | | | | | | | Fix a debug assertion in rem0rec.ic on AMD64; 4.1 was already fixed
| * mem0pool.c:heikki@hundin.mysql.fi2005-01-311-2/+2
| | | | | | | | Fix an assertion failure in 64-bit computers if UNIV_MEM_DEBUG is defined
| * InnoDB: Backport innodb_autoextend_increment from 4.1marko@hundin.mysql.fi2005-01-252-1/+6
| |
View Lorry Controller Status