summaryrefslogtreecommitdiff
path: root/sql/ha_innodb.cc
Commit message (Collapse)AuthorAgeFilesLines
* row0purge.c, row0mysql.c, os0file.c, os0file.h, fil0fil.h, fil0fil.c:heikki@hundin.mysql.fi2003-10-141-2/+1
| | | | | | IMPORT TABLESPACE must reset lsns if they are too high ha_innodb.cc: DISCARD/IMPORT TABLESPACE must have a TL_WRITE lock on the table
* Many files:heikki@hundin.mysql.fi2003-10-131-6/+45
| | | | | ALTER TABLE ... DISCARD/IMPORT TABLESPACE Track crash in buf_LRU_block_remove_hashed_page + 1807 reported in MySQL-3.23.5x
* Many files:heikki@hundin.mysql.fi2003-10-071-262/+397
| | | | | | | | Multiple tablespaces for InnoDB sql_table.cc: Tell explicitly that InnoDB should retrieve all columns in CHECKSUM TABLE sql_update.cc, sql_select.cc, my_base.h: More descriptive flag name HA_EXTRA_RETRIEVE_ALL_COLS
* SCRUMhf@deer.(none)2003-09-191-1/+1
| | | | | | | embedded library hash_insert renamed to my_hash_insert to avoid name intersection with another libraries is there better idea?
* Fix results for mix_innodb_myisam_binlogmonty@mashka.mysql.fi2003-09-121-34/+33
| | | | Optimize calls to current_thd
* After merge fixes.monty@mashka.mysql.fi2003-09-111-88/+7
| | | | Note that mix_innodb_myisam_binlog and union fails after this patch (Will be fixed shortly by maintaners of this code)
* merge with 4.0.15monty@narttu.mysql.fi2003-08-291-1/+0
|\
| * item_func.h:Sinisa@sinisa.nasamreza.org2003-08-201-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | Fix for a bug with LEAST() in WHERE clause ha_innodb.cc: Fix for a configure bug multi_update.result, multi_update.test: Fix for the update with NULL's in the result set sql_update.cc: Fix for the update with NULL's in the result set Fix for the update with NULL's in the result set Fix for the update with NULL's in the result set
* | Merge with 4.0.14monty@mashka.mysql.fi2003-08-111-136/+450
|\ \ | |/
| * ha_innodb.cc:heikki@hundin.mysql.fi2003-07-081-0/+7
| | | | | | | | Prevent the user from creating InnoDB tables with > 1000 columns
| * ha_innodb.cc:heikki@hundin.mysql.fi2003-07-031-4/+4
| | | | | | | | Since the mysql interactive client or some other phase in communication cuts > 64 kB strings to very short, restrict the output of SHOW INNODB STATUS to at most 60 kB
| * Many files:heikki@hundin.mysql.fi2003-07-031-5/+5
| | | | | | | | | | | | Remove potential starvation of a full log buffer flush: only flush up to the lsn which was the largest at the time when we requested the full log buffer flush os0sync.h, os0sync.c: Fix a bug in os_event on Unix: even though we signaled the event, some threads could continue waiting if the event became nonsignaled quickly again; this made group commit less efficient than it should be
| * ha_innodb.cc:heikki@hundin.mysql.fi2003-07-021-2/+0
| | | | | | | | Cleanup
| * ha_innodb.cc:heikki@hundin.mysql.fi2003-07-021-13/+25
| | | | | | | | Remove still some potential hangs over the btr0sea.c semaphore
| * ha_innodb.cc:heikki@hundin.mysql.fi2003-07-011-27/+34
| | | | | | | | Fix a possible hang over the btr0sea.c latch
| * Merge bk-internal.mysql.com:/home/bk/mysql-4.0monty@narttu.mysql.fi2003-06-231-0/+6
| |\ | | | | | | | | | into narttu.mysql.fi:/my/mysql-4.0
| | * Added analyze as alias for optimizemonty@narttu.mysql.fi2003-06-231-0/+6
| | |
| * | dict0dict.h, dict0dict.c, ha_innodb.cc:heikki@hundin.mysql.fi2003-06-221-4/+7
| | | | | | | | | | | | In ORDER BY MySQL seems to set the key read flag also in the case where the primary key contains only a prefix of a column - not the whole column; to prevent potential bugs retrieve the whole column if the index contains a prefix of it
| * | row0mysql.c, dict0dict.ic:heikki@hundin.mysql.fi2003-06-161-1/+2
| | | | | | | | | | | | | | | | | | Cleanup ha_innodb.cc, data0type.h: Make sure non-latin1 users can downgrade from 4.0.14 to an earlier version if they have not created DATA_BLOB column prefix indexes
| * | handler.h, ha_innodb.h, ha_innodb.cc:heikki@hundin.mysql.fi2003-06-151-11/+15
| | | | | | | | | | | | Cleanup; remove compiler warning on Windows
| * | Many files:heikki@hundin.mysql.fi2003-06-151-88/+364
| |/ | | | | | | Merge InnoDB-4.0.14: SAVEPOINT now implemented; InnoDB now accepts also column prefix keys; crashing bug in ON UPDATE CASCADE fixed; page checksum formula fixed
* | Merge with 4.0.13monty@narttu.mysql.fi2003-06-051-76/+146
|\ \ | |/
| * ha_innodb.cc:heikki@hundin.mysql.fi2003-06-051-2/+1
| | | | | | | | Revert a change to dict_mem_index_add_field which slipped prematurely into the bk tree
| * ha_innodb.cc, handler.cc:heikki@hundin.mysql.fi2003-06-051-78/+149
| | | | | | | | Fix the BDB crash in the previous push; to save CPU remove duplicate calls of commit in InnoDB
* | ha_innodb.cc:heikki@hundin.mysql.fi2003-05-261-2/+2
| | | | | | | | | | | | Remove accidenatlly committed debug printfs when query cache is used sql_update.cc, sql_load.cc, sql_insert.cc, sql_delete.cc: For the transactional query cache algorithm to work we must invalidate the query cache in INSERT/DELETE/UPDATE before writing to the binlog or calling ha_autocommit_... Note that binlog writing may also call commit. The crucial thing is that the transaction which modified data must not be committed BEFORE the query cache is invalidated.
* | Merge with 4.0.13monty@narttu.mysql.fi2003-05-191-37/+136
|\ \ | |/
| * Many files:heikki@hundin.mysql.fi2003-05-031-18/+46
| | | | | | | | Eliminate the LOCK_log bottleneck in group commit in binlogging: flush InnoDB log files only after it has been released
| * Merge bk-internal.mysql.com:/home/bk/mysql-4.0monty@mashka.mysql.fi2003-04-271-9/+0
| |\ | | | | | | | | | into mashka.mysql.fi:/home/my/mysql-4.0
| | * trx0trx.h, trx0trx.c, ha_innodb.cc:heikki@hundin.mysql.fi2003-04-271-9/+0
| | | | | | | | | | | | Remove code never actually used in IGNORE; InnoDB just rolls back the latest row insert or update on a duplicate key error and leaves it for MySQL to decide whether to ignore the error
| * | Merge with 3.23:monty@mashka.mysql.fi2003-04-261-1/+1
| |/ | | | | | | | | | | Set innobase_flush_log_at_trx_commit to 1 by default Fix problem with timestamp on 64 bit systems Reserve alarms for up to 10 slave threads
| * ha_innodb.cc:heikki@hundin.mysql.fi2003-04-241-0/+1
| | | | | | | | When FLUSH LOGS is called, flush InnoDB logs to disk also in the case innodb_flush_log_at_trx_commit=0
| * ha_innodb.h, ha_innodb.cc:heikki@hundin.mysql.fi2003-04-241-0/+17
| | | | | | | | Make ANALYZE TABLE to update index cardinality and other statistics also for an InnoDB table; note that the estimates are based on 10 random dives, not on an exhaustive read of the table
| * mergemonty@narttu.mysql.fi2003-04-241-4/+25
| |\
| | * Fixes for valgrindmonty@narttu.mysql.fi2003-04-231-4/+25
| | | | | | | | | | | | | | | | | | Added optimzation for clustered index Fixed bug in UPDATE ... ORDER BY Fixed handling of UPDATE ... LIMIT
| * | ha_innodb.cc:heikki@hundin.mysql.fi2003-04-181-2/+12
| | | | | | | | | | | | | | | Prevent crash if MySQL calls rnd_end WITOUT calling rnd_init first: only restore active_index if it the old value was pushed in rnd_init Initialize active_index to a sensible value: prevent crash if we restore it to the original value after an table scan
| * | ha_innodb.h, ha_innodb.cc:heikki@hundin.mysql.fi2003-04-181-28/+43
| | | | | | | | | | | | | | | | | | Make InnoDB to restore old active_index value after a table scan: MySQL may assume that a scan does NOT change active_index; this partially fixes bug 241 of UPDATE ... ORDER BY ... but it still remains that MySQL actually ignores the ORDER BY for both MyISAM and InnoDB tables log0recv.c: Use fflush to make sure report of a corrupt log record is printed to .err log before mysqld crashes
| * | ha_innodb.cc, row0sel.c, row0mysql.c, row0mysql.h:heikki@hundin.mysql.fi2003-04-171-1/+5
| | | | | | | | | | | | Allow HANDLER PREV and NEXT also after positioning the cursor with a unique search on the primary key
| * | Many files:heikki@hundin.mysql.fi2003-04-161-0/+14
| |/ | | | | | | Merge InnoDB-4.0.13; DROP FOREIGN KEY now works
* | forgot to commit this one in cset 1.1561 (replication)guilhem@mysql.com2003-04-251-4/+4
| |
* | mergingbell@sanja.is.com.ua2003-04-161-1/+1
|\ \
| * \ Merge sanja.is.com.ua:/home/bell/mysql/mysql-4.1bell@sanja.is.com.ua2003-02-181-1/+1
| |\ \ | | | | | | | | | | | | into sanja.is.com.ua:/home/bell/mysql/work-qc-4.1
| | * \ mergingbell@sanja.is.com.ua2002-12-111-1/+1
| | |\ \
| | | * | new innodb query cache behaviour (recommit because of problem with 4.1 ↵bell@sanja.is.com.ua2002-11-031-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | repository pushing) fixed bug in quqry cache dbd transaction processing
* | | | | Merge bk-internal.mysql.com:/home/bk/mysql-4.1monty@narttu.mysql.fi2003-03-171-1/+1
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | into narttu.mysql.fi:/my/mysql-4.1
| * | | | | Preparing to client<->server autoconvertbar@bar.mysql.r18.ru2003-03-171-1/+1
| | | | | |
* | | | | | Merge with 4.0monty@narttu.mysql.fi2003-03-161-4/+28
|\ \ \ \ \ \ | |/ / / / / |/| | | | / | | |_|_|/ | |/| | |
| * | | | ha_innodb.cc:heikki@hundin.mysql.fi2003-03-131-0/+10
| | | | | | | | | | | | | | | | | | | | Fix bug: MySQL could erroneously return Empty set if InnoDB estimated index range size to 0 records though the range was not empty; MySQL also failed to do the next-key locking in the case of an empty index range
| * | | | ha_innodb.cc:heikki@hundin.mysql.fi2003-03-041-0/+4
| | | | | | | | | | | | | | | | | | | | Add comment that Guilhem should check master_log_name, pending etc are right if the master log gets rotated
| * | | | ha_innodb.cc:heikki@hundin.mysql.fi2003-03-041-4/+1
| | | | | | | | | | | | | | | | | | | | Remove (already commented out) code about storing the latest relay log pos info to InnoDB: we will probably use only the master log pos info when we restart a slave after a crash
| * | | | ha_innodb.h, ha_innodb.cc, handler.h, handler.cc, sql_class.cc:heikki@hundin.mysql.fi2003-03-031-0/+13
| | | | | | | | | | | | | | | | | | | | Fix a hang on the adaptive hash S-latch if an application program uses mysql_use_result() and performs queries on two connections at the same time
View Lorry Controller Status