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
..
Makefile.am	Cset exclude: marko@hundin.mysql.fi|ChangeSet|20040525171209|56870	2004-06-17 11:57:45 +03:00
makefilewin	Added Innobase to source distribution	2001-02-17 14:19:19 +02:00
srv0que.c	que0que.c, srv0que.c:	2004-06-17 16:05:19 +03:00
srv0srv.c	InnoDB: Win64 portability fixes	2005-03-08 16:25:31 +02:00
srv0start.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