thank you for your reply :) I've roughly read some source codes about MYSQL_BIN_LOG & Log_Event. It seems that the way which mysql writes binlog in is per Log_Event. In that case, records are stored in sequence, just like plain text logs does. So, even if I can write pure SQLs into an another plain text log with simultaneous binlog-writes, the file could get corruptted with fairly close probability as binlog does...
Do I miss something? 2009/2/24 Baron Schwartz <ba...@xaprb.com>: > Hi, > > On Mon, Feb 23, 2009 at 11:10 PM, Cui Shijun <rancp...@gmail.com> wrote: >> hi, >> I've been using mysql-5.1.22 in my project, which processes a lot of >> read operations but little write operations. I got the idea from some >> of my coworkers that binlog has a chance to be corrputed so that >> mysqlbinlog can't process it correctly. >> >> Is there any usable plain text SQL log in mysql( I care about write >> operations only )? If not, where to start with if I want to add such a >> log? > > The plain text logs have the same problem. The binlog is generally as > reliable as anything you could build yourself IMO. > > Baron > > -- > Baron Schwartz, Director of Consulting, Percona Inc. > Our Blog: http://www.mysqlperformanceblog.com/ > Our Services: http://www.percona.com/services.html > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
