# Unsafe statement written to the binary log using since BINLOG\_FORMAT = STATEMENT... **URL:** \ **Category:** Percona Toolkit\ **Created:** [May 4, 2016, 8:21pm UTC](https://forums.percona.com/t/unsafe-statement-written-to-the-binary-log-using-since-binlog-format-statement/4872 "2016-05-04T20:21:43Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Helix](https://avatars.discourse-cdn.com/v4/letter/h/e19adc/32.png) [@Helix](https://forums.percona.com/u/Helix)\ **Post date:** [May 4, 2016, 8:21pm UTC](https://forums.percona.com/t/unsafe-statement-written-to-the-binary-log-using-since-binlog-format-statement/4872/1 "2016-05-04T20:21:43Z")
Hi, ALL there are many warning messages like below when use pt-table-checksum to check 3 nodes data in our PXC, why it occur? And are there any way correct that ? In the my.cnf file, BINLOG\_FORMAT is set to ROW, thanks in advance. 2016-05-05 03:37:41 24482 [Warning] Unsafe statement written to the binary log using statement format since BINLOG\_FORMAT = STATEMENT. REPLACE… SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave. Statement: REPLACE INTO `percona`.`checksums` (db, tbl, chunk, chunk\_index, lower\_boundary, upper\_boundary, this\_cnt, this\_crc) SELECT /_!99997_/ ‘sp2p’, ‘t\_wsapi\_token’, ‘2’, ‘PRIMARY’, ‘694425’, ‘1004712’, COUNT(\*) AS cnt, COALESCE(LOWER(CONV(BIT\_XOR(CAST(CRC32(CONCAT\_WS(‘#’, `ws_api_token_id`, `fk_ws_api_user_id`, `token`, `comment`, UNIX\_TIMESTAMP(`create_time`), UNIX\_TIMESTAMP(`update_time`), `create_by`, `update_by`, `record_status`, CONCAT(ISNULL(`comment`), ISNULL(`create_time`), ISNULL(`update_time`), ISNULL(`create_by`), ISNULL(`update_by`)))) AS UNSIGNED)), 10, 16)), 0) AS crc FROM `sp2p`.`t_wsapi_token` FORCE INDEX(`PRIMARY`) WHERE ((`ws_api_token_id` \>= ‘694425’)) AND ((`ws_api_token_id` \<= '100471