MySQL Forums
Forum List  »  Replication

Statement instead of Row type?
Posted by: Stephen Boesch
Date: May 23, 2011 08:11PM

Although my.cnf is set to ROW and have verified (via show variables) it "took", i'm seeing statement format binlogs at this point. The ROW format was working before, I am not sure why this changed. I am running

I restarted mysql and the Statement (instead of row) continues to happen - even though the show variables displays ROW.

I know it's statement because running mysqlbinlog is generating output like the following:

(mysqlbinlog --base64-output=decode-rows --verbose <file>)
Server version: 5.1.56-log MySQL Community Server (GPL)


UPDATE QRTZ_SCHEDULER_STATE SET LAST_CHECKIN_TIME = 1306202473922, RECOVERER = null WHERE INSTANCE_NAME = 'googleetest9-gnt-new.hot.corp.google.com:9005'
UPDATE QRTZ_SCHEDULER_STATE SET LAST_CHECKIN_TIME = 1306202481482, RECOVERER = null WHERE INSTANCE_NAME = 'googleetest9-gnt-new.hot.corp.google.com:9005'
UPDATE QRTZ_SCHEDULER_STATE SET LAST_CHECKIN_TIME = 1306202488984, RECOVERER = null WHERE INSTANCE_NAME = 'googleetest9-gnt-new.hot.corp.google.com:9005'
UPDATE QRTZ_SCHEDULER_STATE SET LAST_CHECKIN_TIME = 1306202496487, RECOVERER = null WHERE INSTANCE_NAME = 'googleetest9-gnt-new.hot.corp.google.com:9005'
UPDATE QRTZ_TRIGGERS SET TRIGGER_STATE = 'MISFIRED' WHERE (TRIGGER_STATE = 'WAITING' OR TRIGGER_STATE = 'WAITING') AND NEXT_FIRE_TIME < 1306202437971


Those are statement type not ROW type.


Here is output of show variables.


mysql> show variables like '%log%';
+-----------------------------------------+----------------------------------------------+
| Variable_name | Value |
+-----------------------------------------+----------------------------------------------+
| back_log | 50 |
| binlog_cache_size | 32768 |
| binlog_direct_non_transactional_updates | OFF |
| binlog_format | ROW |
| expire_logs_days | 0 |
| general_log | OFF |
| general_log_file | /usr/local/google/mysql/corpeng-pipe-vm3.log |
| innodb_flush_log_at_trx_commit | 1 |
| innodb_locks_unsafe_for_binlog | OFF |
| innodb_log_buffer_size | 1048576 |
| innodb_log_file_size | 5242880 |
| innodb_log_files_in_group | 2 |
| innodb_log_group_home_dir | ./ |
| innodb_mirrored_log_groups | 1 |
| log | OFF |
| log_bin | ON |
| log_bin_trust_function_creators | OFF |
| log_bin_trust_routine_creators | OFF |
| log_error | /var/log/mysqld.log |
| log_output | FILE |
| log_queries_not_using_indexes | OFF |
| log_slave_updates | ON |
| log_slow_queries | ON |
| log_warnings | 1 |
| max_binlog_cache_size | 18446744073709547520 |
| max_binlog_size | 2097152 |
| max_relay_log_size | 0 |
| relay_log | |
| relay_log_index | |
| relay_log_info_file | relay-log.info |
| relay_log_purge | ON |
| relay_log_space_limit | 0 |
| slow_query_log | ON |
| slow_query_log_file | ON |
| sql_log_bin | ON |
| sql_log_off | OFF |
| sql_log_update | ON |
| sync_binlog | 0 |
+-----------------------------------------+----------------------------------------------+
38 rows in set (0.00 sec)

Options: ReplyQuote


Subject
Views
Written By
Posted
Statement instead of Row type?
2692
May 23, 2011 08:11PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.