API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Sep 20th, 2019
227
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 52.25 KB | None | 0 0
raw download clone embed print report
  1. 2019-09-20 11:36:52 34943159552 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE sfk_posts SET post_password = '7008ed35e411e3c29715', post_modified_gmt = '2019-09-20 11:36:52', post_modified = '2019-09-20 11:36:52' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:36:52' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  2. 2019-09-20 11:36:58 34894651392 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave. Statement: INSERT IGNORE INTO sfk_mailpoet_subscribers (is_woocommerce_user, email, status, created_at, last_subscribed_at, source)
  3. SELECT 1, wppm.meta_value, "subscribed", CURRENT_TIMESTAMP(), CURRENT_TIMESTAMP(), "woocommerce_user" FROM `sfk_postmeta` wppm
  4. JOIN `sfk_posts` p ON wppm.post_id = p.ID AND p.post_type = "shop_order"
  5. WHERE wppm.meta_key = "_billing_email" AND wppm.meta_value != ""
  6. AND p.ID = "51067"
  7. ON DUPLICATE KEY UPDATE is_woocommerce_user = 1
  8. 2019-09-20 11:36:58 34894651392 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on master and the slave. Statement: INSERT IGNORE INTO sfk_mailpoet_subscribers (is_woocommerce_user, email, status, created_at, last_subscribed_at, source)
  9. SELECT 1, wppm.meta_value, "subscribed", CURRENT_TIMESTAMP(), CURRENT_TIMESTAMP(), "woocommerce_user" FROM `sfk_postmeta` wppm
  10. JOIN `sfk_posts` p ON wppm.post_id = p.ID AND p.post_type = "shop_order"
  11. WHERE wppm.meta_key = "_billing_email" AND wppm.meta_value != ""
  12. AND p.ID = "51067"
  13. ON DUPLICATE KEY UPDATE is_woocommerce_user = 1
  14. 2019-09-20 11:36:58 34894651392 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: INSERT IGNORE INTO sfk_mailpoet_subscribers (is_woocommerce_user, email, status, created_at, last_subscribed_at, source)
  15. SELECT 1, wppm.meta_value, "subscribed", CURRENT_TIMESTAMP(), CURRENT_TIMESTAMP(), "woocommerce_user" FROM `sfk_postmeta` wppm
  16. JOIN `sfk_posts` p ON wppm.post_id = p.ID AND p.post_type = "shop_order"
  17. WHERE wppm.meta_key = "_billing_email" AND wppm.meta_value != ""
  18. AND p.ID = "51067"
  19. ON DUPLICATE KEY UPDATE is_woocommerce_user = 1
  20. 2019-09-20 11:36:58 34944708352 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE md FROM `sfk_mobileassistant_devices` md
  21. LEFT JOIN `sfk_mobileassistant_push_settings` mpn ON mpn.`device_unique_id` = md.`device_unique_id`
  22. WHERE mpn.`device_unique_id` IS NULL
  23. 2019-09-20 11:36:58 34944708352 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE ma FROM `sfk_mobileassistant_accounts` ma
  24. LEFT JOIN `sfk_mobileassistant_devices` md ON md.`account_id` = ma.`id`
  25. WHERE ma.`id` IS NULL
  26. 2019-09-20 11:36:58 34944708352 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE md FROM `sfk_mobileassistant_devices` md
  27. LEFT JOIN `sfk_mobileassistant_push_settings` mpn ON mpn.`device_unique_id` = md.`device_unique_id`
  28. WHERE mpn.`device_unique_id` IS NULL
  29. 2019-09-20 11:36:58 34944708352 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE ma FROM `sfk_mobileassistant_accounts` ma
  30. LEFT JOIN `sfk_mobileassistant_devices` md ON md.`account_id` = ma.`id`
  31. WHERE ma.`id` IS NULL
  32. 2019-09-20 11:36:58 34944708352 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE md FROM `sfk_mobileassistant_devices` md
  33. LEFT JOIN `sfk_mobileassistant_push_settings` mpn ON mpn.`device_unique_id` = md.`device_unique_id`
  34. WHERE mpn.`device_unique_id` IS NULL
  35. 2019-09-20 11:36:58 34944708352 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE ma FROM `sfk_mobileassistant_accounts` ma
  36. LEFT JOIN `sfk_mobileassistant_devices` md ON md.`account_id` = ma.`id`
  37. WHERE ma.`id` IS NULL
  38. 2019-09-20 11:36:58 34944708352 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE md FROM `sfk_mobileassistant_devices` md
  39. LEFT JOIN `sfk_mobileassistant_push_settings` mpn ON mpn.`device_unique_id` = md.`device_unique_id`
  40. WHERE mpn.`device_unique_id` IS NULL
  41. 2019-09-20 11:36:58 34944708352 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE ma FROM `sfk_mobileassistant_accounts` ma
  42. LEFT JOIN `sfk_mobileassistant_devices` md ON md.`account_id` = ma.`id`
  43. WHERE ma.`id` IS NULL
  44. 2019-09-20 11:36:58 34944708352 [Note] Suppressing warnings of type 'Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave.' for up to 300 seconds because of flooding
  45. 2019-09-20 11:37:00 34895181824 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE bol_posts SET post_password = 'cf4cc60a0eb1b67c1952', post_modified_gmt = '2019-09-20 11:37:00', post_modified = '2019-09-20 11:37:00' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:37:00' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  46. 2019-09-20 11:37:38 34944718592 [Note] Suppressing warnings of type 'The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.' for up to 300 seconds because of flooding
  47. 2019-09-20 11:40:01 34947716864 [Note] Suppressed 50 unsafe warnings during the last 316 seconds
  48. 2019-09-20 11:40:01 34947716864 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE bol_posts SET post_password = '8b8ff604b4b9ef7eb670', post_modified_gmt = '2019-09-20 11:40:01', post_modified = '2019-09-20 11:40:01' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:40:01' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  49. 2019-09-20 11:40:05 34944723712 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE sfk_posts SET post_password = 'ec59efcfefd13a80083b', post_modified_gmt = '2019-09-20 11:40:05', post_modified = '2019-09-20 11:40:05' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:40:05' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  50. 2019-09-20 11:40:13 34944704512 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE mma_posts SET post_password = '97f624dcd91445b3224c', post_modified_gmt = '2019-09-20 11:40:13', post_modified = '2019-09-20 11:40:13' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:40:13' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  51. 2019-09-20 11:41:00 34945019648 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE bol_posts SET post_password = '75d42634b09484036372', post_modified_gmt = '2019-09-20 11:41:00', post_modified = '2019-09-20 11:41:00' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:41:00' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  52. 2019-09-20 11:41:04 34943600896 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE sfk_posts SET post_password = '211c10800e8d5d506395', post_modified_gmt = '2019-09-20 11:41:04', post_modified = '2019-09-20 11:41:04' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:41:04' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  53. 2019-09-20 11:41:04 34895174144 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE triwp_posts SET post_password = '708052435559b28a38e3', post_modified_gmt = '2019-09-20 11:41:04', post_modified = '2019-09-20 12:41:04' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:41:04' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  54. 2019-09-20 11:41:19 34945026048 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE mma_posts SET post_password = '9cf2048397f969242f63', post_modified_gmt = '2019-09-20 11:41:19', post_modified = '2019-09-20 11:41:19' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:41:19' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  55. 2019-09-20 11:41:50 34944712192 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE sfk_posts SET post_password = '9a8b07583bfacb6be9c0', post_modified_gmt = '2019-09-20 11:41:50', post_modified = '2019-09-20 11:41:50' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:41:50' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  56. 2019-09-20 11:41:59 34946418944 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE bol_posts SET post_password = '8f22b46eed82f05e132c', post_modified_gmt = '2019-09-20 11:41:59', post_modified = '2019-09-20 11:41:59' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:41:59' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  57. 2019-09-20 11:42:24 34945022208 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE triwp_posts SET post_password = '215a49d03fb526527227', post_modified_gmt = '2019-09-20 11:42:24', post_modified = '2019-09-20 12:42:24' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:42:24' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  58. 2019-09-20 11:42:44 34943151872 [Note] Suppressing warnings of type 'The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.' for up to 300 seconds because of flooding
  59. 2019-09-20 11:45:01 34944718592 [Note] Suppressed 18 unsafe warnings during the last 301 seconds
  60. 2019-09-20 11:45:01 34944718592 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE bol_posts SET post_password = '7bb41e62dd2f2d99df27', post_modified_gmt = '2019-09-20 11:45:01', post_modified = '2019-09-20 11:45:01' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:45:01' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  61. 2019-09-20 11:45:05 34944205568 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE triwp_posts SET post_password = 'f9c31e16f40e7f8a7e19', post_modified_gmt = '2019-09-20 11:45:05', post_modified = '2019-09-20 12:45:05' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:45:05' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  62. 2019-09-20 11:45:11 34944209408 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE mma_posts SET post_password = '7af60ccb0bdcc60e12e2', post_modified_gmt = '2019-09-20 11:45:11', post_modified = '2019-09-20 11:45:11' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:45:11' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  63. 2019-09-20 11:45:51 34944517632 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE sfk_posts SET post_password = 'c71ab7de39a4b132cf88', post_modified_gmt = '2019-09-20 11:45:51', post_modified = '2019-09-20 11:45:51' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:45:51' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  64. 2019-09-20 11:46:01 34944707072 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE bol_posts SET post_password = '1439fa7804831a7979d3', post_modified_gmt = '2019-09-20 11:46:01', post_modified = '2019-09-20 11:46:01' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:46:01' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  65. 2019-09-20 11:46:14 34951705856 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE mma_posts SET post_password = '9439a87e1b940e749d64', post_modified_gmt = '2019-09-20 11:46:14', post_modified = '2019-09-20 11:46:14' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:46:14' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  66. 2019-09-20 11:46:25 34894662912 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE triwp_posts SET post_password = '6e369d38859376e82d49', post_modified_gmt = '2019-09-20 11:46:25', post_modified = '2019-09-20 12:46:25' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:46:25' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  67. 2019-09-20 11:46:52 34947710464 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE sfk_posts SET post_password = 'bae9ee384227264eacb2', post_modified_gmt = '2019-09-20 11:46:52', post_modified = '2019-09-20 11:46:52' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:46:52' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  68. 2019-09-20 11:47:01 34944712192 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE bol_posts SET post_password = '4e91915782ac1fca300f', post_modified_gmt = '2019-09-20 11:47:01', post_modified = '2019-09-20 11:47:01' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:47:01' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  69. 2019-09-20 11:47:43 34943597056 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE mma_posts SET post_password = '3de1e5d4a4cd7fd6b80b', post_modified_gmt = '2019-09-20 11:47:43', post_modified = '2019-09-20 11:47:43' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:47:43' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  70. 2019-09-20 11:47:52 34943600896 [Note] Suppressing warnings of type 'The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.' for up to 300 seconds because of flooding
  71. 2019-09-20 11:50:23 34913826304 [Note] Suppressed 19 unsafe warnings during the last 321 seconds
  72. 2019-09-20 11:50:23 34913826304 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE mma_posts SET post_password = '0519f64b3d471978c216', post_modified_gmt = '2019-09-20 11:50:23', post_modified = '2019-09-20 11:50:23' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:50:23' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  73. 2019-09-20 11:50:27 34943160832 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE triwp_posts SET post_password = '7d4bab947af238a25e99', post_modified_gmt = '2019-09-20 11:50:27', post_modified = '2019-09-20 12:50:27' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:50:27' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  74. 2019-09-20 11:50:52 34947716864 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE sfk_posts SET post_password = '825e86c157b27e4c7b67', post_modified_gmt = '2019-09-20 11:50:52', post_modified = '2019-09-20 11:50:52' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:50:52' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  75. 2019-09-20 11:50:59 34895174144 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE bol_posts SET post_password = 'bb1749098a4e025b73a8', post_modified_gmt = '2019-09-20 11:50:59', post_modified = '2019-09-20 11:50:59' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:50:59' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  76. 2019-09-20 11:51:12 34944204288 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE mma_posts SET post_password = '8a8551dd29d9c03b9f7a', post_modified_gmt = '2019-09-20 11:51:12', post_modified = '2019-09-20 11:51:12' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:51:12' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  77. 2019-09-20 11:51:52 34944708352 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE sfk_posts SET post_password = 'e8e18782f932a0053ff9', post_modified_gmt = '2019-09-20 11:51:52', post_modified = '2019-09-20 11:51:52' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:51:52' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  78. 2019-09-20 11:52:01 34944213248 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE bol_posts SET post_password = '5fac985fa69ded1edcda', post_modified_gmt = '2019-09-20 11:52:01', post_modified = '2019-09-20 11:52:01' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:52:01' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  79. 2019-09-20 11:52:12 34946048512 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE mma_posts SET post_password = '76af5a4e37c95a5b4b69', post_modified_gmt = '2019-09-20 11:52:12', post_modified = '2019-09-20 11:52:12' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:52:12' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  80. 2019-09-20 11:52:52 34946431744 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE sfk_posts SET post_password = '3fb98033271c4299d025', post_modified_gmt = '2019-09-20 11:52:52', post_modified = '2019-09-20 11:52:52' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:52:52' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  81. 2019-09-20 11:52:59 34943167232 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE bol_posts SET post_password = '6ad35920c4a6c539f66e', post_modified_gmt = '2019-09-20 11:52:59', post_modified = '2019-09-20 11:52:59' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:52:59' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  82. 2019-09-20 11:53:08 34951705856 [Note] Suppressing warnings of type 'The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.' for up to 300 seconds because of flooding
  83. 2019-09-20 11:55:23 34944723712 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave. Statement: INSERT IGNORE INTO sfk_mailpoet_subscribers (is_woocommerce_user, email, status, created_at, last_subscribed_at, source)
  84. SELECT 1, wppm.meta_value, "subscribed", CURRENT_TIMESTAMP(), CURRENT_TIMESTAMP(), "woocommerce_user" FROM `sfk_postmeta` wppm
  85. JOIN `sfk_posts` p ON wppm.post_id = p.ID AND p.post_type = "shop_order"
  86. WHERE wppm.meta_key = "_billing_email" AND wppm.meta_value != ""
  87. AND p.ID = "51070"
  88. ON DUPLICATE KEY UPDATE is_woocommerce_user = 1
  89. 2019-09-20 11:55:23 34944723712 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on master and the slave. Statement: INSERT IGNORE INTO sfk_mailpoet_subscribers (is_woocommerce_user, email, status, created_at, last_subscribed_at, source)
  90. SELECT 1, wppm.meta_value, "subscribed", CURRENT_TIMESTAMP(), CURRENT_TIMESTAMP(), "woocommerce_user" FROM `sfk_postmeta` wppm
  91. JOIN `sfk_posts` p ON wppm.post_id = p.ID AND p.post_type = "shop_order"
  92. WHERE wppm.meta_key = "_billing_email" AND wppm.meta_value != ""
  93. AND p.ID = "51070"
  94. ON DUPLICATE KEY UPDATE is_woocommerce_user = 1
  95. 2019-09-20 11:55:23 34944723712 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: INSERT IGNORE INTO sfk_mailpoet_subscribers (is_woocommerce_user, email, status, created_at, last_subscribed_at, source)
  96. SELECT 1, wppm.meta_value, "subscribed", CURRENT_TIMESTAMP(), CURRENT_TIMESTAMP(), "woocommerce_user" FROM `sfk_postmeta` wppm
  97. JOIN `sfk_posts` p ON wppm.post_id = p.ID AND p.post_type = "shop_order"
  98. WHERE wppm.meta_key = "_billing_email" AND wppm.meta_value != ""
  99. AND p.ID = "51070"
  100. ON DUPLICATE KEY UPDATE is_woocommerce_user = 1
  101. 2019-09-20 11:55:23 34944719872 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE md FROM `sfk_mobileassistant_devices` md
  102. LEFT JOIN `sfk_mobileassistant_push_settings` mpn ON mpn.`device_unique_id` = md.`device_unique_id`
  103. WHERE mpn.`device_unique_id` IS NULL
  104. 2019-09-20 11:55:23 34944719872 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE ma FROM `sfk_mobileassistant_accounts` ma
  105. LEFT JOIN `sfk_mobileassistant_devices` md ON md.`account_id` = ma.`id`
  106. WHERE ma.`id` IS NULL
  107. 2019-09-20 11:55:23 34944719872 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE md FROM `sfk_mobileassistant_devices` md
  108. LEFT JOIN `sfk_mobileassistant_push_settings` mpn ON mpn.`device_unique_id` = md.`device_unique_id`
  109. WHERE mpn.`device_unique_id` IS NULL
  110. 2019-09-20 11:55:23 34944719872 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE ma FROM `sfk_mobileassistant_accounts` ma
  111. LEFT JOIN `sfk_mobileassistant_devices` md ON md.`account_id` = ma.`id`
  112. WHERE ma.`id` IS NULL
  113. 2019-09-20 11:55:23 34944719872 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE md FROM `sfk_mobileassistant_devices` md
  114. LEFT JOIN `sfk_mobileassistant_push_settings` mpn ON mpn.`device_unique_id` = md.`device_unique_id`
  115. WHERE mpn.`device_unique_id` IS NULL
  116. 2019-09-20 11:55:23 34944719872 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE ma FROM `sfk_mobileassistant_accounts` ma
  117. LEFT JOIN `sfk_mobileassistant_devices` md ON md.`account_id` = ma.`id`
  118. WHERE ma.`id` IS NULL
  119. 2019-09-20 11:55:23 34944719872 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE md FROM `sfk_mobileassistant_devices` md
  120. LEFT JOIN `sfk_mobileassistant_push_settings` mpn ON mpn.`device_unique_id` = md.`device_unique_id`
  121. WHERE mpn.`device_unique_id` IS NULL
  122. 2019-09-20 11:55:23 34944719872 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE ma FROM `sfk_mobileassistant_accounts` ma
  123. LEFT JOIN `sfk_mobileassistant_devices` md ON md.`account_id` = ma.`id`
  124. WHERE ma.`id` IS NULL
  125. 2019-09-20 11:55:23 34944719872 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE md FROM `sfk_mobileassistant_devices` md
  126. LEFT JOIN `sfk_mobileassistant_push_settings` mpn ON mpn.`device_unique_id` = md.`device_unique_id`
  127. WHERE mpn.`device_unique_id` IS NULL
  128. 2019-09-20 11:55:23 34944719872 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE ma FROM `sfk_mobileassistant_accounts` ma
  129. LEFT JOIN `sfk_mobileassistant_devices` md ON md.`account_id` = ma.`id`
  130. WHERE ma.`id` IS NULL
  131. 2019-09-20 11:55:24 34944719872 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE md FROM `sfk_mobileassistant_devices` md
  132. LEFT JOIN `sfk_mobileassistant_push_settings` mpn ON mpn.`device_unique_id` = md.`device_unique_id`
  133. WHERE mpn.`device_unique_id` IS NULL
  134. 2019-09-20 11:55:24 34944719872 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE ma FROM `sfk_mobileassistant_accounts` ma
  135. LEFT JOIN `sfk_mobileassistant_devices` md ON md.`account_id` = ma.`id`
  136. WHERE ma.`id` IS NULL
  137. 2019-09-20 11:55:24 34944719872 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE md FROM `sfk_mobileassistant_devices` md
  138. LEFT JOIN `sfk_mobileassistant_push_settings` mpn ON mpn.`device_unique_id` = md.`device_unique_id`
  139. WHERE mpn.`device_unique_id` IS NULL
  140. 2019-09-20 11:55:24 34944719872 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE ma FROM `sfk_mobileassistant_accounts` ma
  141. LEFT JOIN `sfk_mobileassistant_devices` md ON md.`account_id` = ma.`id`
  142. WHERE ma.`id` IS NULL
  143. 2019-09-20 11:55:25 34944719872 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: INSERT INTO sfk_postmeta (post_id,meta_key,meta_value)
  144. SELECT 51070,'_order_number',IF(MAX(CAST(meta_value AS SIGNED)) IS NULL OR MAX(CAST(meta_value AS SIGNED)) < 100, 100, MAX(CAST(meta_value AS SIGNED))+1)
  145. FROM sfk_postmeta
  146. WHERE meta_key='_order_number'
  147. 2019-09-20 11:55:30 34914346240 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE triwp_posts SET post_password = '863e56656a289b638efa', post_modified_gmt = '2019-09-20 11:55:30', post_modified = '2019-09-20 12:55:30' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:55:30' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  148. 2019-09-20 11:55:48 34944206848 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE sfk_posts SET post_password = '6e8fb9cba681aa0bd05a', post_modified_gmt = '2019-09-20 11:55:48', post_modified = '2019-09-20 11:55:48' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:55:48' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  149. 2019-09-20 11:56:02 34944500992 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE bol_posts SET post_password = '3c3bc7f855103b59ac81', post_modified_gmt = '2019-09-20 11:56:02', post_modified = '2019-09-20 11:56:02' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:56:02' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  150. 2019-09-20 11:56:12 34944718592 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE mma_posts SET post_password = '451b800b50ab95ef60bf', post_modified_gmt = '2019-09-20 11:56:12', post_modified = '2019-09-20 11:56:12' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:56:12' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  151. 2019-09-20 11:56:14 34946424064 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE md FROM `sfk_mobileassistant_devices` md
  152. LEFT JOIN `sfk_mobileassistant_push_settings` mpn ON mpn.`device_unique_id` = md.`device_unique_id`
  153. WHERE mpn.`device_unique_id` IS NULL
  154. 2019-09-20 11:56:14 34946424064 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE ma FROM `sfk_mobileassistant_accounts` ma
  155. LEFT JOIN `sfk_mobileassistant_devices` md ON md.`account_id` = ma.`id`
  156. WHERE ma.`id` IS NULL
  157. 2019-09-20 11:56:14 34946424064 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE md FROM `sfk_mobileassistant_devices` md
  158. LEFT JOIN `sfk_mobileassistant_push_settings` mpn ON mpn.`device_unique_id` = md.`device_unique_id`
  159. WHERE mpn.`device_unique_id` IS NULL
  160. 2019-09-20 11:56:14 34946424064 [Note] Suppressing warnings of type 'Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave.' for up to 300 seconds because of flooding
  161. 2019-09-20 11:57:02 34914351360 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE bol_posts SET post_password = '1645c091be06ff1b5344', post_modified_gmt = '2019-09-20 11:57:02', post_modified = '2019-09-20 11:57:02' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:57:02' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  162. 2019-09-20 11:57:09 34914346240 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE sfk_posts SET post_password = 'a081adc0374396acf450', post_modified_gmt = '2019-09-20 11:57:09', post_modified = '2019-09-20 11:57:09' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:57:09' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  163. 2019-09-20 11:57:10 34946424064 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE triwp_posts SET post_password = '75a62ad19e240052dcdb', post_modified_gmt = '2019-09-20 11:57:10', post_modified = '2019-09-20 12:57:10' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:57:10' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  164. 2019-09-20 11:57:13 34946431744 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE mma_posts SET post_password = '1113efce5592b61d4d5a', post_modified_gmt = '2019-09-20 11:57:13', post_modified = '2019-09-20 11:57:13' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:57:13' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  165. 2019-09-20 11:57:50 34943167232 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE sfk_posts SET post_password = 'd2e28a522f0486bcf918', post_modified_gmt = '2019-09-20 11:57:50', post_modified = '2019-09-20 11:57:50' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 11:57:50' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  166. 2019-09-20 11:57:54 34894655232 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave. Statement: INSERT IGNORE INTO mma_mailpoet_subscribers (is_woocommerce_user, email, status, created_at, last_subscribed_at, source)
  167. SELECT 1, wppm.meta_value, "subscribed", CURRENT_TIMESTAMP(), CURRENT_TIMESTAMP(), "woocommerce_user" FROM `mma_postmeta` wppm
  168. JOIN `mma_posts` p ON wppm.post_id = p.ID AND p.post_type = "shop_order"
  169. WHERE wppm.meta_key = "_billing_email" AND wppm.meta_value != ""
  170. AND p.ID = "40586"
  171. ON DUPLICATE KEY UPDATE is_woocommerce_user = 1
  172. 2019-09-20 11:57:54 34894655232 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on master and the slave. Statement: INSERT IGNORE INTO mma_mailpoet_subscribers (is_woocommerce_user, email, status, created_at, last_subscribed_at, source)
  173. SELECT 1, wppm.meta_value, "subscribed", CURRENT_TIMESTAMP(), CURRENT_TIMESTAMP(), "woocommerce_user" FROM `mma_postmeta` wppm
  174. JOIN `mma_posts` p ON wppm.post_id = p.ID AND p.post_type = "shop_order"
  175. WHERE wppm.meta_key = "_billing_email" AND wppm.meta_value != ""
  176. AND p.ID = "40586"
  177. ON DUPLICATE KEY UPDATE is_woocommerce_user = 1
  178. 2019-09-20 11:58:00 34913217024 [Note] Suppressing warnings of type 'The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.' for up to 300 seconds because of flooding
  179. 2019-09-20 12:00:30 34894651392 [Note] Suppressed 68 unsafe warnings during the last 307 seconds
  180. 2019-09-20 12:00:30 34894651392 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE mma_posts SET post_password = '021fe7455762041ba97d', post_modified_gmt = '2019-09-20 12:00:30', post_modified = '2019-09-20 12:00:30' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-09-20 12:00:30' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
  181. 190920 12:43:55 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
  182. 2019-09-20 12:43:55 34422751232 [Note] /usr/local/libexec/mysqld (mysqld 10.1.40-MariaDB) starting as process 7919 ...
  183. 2019-09-20 12:43:57 34422751232 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
  184.  
  185. 2019-09-20 12:43:57 34422751232 [Note] InnoDB: Using mutexes to ref count buffer pool pages
  186. 2019-09-20 12:43:57 34422751232 [Note] InnoDB: The InnoDB memory heap is disabled
  187. 2019-09-20 12:43:57 34422751232 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
  188. 2019-09-20 12:43:57 34422751232 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
  189. 2019-09-20 12:43:57 34422751232 [Note] InnoDB: Compressed tables use zlib 1.2.11
  190. 2019-09-20 12:43:57 34422751232 [Note] InnoDB: Using SSE crc32 instructions
  191. 2019-09-20 12:43:57 34422751232 [Note] InnoDB: Initializing buffer pool, size = 128.0M
  192. 2019-09-20 12:43:57 34422751232 [Note] InnoDB: Completed initialization of buffer pool
  193. 2019-09-20 12:43:57 34422751232 [Note] InnoDB: Highest supported file format is Barracuda.
  194. 2019-09-20 12:43:57 34422751232 [Note] InnoDB: Starting crash recovery from checkpoint LSN=438816573015
  195. 2019-09-20 12:44:13 34422751232 [Note] InnoDB: Processed 2255 .ibd/.isl files
  196. 2019-09-20 12:44:28 34422751232 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
  197. 2019-09-20 12:44:28 34422751232 [Note] InnoDB: Read redo log up to LSN=438816704000
  198. 2019-09-20 12:44:28 34422751232 [Note] InnoDB: Starting final batch to recover 126 pages from redo log
  199. InnoDB: Last MySQL binlog file position 0 1054665644, file name ./mysql-bin.000562
  200. 2019-09-20 12:44:29 34422751232 [Note] InnoDB: 128 rollback segment(s) are active.
  201. 2019-09-20 12:44:29 34422751232 [Note] InnoDB: Waiting for purge to start
  202. 2019-09-20 12:44:29 34422751232 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.43-84.3 started; log sequence number 438816958010
  203. 2019-09-20 12:44:32 34912111616 [Note] InnoDB: Dumping buffer pool(s) not yet started
  204. 2019-09-20 12:44:32 34422751232 [Note] Plugin 'FEEDBACK' is disabled.
  205. 2019-09-20 12:44:32 34422751232 [Note] Recovering after a crash using mysql-bin
  206. 2019-09-20 12:44:47 34422751232 [Note] Starting crash recovery...
  207. 2019-09-20 12:44:47 34422751232 [Note] Crash recovery finished.
  208. 2019-09-20 12:44:48 34422751232 [Note] Server socket created on IP: '0.0.0.0'.
  209. 2019-09-20 12:44:48 34422751232 [Note] /usr/local/libexec/mysqld: ready for connections.
  210. Version: '10.1.40-MariaDB' socket: '/tmp/mysql.sock' port: 3306 FreeBSD Ports
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!