vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Another newbie question (new to mysql but not database administration). I'm setting up a database using InnoDB tables. Seems that InnoDB maintains it's own transaction logs in addition to the mysql binlog. Is there any benefit to setting sync_binlog=1? I read somewhere in the manual that this is the "safest" setting, but if InnoDB is able to rollback uncommitted transactions during crash recovery using it's own logs, what's the point of setting sync_binlog=1? Just to keep the mysql binlog in sync with the InnoDB logs? What advantage is there even to that if the uncommitted transactions get properly rolled back by InnoDB? TIA -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with PCLinuxOS - http://enigmail.mozdev.org iEYEARECAAYFAkeaAE8ACgkQzIf+rZpn0oR3NgCggSKZP3iPYm U6twaBGpdQJcDm 0KgAoJxhqHRGVbY5BRh5M69Nzc8sup8r =cjUR -----END PGP SIGNATURE----- |