Hello Heikki,
Monday, March 19, 2001, 4:40:30 PM, you wrote:
>>Also the problem with innobase_flush_log_at_trx_commit=0 should be
>>there is no guarantie the last transaction commited will be on it's
>>place if the power would be lost. Also I don't know is it possible in
>>this case for database to be corrupted as some transactions may modify
>>database but are not in a logfile (Let's ask Heikki about this).
HT> The database does not get corrupted even if you use
HT> innobase_flush_logs_at_trx_commit=0 and it crashes: Innobase always writes
HT> the appropriate log segment to disk before writing a modified database
HT> page to disk. In this sense the log on disk is always 'ahead' of the disk
HT> image of the database. But, of course, you may lose the updates of the
HT> latest transactions in a crash, if the database has not yet written the
HT> relevant log segment to disk.
OK. The only question is is in this case only last transactions may be
lost, and what the transaction can be only be lost completely ?
I'm speaking about the situation - if I have connection there I have
1,2,3,4 transactions as a sequince - may it happen what changes made
by transaction 4 take place while while by transaction 3 not ?
--
Best regards,
Peter mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
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
