gbichot@quadita2.mysql.com 8b625529c9 This code change has 0 effects as it's about the case where innobase_very_fast_shutdown!=0, ... which is always false. In a very fast InnoDB shutdown, we just ensure that no more transactions are running, flush InnoDB log, signal InnoDB threads to die, and then return from InnoDB (from innobase_end()) without waiting for those threads to actually die. I have tested on a 4CPU machine that even with --innodb_flush_log_at_trx_commit=0, this optimized InnoDB very fast shutdown loses no committed transactions. Patch pre-approved by Heikki.		2005-03-09 00:32:58 +01:00
..
log0log.c	This code change has 0 effects as it's about the case where innobase_very_fast_shutdown!=0,	2005-03-09 00:32:58 +01:00
log0recv.c	After review fixes. Fix bugs in TRUNCATE.	2005-03-01 19:42:59 +02:00
Makefile.am	- Fixed bug in "make DESTDIR=<dir> install" - the InnoDB static	2003-04-10 20:03:52 +02:00
makefilewin	Added Innobase to source distribution	2001-02-17 14:19:19 +02:00