On Wed, Jan 30, 2002 at 03:06:36PM -0800, Joseph Drozdik wrote: > Hi all, > > I've been looking at the performance of mysql using innodb tables > and I've noticed that I can get a huge benifit by setting > innodb_flush_log_at_trx_commit = 0. The documentation warns me that > I can loose a couple of seconds of transactions in system crash if I > do this. > > It seems like a great tradeoff but the question is, is there any way > that this delayed flushing can cause multi-query transactions to be > only half-flushed. Loosing some transactions is ok but loosing half > of one would be unnacceptable.
The whole point of transactions is that there is not such thing as "half a transaction" from the database's point of view. If the server dies and it must used the transaction log to playback transactions upon restart, it will only play back committed transactions. Jeremy -- Jeremy D. Zawodny, <[EMAIL PROTECTED]> Technical Yahoo - Yahoo Finance Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 685-5936 MySQL 3.23.41-max: up 27 days, processed 620,964,155 queries (256/sec. avg) --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
