Hi! ----- Original Message ----- From: "Jeremy Zawodny" <[EMAIL PROTECTED]> To: "Dyego Souza do Carmo" <[EMAIL PROTECTED]> Cc: "Heikki Tuuri" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Monday, October 07, 2002 10:10 PM Subject: Re: The secure mode in InnoDB
> On Mon, Oct 07, 2002 at 01:53:25PM -0300, Dyego Souza do Carmo wrote: > > Hello Heikki ! > > > > what is the best secure mode to use innodb ? ( min time to write data > > in disk ) > > You're confusing two ideas. The most secure (reliable) is 1. The > fastest is 0. You can't have both. Jeremy is right. 1 is the only option which calls fsync after each log write at trx commit. An fsync flushes the log to disk, at least in theory. For most users who need high speed, 2 is the best option starting from 3.23.52. It writes the log buffer to the log file at each commit. You will not lose committed transactions in a pure mysqld process crash as long as your OS does not crash, or there is no power outage. That is because the OS file cache is not lost in a pure mysqld crash. > Jeremy Regards, Heikki sql query > -- > Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! > <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ > > MySQL 3.23.51: up 62 days, processed 1,331,355,814 queries (246/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
